Acme Packet (MOSC)

MOSC Banner

How SBC handle Contact IP in 200OK with loose routing and strict routing

edited Aug 28, 2014 5:52PM in Acme Packet (MOSC) 1 commentAnswered

Hi folks,

 

For example, my SBC SIP interface is 1.1.1.1 and SA's IP is 2.2.2.2. So when a SIP call is sent from SBC to SA, e.g. INVITE, TRYING, RINGING, then 200OK

 

In the 200OK sent from 2.2.2.2 to 1.1.1.1, I find out

 

Contact: <sip:6901@cisco.com;gr=urn:uuid:e0257bb0-ef9b-5957-9807-7633ea326048>;isfocus;x-cisco-tip;x-cisco-multiple-screen=3             ---> yes, there is not ">" at the end.

 

Record-Route: <siproxy-call-id=9a11c2cf-bada-4a4b-bd22-e75b2938a8ff@2.2.2.6:5061;transport=tls;lr>

Record-Route: <siproxy-call-id=9a11c2cf-bada-4a4b-bd22-e75b2938a8ff@2.2.2.6:5060;transport=tcp;lr>

 

So my question is, how SBC reply ACK and where the ACK send to?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center