09-22-2015 04:09 AM - edited 03-18-2019 05:01 AM
Hi everyone!
I´m deploying the following scenario:
Cucm --> exp-c --> exp-e
I have registered sx10 and cisco jabbers on Cucm and I have implemented mra and b2b on expressway solution. From sx10 I can dial to external domain, external ip address and everythings work fine.
Also, I uploaded jabber-config.xml for uri dialing from jabbers users but I have a problem: When I dial b2b calls from a jabber user, the call arrive to expressway-c but this uses the mra zone to expressway-e, then "Service Unavailable" error appear . I have already added the b2b zone and work well from sx10 endpoint but no from jabbers users.
Anyone can help me?
Regards!
Solved! Go to Solution.
09-25-2015 08:41 AM
Something odd is going on here. It looks like Jabber is still trying to make this call as an MRA call.
Try adding a SIP Route Pattern (domain pattern) in CUCM for externaldomain.es and point it at your 5560 B2B SIP Trunk to Expressway. Then restart Jabber and try the call again. If it does not succeed please post the search history again.
09-22-2015 04:25 AM
Hi Dear,
check in search history why same call using different different zones to reach destination
i understood when you are dialing from sx 10 its working fine and going out from b2b zone
but in case of jabber dialing same destination but going out from MRA zone
same destination ( but using different zone )
Please check both call search history u will get idea where you are missing exactly
09-22-2015 12:34 PM
What version UCM are you running? Also please post jabber-config.xml, output of both calls search history on Exp-c and Exp-e.
09-22-2015 11:27 PM
Hi,
Thanks for your both replies.
The version are:
- Cucm: 10.5.2.10000-5
- EXP-C/E: X8.5.1
The jabber config:
<config version="1.0">
<Directory>
<DirectoryServerType>UDS</DirectoryServerType>
</Directory>
<Policies>
<Screen_Capture_Enabled>true</Screen_Capture_Enabled>
<File_Transfer_Enabled>true</File_Transfer_Enabled>
<EnableVideo>true</EnableVideo>
<UserDefinedRemoteDestinations>true</UserDefinedRemoteDestinations>
<EnableSIPURIDialling>true</EnableSIPURIDialling>
<DirectoryURI>mail</DirectoryURI>
</Policies>
<Options>
<AllowUserCustomTabs>true</AllowUserCustomTabs>
</Options>
</config>
Also, I saw, on the expressway-c that the originating zone of the fails call is Defaultzone (type default) but the originating zone of the good call is type Neighbor called: "cucm traversal b2b".
Fails call
Zone (1)
Name: DefaultZone
Type: Default
Good Call
Zone (1)
Name: Cucm Traversal B2B
Type: Neighbor
The jabbers, are registered from internet across the expressway-e.
Regards!
09-23-2015 09:12 AM
If you can copy and paste the full search history from each call that would reveal why the failed call is hitting the default zone.
09-24-2015 12:32 AM
Hi again!
Ok, i copy the search history:
Well call (from sx10 codec to external uri):
Bad call (from jabber codec to external uri):
Regards!!!
09-25-2015 08:41 AM
Something odd is going on here. It looks like Jabber is still trying to make this call as an MRA call.
Try adding a SIP Route Pattern (domain pattern) in CUCM for externaldomain.es and point it at your 5560 B2B SIP Trunk to Expressway. Then restart Jabber and try the call again. If it does not succeed please post the search history again.
09-28-2015 03:14 AM
Hi,
It seems to work...I configured the sip route patter to external domain and worked properly. After that I deleted the sip route patter again and I called back again and also worked ... I don´t understand anything...
I´m going to test everything again and to make more test.
Thanks for your help!!!
Regards!
10-02-2015 02:56 PM
Once the pattern was deleted it should not have worked, that is a little odd. Did you reset the SIP Trunk after deleting the pattern? Give that a shot and see if it makes a difference.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide