Acme Packet (MOSC)

MOSC Banner

Ever-changing SDP in re-Invite

in Acme Packet (MOSC) 6 commentsAnswered ✓

Hi,

I got the following scenario:

UA sets up a SIP call with the SBC, then every 3min, in accordance with the timer expansion, sends a re-invite.

The the SDP in the re-invites are identical with one exception, the o= parameter.

The <sess-id> and the <sess-version> are incremented with every re-Invite although all the other SDP parameters remain the same.

example:

1st re-Invite o=- 127 127 .....

2nd re-invite o=- 128 128 ...

3rd re-invite o=- 129 129 ...

Question: shouldn't the <sess-id> and the <sess-version> remain unchanged as there are no changes to the rest of the parameters ?

The above result in that that after every such re-invite the following parameters in the RTP stream from the SBC to the UA are initialized:

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