cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1391
Views
7
Helpful
18
Replies

Inter-Cluster Trunk (Non-Gateway Controlled) won't register

philip-cr
Level 1
Level 1

I figured out a workaround for this issue, but found it very curious. My Inter-Cluster Trunk only registers to my Subscriber Nodes. If I change the IP in the trunk to either of my Publisher Nodes then it no longer routes calls through it.

Any ideas as to what could cause a Publisher to not be registered for this? The SIP trunks work fine.


It's a test environment and I have an extremely basic setup:

philipcr_0-1755198062352.png

philipcr_1-1755198188329.png

 

 

18 Replies 18

Rookie mistake, I changed the order in the CCM-Group, but it was not the CCM-Group selected in the device pool... You were right it mattered which order it was in.

Firstly, AFAIK, ICT trunks are no longer widely used in Such deployments. It's generally recommended to use SIP trunks for inter-cluster communication.

Secondly, you have the option to include both the publisher and subscriber nodes in the ICT trunk configuration. You're currently only adding the publisher, you must  include both nodes.

If i recall correctly  when using the "Run on All Nodes" option in combination with a CM Group, the system typically attempts to register with the node that appears first in the CM Group list. There is a specific algorithm that governs this behavior, so it’s worth reviewing Cisco’s documentation to understand how it works.

since your setup only involves two nodes, enabling "Run on All Nodes" may not be necessary.



Response Signature


I tried putting the publisher on top in the Call Manager group and it had no affect on the situation. Call Manager Service is running on all nodes.