Acme Packet (MOSC)

MOSC Banner

The case of the missing 200 OK...

edited Feb 26, 2013 6:35AM in Acme Packet (MOSC) 5 commentsAnswered

I have added a new trunk provider to our 3800, and have a strange problem.   An incoming call is properly established, (INVITE, 200 OK, ACK)  and then the PBX sends a re-INVITE message back to update some caller ID info.  Not a big deal, but the when the carrier replies, the SBC sees the 100 TRYING message, but not the 200 OK.   Call then times out and drops.

 

The carrier confirms they are sending the 200 OK, and the packet trace on the SBC interface (via remote capture-receiver) shows the 200 OK.   Wireshark identifies the 200 OK as part of the call in the VoIP tools.   Call-ID and CSEQ numbers look fine.   However, the SBC does not process the 200 OK, and the sipmsg.log and log.sipd do not even show it.  

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