10-22-2016 10:41 PM - edited 03-12-2019 10:24 AM
This feature isn't supported with Expressway MRA deployment
We deployed this feature with CUCM and CUP version 11.5.1.10000-4, and we found two limitations:
1. Jabber with Extend and Connect setup in CUCM is not able to add remote destinations via Jabber, when number was matching any translation pattern with '!' at the end, and Urgent priority UNCHECKED.
2. When we added remote destinations on the CUCM admin page, It was not visible on the client side. - Only the client can add remote destination for Extend and Connect.
Thanks for the summary, and the comparison.
Hi Karoly,
In relation to your first point - was this raised with Cisco at all?
I believe I'm hitting the same issue (I've raised with TAC / PDI team currently), but wondering if you could comment further - we are also not able to set the remote destination currently via Jabber client, unless it's the same number you've already set on the CUCM side (add / edit from client results in an 'unable to connect' error).
1. Jabber with Extend and Connect setup in CUCM is not able to add remote destinations via Jabber, when number was matching any translation pattern with '!' at the end, and Urgent priority UNCHECKED.
Hi Scott,
Yes, we had a TAC case about it. Based on it, we were hitting a bug CSCuv03102, and as there is no planned release to fix this issue, we had to use a translation pattern with urgent priority as a workaround.
In our case, we have not tried adding the same number on the CUCM and then on the Jabber client. We tested only from the client side.
Br,
Karoly
Is there still a cucm version where Extend and Connect works with Expressway MRA deployment ?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: