05-19-2015 02:35 AM - edited 03-18-2019 04:30 AM
Hello Gents,
I am running into an issue with a deployment involving Mobile Remote Access using Expressway C & E.
In fact, Jabber clients on the outside network are registering correctly with the CUCM and can make calls to internal DNs with no problem. Here is the Expressway zone routing (Which is pretty standard for a MRA deployment):
EXP-E: CollaborationEdgeZone -> CollaborationEdgeZToTraversalSZ -> TraversalSubZone -> Zone003ToTraversalSZ -> Unified Communication Manager Zone
EXP-C: Unified Communication Manager Zone -> Zone004ToTraversalSZ -> TraversalSubZone -> Zone002ToTraversalSZ -> CEtcp-172.16.142.41
However, when calling from an internal DN (registered to CUCM) to a Jabber located on the outside network, I am getting a rejected call with response 487. It says it might be related to inter-working issues but I cannot see why.
The zone routing is as follows:
Call details from the Expressway-C:
Call information | |
---|---|
State | Disconnected |
Start time | 2015-05-19 11:02:44 |
End time | 2015-05-19 11:02:46 |
Duration | 2 seconds |
Tag | 1b86cd87-52b2-41f0-bab2-41230bdb3465 |
Serial number | 45b1c960-71c6-4e5f-968e-510cd880305d |
Type | Video |
Bandwidth | |
---|---|
Requested | 384 kbps |
Allocated | 384 kbps |
Route | CEtcp-172.16.142.41 -> Zone002ToTraversalSZ -> TraversalSubZone -> Zone004ToTraversalSZ -> Unified Communication Manager Zone |
Leg 1 | |
---|---|
Bandwidth node | CEtcp-172.16.142.41 |
Source alias 1 | sip:1111@172.16.142.41 (Url) |
Target alias 1 | sip:bd4de6b0-8f1e-c91c-215f-a84178316e91@10.113.50.157:51630;transport=tls (Url) |
Protocol | SIP |
Address | 172.16.142.41:5060 |
Transport | TCP |
Reason | Request Terminated |
Cause | 487 |
Leg 2 | |
---|---|
Bandwidth node | Unified Communication Manager Zone |
Target alias 1 | sip:1411@172.16.142.41 (Url) |
Protocol | SIP |
Address | PUBLIC_IP_EXPRESSWAY-E:7002 |
Transport | TLS |
Leg 3 | |
---|---|
Bandwidth node | Unified Communication Manager Zone |
Target alias 1 | sip:1411@172.16.142.41 (Url) |
Protocol | SIP |
Address | 172.16.146.36:5071 |
Transport | TLS |
Encryption type | None |
Session 1 | |
---|---|
Status | Replaced |
Media routed | True |
Call routed | True |
Participant 1 | Leg 1 |
Participant 2 | Leg 2 |
Bandwidth allocated | 0 kbps |
Bandwidth requested | 0 kbps |
Session 2 | |
---|---|
Status | Cancelled |
Media routed | False |
Call routed | True |
Participant 1 | Leg 1 |
Participant 2 | Leg 3 |
Bandwidth allocated | 384 kbps |
Bandwidth requested | 384 kbps |
Route | CEtcp-172.16.142.41 -> Zone002ToTraversalSZ -> TraversalSubZone -> Zone004ToTraversalSZ -> Unified Communication Manager Zone |
Call details from Expressway-E:
Call information | |
---|---|
State | Disconnected |
Start time | 2015-05-19 11:02:45 |
End time | 2015-05-19 11:02:49 |
Duration | 4 seconds |
Tag | 1b86cd87-52b2-41f0-bab2-41230bdb3465 |
Serial number | 0b3ee2f9-6655-41f7-a817-13e2414ab77b |
Type | Video |
Bandwidth | |
---|---|
Requested | 384 kbps |
Allocated | 384 kbps |
Route | Unified Communication Manager Zone -> Zone003ToTraversalSZ -> TraversalSubZone -> CollaborationEdgeZToTraversalSZ -> CollaborationEdgeZone |
Leg 1 | |
---|---|
Bandwidth node | Unified Communication Manager Zone |
Source alias 1 | sip:1111@172.16.142.41 (Url) |
Target alias 1 | sip:bd4de6b0-8f1e-c91c-215f-a84178316e91@10.113.50.157 (Url) |
Protocol | SIP |
Address | PUBLIC_IP_EXPRESSWAY-E:28208 |
Transport | TLS |
Encryption type | None |
Reason | Request Terminated |
Cause | 487 |
Leg 2 | |
---|---|
Bandwidth node | CollaborationEdgeZone |
Target alias 1 | sip:1411@172.16.142.41 (Url) |
Protocol | SIP |
Address | 146.185.36.95:48795 |
Transport | TLS |
Encryption type | None |
Session 1 | |
---|---|
Status | Cancelled |
Media routed | True |
Call routed | True |
Participant 1 | Leg 1 |
Participant 2 | Leg 2 |
Bandwidth allocated | 384 kbps |
Bandwidth requested | 384 kbps |
Route | Unified Communication Manager Zone -> Zone003ToTraversalSZ -> TraversalSubZone -> CollaborationEdgeZToTraversalSZ -> CollaborationEdgeZone |
I appreciate your help with this.
Regards,
Jad
05-29-2015 04:14 PM
Could you post an Event log from Expressway-E? Did you check if a firewall is properly configured?
06-01-2015 05:47 AM
The Event Log output is present in the post.
The firewall is properly configured as well.
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