Sip Trunk or Inter-Cluster Trunk

[pjdouglas42]

Hi All,

We are running call manager v 10.5 and have just installed a private link to another site.

The call manager systems at each site are completely independant of each other and do not share the share dialing plans.

Our intention is to route internal calls down the link between the two sites via a sip trunk.

It has now been suggested that we use an inter-cluster trunk - non-gatekeepr controlled over sip.

I just wondered what the advantages/dis-advantages where using one over the other ?

From what I have read inter-cluster links are simple to setup but less resilient than sip. My understanding is that sip would be the better option.

Would appreciate some advice on the pro's and con's on which is the better option.

Many Thanks

Paul

[Suresh Subramanian]

While H.323 trunks are still supported, SIP trunks are the recommended trunk type for Unified Communication deployments because SIP trunks provide additional features and functionality not available with H.323 trunks.

while SIP and H.323 trunks share many of the same features for trunk connections between Cisco devices, SIP trunks support several features that are not supported by H.323 trunks. For trunk connections to other vendors' products and to service provider networks, SIP is the most commonly deployed protocol today and is growing in usage as Unified Communications products and networks using protocols such as H.323 migrate to SIP.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab10/collab10/trunks.html

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab10/collab10/trunks.html#44742

[pjdouglas42]

Many thanks for your reply Suresh.

Its pretty much what I thought, not sure why inter-cluster link was suggested.

Kind Regards

Paul