| Asset ID: |
1-72-1936542.1 |
| Update Date: | 2016-10-31 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1936542.1
:
Phone Number Being Stripped From A Call URI
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
|
In this Document
Created from <SR 3-9706261471>
Applies to:
Acme Packet 4500 - Version S-Cx6.0.x to S-Cz7.2.0 [Release S-Cx6.0 to S-Cz7.0]
Information in this document applies to any platform.
Symptoms
The phone number in the URI request header is being stripped by the SBC and we cannot determine why.
Example:
Incoming URI from 10.251.1.5 to peer-interface 172.27.33.93 (realm access-cale) - INVITE sip:6232291600@172.27.33.93:5060 SIP/2.0
Outgoing URI from the SBC core interface 216.27.193.87 (realm core-cale) to our call server 216.27.193.70 - INVITE sip:vas1.phx1.voip.tnltd.net:5060 SIP/2.0
The number 6232291600 is being stripped from the request causing our call to fail. This only happens to calls from 10.251.1.5, which has a session-agent configured. Calls from the other session-agents in realm access-cale do not exhibit this behavior.
I've attached a packet capture along with acme logs including a support-info.
Cause
strict routing in route header sent to sbc
sip rfc:
A proxy is said to be strict routing if it follows the Route processing rules of RFC 2543 and many prior work in progress versions of this RFC. That rule caused proxies to destroy the contents of the Request-URI when a Route header field was present. Strict routing behavior is not used in this specification, in favor of a loose routing behavior.
Solution
Customer can opt to send the route header with loose routing.
i.e.:
instead of
Route: <sip:172.27.33.93:5060>
the header is lr:
Route: <sip:172.27.33.93:5060;lr>
OR
Can remove the route header (before sending to SBC)
OR
Or on SBC, in sip-interface, the option strip-route-headers can be applied
OR
The other option would be to apply an HMR to Session Agent , if the strip-route-headers cannot be applied to sip-interface
HMR would look something like:
sip-manipulation
name StripRoute
description
header-rule
name StripOurRoute
header-name Route
action delete
comparison-type case-sensitive
match-value
msg-type request
new-value
methods
References
<NOTE:1589489.1> - How to Capture all Log Files on Acme Packet 3800 or 4500
Attachments
This solution has no attachment
