Jabber SIP B2B URI calls
This diagram shows how Expressways convey calls between inbound and outbound. In Cisco document, please check here:
The example I use is to let Expressways transmit outgoing calls to WebEx CMR and specific business partners.
SIP Trunk Security Profile on CUCM
In case of using MRA, please make a different incoming port 5065 instead of default 5060.
SIP Trunk Configuration on CUCM
My case has two expressway C’s in a cluster. I put in two IPs of them with 5060 destination port.
SIP Route Patterns to Expressway C
9-digit simplified WebEx CMR dial-pattern
Unified CM Neighbor Zone (B2B) on Expressway C
Why port 5060? see here Registration issue
Due to 5060/5061 is used for your MRA, change the SIP port on the SIP Trunk Security Profile that is applied to the existing SIP trunk configured in CUCM and the Expressway-C neighbor zone for CUCM to a different port such as 5065.
A diagnostic log from Expressway-C shows a SIP/2.0 405 Method Not Allowed message in response to the Registration request sent by the Jabber client. This is likely due to an existing Session Initiation Protocol (SIP) trunk between Expressway-C and CUCM using port 5060/5061.
TraversalClient (B2B) Traversal client zone on Expressway C
URI Outbound Search rules on Expressway C
9-digit WebEx Outbound Search rules on Expressway C
Inbound domain call Search rules on Expressway C
DNS Zone on Expressway E
TraversalServer (B2B) Zone on Expressway E
B2B outbound call search rule on Expressway E
I configured only one rule to simply my configuration. It only accepts calls from Server zone on VCS-Core server.
B2B inbound call search rule on Expressway E
No comments:
Post a Comment