05-20-2015 02:19 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
02-22-2016 03:28 AM
Hi Jad,
Did you ever solve this?
--Paul
08-08-2016 10:15 PM
Hi,
was there a solution for this issue. I have the same problem on an MRA deployment with 11.5 CUCM
09-22-2016 06:58 AM
Did anyone ever find a solution?
11-02-2016 07:56 PM
Hello,
We are having the same Expressway MRA calling issue with CUCM version 11. Seeing the Response Code 487. Did anyone ever figure this out?
Thanks. Jordan
09-28-2016 09:44 AM
Same here, did anyone ever find the answer?
06-29-2016 08:03 AM
Hi!
I have the same issue happening on my MRA deployment did you figured out how to solve it?
11-07-2018 11:42 PM
Hi, Did anyone solve the problem ?
04-21-2020 08:41 PM
Did anyone find a resolution for this issue? I have a few users not all that can receive inbound calls and make outbound calls when connected to the VPN. These same users can make outbound calls but can't receive inbound calls when calls route through the internet. I get the 487 request terminated error message.
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