Re: Call Manager Inter Cluster Trunk Gatekeeper Controlled
The Annex M.1 feature uses intercluster trunks and H.225 trunks to transport (tunnel) non-H.323 protocol information in H.323 signaling messages between Cisco CallManagers. Annex M.1 supports QSIG calls and QSIG call independent signaling connections. After you complete intercluster trunk configuration in Cisco CallManager Administration, QSIG tunneling supports the following features: Call Completion, Call Diversion, Call Transfer, Identification Services, Message Waiting Indication, and Path Replacement.
Note For designated third-party switch equipment, the Annex M.1 feature can also use H.323 gateways to transport (tunnel) non-H.323 protocol information in H.323 signaling messages between Cisco CallManagers. Refer to the Cisco CallManager Compatibility Matrix for information about Annex M.1 feature interoperability with third-party vendors.
Tip If you use a gatekeeper, you must configure every gateway in the network for QSIG tunneling. If any gateway in the network does not support QSIG tunneling, calls drop at the intercluster trunk that is configured for QSIG tunneling.
For Cisco CallManager to support QSIG tunneling, you must choose the QSIG option in the Tunneled Protocol drop-down list box and check the Path Replacement Support check box in the Trunk Configuration window in Cisco CallManager Administration. By default, Cisco CallManager sets the option in the Tunneled Protocol drop-down list box to None; after you configure the QSIG Tunneled Protocol option, the Path Replacement Support check box automatically becomes checked. If you do not require path replacement over Annex M.1 or QSIG-tunneled trunks, you can uncheck the check box.
When you set the Tunneled Protocol field to None, Cisco CallManager automatically grays out the Path Replacement Support check box. When you set the Tunneled Protocol field to QSIG, you cannot configure the Redirecting Number IE Delivery (Inbound), Redirecting Number IE Delivery (Outbound), or Display IE Delivery options.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...