Acme Packet (MOSC)

MOSC Banner

SBC does not change sess-id in o line after SDP change

edited Jul 29, 2020 8:22AM in Acme Packet (MOSC) 1 commentAnswered ✓

Hi Guys,

I have the following problem:

SBC is using on the LAN side RTP, but on WAN side SRTP, so it adds the crypto line in SDP on INVITE requests.

Unfortunately, on session refresh reINVITEs, SDP does not change, but sdes profile is set to rekey on reinvites. So that means that SDP which is sending to WAN side has been changed, because of new crypto line.

As per RFC 4566 the sess-id in originator line must increase, when SDP changes.

In my case, SBC leaves the sess-id. The problem is, the the SIP EP on WAN side is looking in the sess-id part of o= line and ignores the new keys, which causes in broken RTP.

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