Run On All Active CM Nodes Route List vs SIP Trunk - Deep Dive

[Meddane]

Run on All Active Nodes disabled on both Route List and SIP Trunk.

In this case, using the Route List and Route Group concepts, the Route List is the calling device. The endpoints HQ-Phone-1 with DN 5001 and HQ-Phone-2 are registered to HQ-PUB and HQ-SUB respectively.

Case 1 :

• The Route List is registered to HQ-PUB 10.1.5.15.
• The SIP Trunk is associated to UCM Group SUB that contains HQ-SUB 10.1.5.14.

Because the calling device (Route List) is registered to CUCM HQ-PUB that is NOT part of UCM Group’s SIP Trunk. The outbound call is sent using the From header: "500X" <sip:500X@10.1.5.14>, the Server 10.1.5.14 in the UCM Group of the SIP Trunk is always used to initiate outbound call.

Case 2 :

• The Route List is registered to HQ-PUB 10.1.5.15.
• The SIP Trunk is associated to UCM Group PUB that contains HQ-PUB 10.1.5.15.

Because the calling device (Route List) is registered to CUCM HQ-PUB that is part of UCM Group’s SIP Trunk. The outbound call is sent using the From header: "500X" <sip:500X@10.1.5.15>, the Server 10.1.5.15 where the Route List is registered to is always used to initiate outbound call.

Case 3 :

• The Route List is registered to HQ-SUB 10.1.5.14.
• The SIP Trunk is associated to UCM Group PUB that contains HQ-PUB 10.1.5.15.

Because the calling device (Route List) is registered to CUCM HQ-SUB that is NOT part of UCM Group’s SIP Trunk. The outbound call is sent using the From header: "500X" <sip:500X@10.1.5.15>, the Server 10.1.5.15 in the UCM Group of the SIP Trunk is always used to initiate outbound call.

Case 4 :

• The Route List is registered to HQ-SUB 10.1.5.14.
• The SIP Trunk is associated to UCM Group SUB that contains HQ-SUB 10.1.5.14.

Because the calling device (Route List) is registered to CUCM HQ-SUB that is part of UCM Group’s SIP Trunk. The outbound call is sent using the From header: "500X" <sip:500X@10.1.5.14>, the Server 10.1.5.14 where the Route List is registered to is always used to initiate outbound call.

Run on All Active Nodes enabled on Route List, disabled on SIP Trunk. In this case the Endpoint is the calling device.

Case 1 :

• The Endpoint is registered to HQ-PUB 10.1.5.15.
• The Route List with Run On All Active UCM Nodes enabled. Note : The UCM Group is irrelevant for the Route List.
• The SIP Trunk is associated to UCM Group PUB that contains HQ-PUB 10.1.5.15.

The phone HQ-Phone-1 is registered in the HQ-PUB which is part of the UCM Group's SIP Trunk. The outbound call is sent using the following From header: "5001" <sip:5001@10.1.5.15>, the Server 10.1.5.15 where the Endpoint is registered to is used to initiate outbound call.

The phone HQ-Phone-2 is registered in the HQ-SUB and this server is not in the UCM Group's SIP Trunk. The outbound call is sent using the following From header: "5002" <sip:5002@10.1.5.15>, the Server 10.1.5.15 in the UCM Group of the SIP Trunk is used to initiate outbound call.

Case 2 :

• The Endpoint is registered to HQ-PUB 10.1.5.15.
• The Route List with Run On All Active UCM Nodes enabled. Note : The UCM Group is irrelevant for the Route List.
• The SIP Trunk is associated to UCM Group SUB that contains HQ-SUB 10.1.5.14.

The Phone HQ-Phone-1 is registered in the HQ-PUB and this server is not in the UCM Group's SIP Trunk. The outbound call is sent using the following From header: "5001" <sip:5001@10.1.5.14>, the Server 10.1.5.14 in the UCM Group of the SIP Trunk is used to initiate outbound call.

The phone HQ-Phone-2 is registered in the HQ-SUB which is part of the UCM Group's SIP Trunk. The outbound call is sent using the following From header: "5002" <sip:5002@10.1.5.14>, the Server 10.1.5.14 where the Endpoint is registered to is used to initiate outbound call.

Run on All Active Nodes disabled on Route List, enabled on SIP Trunk. In this case the Route List is the calling device.

Case 1 :

• The Endpoint is registered to HQ-PUB 10.1.5.15.
• The SIP Trunk with Run On All Active UCM Nodes enabled. Note : The UCM Group is irrelevant for the SIP Trunk.
• The Route List is associated to UCM Group PUB that contains HQ-PUB 10.1.5.15.

For both HQ-Phone-1 and HQ-Phone-2 Calls. The outbound call is sent using the following From header: "5001" <sip:5001@10.1.5.15>, the Server 10.1.5.15 where the Route List is registered to is used to initiate outbound call.

Case 2 :

• The Endpoint is registered to HQ-PUB 10.1.5.15.
• The SIP Trunk with Run On All Active UCM Nodes enabled. Note : The UCM Group is irrelevant for the SIP Trunk.
• The Route List is associated to UCM Group SUB that contains HQ-SUB 10.1.5.14. Note : the Route List is the calling device.

For both HQ-Phone-1 and HQ-Phone-2 Calls. The outbound call is sent using the following From header: "5001" <sip:5001@10.1.5.14>, the Server 10.1.5.14 where the Route List is registered to is used to initiate outbound call.

As you can notice, The Route List is only active on one CUCM server, as a result all outbound calls will be initiated by the server where the Route List is registered to. This is not recommended.

Run on All Active Nodes enabled on both Route List and SIP Trunk

In this case the UCM Groups for Route List and SIP Trunk are irrelevant. The Endpoint is the calling device.

1. If the Phone is registered to HQ-PUB 10.1.1.5.15. The outbound call is sent using the following From header: "5001" <sip:5001@10.1.5.15>, the Server 10.1.5.15 where the Endpoint is registered to is used to initiate outbound call.
2. If the Phone is registered to HQ-SUB 10.1.1.5.14. The outbound call is sent using the following From header: "5001" <sip:5001@10.1.5.14>, the Server 10.1.5.14 where the Endpoint is registered to is used to initiate outbound call.