Acme Packet (MOSC)

MOSC Banner

session-id

in Acme Packet (MOSC) 1 commentAnswered

SBC running 7.4, endpoint is replying to SBC with 100 trying and 180 ringing, but SBC thinks it never got a reply and keeps inviting. The only "different" thing I see in the 100 trying is a header Session-ID:


This is in the 100 trying:

Session-ID: 00000000000000000000000000000000;remote=1bbfcf46f902593d82a56a5772fe85cc 

Then the 180 shows:

Session-ID: 3318fdb4942104246f6f5fba34623402;remote=1bbfcf46f902593d82a56a5772fe85cc 

SBC does not provide session-ID on the invite out. Are these messing up the call flow? Can the SBC not correlate the 1xx messages because of the session-IDs?

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