Acme Packet (MOSC)

MOSC Banner

SIP 513 Message Too Big becasue of message length

edited Apr 10, 2013 10:44PM in Acme Packet (MOSC) 1 commentAnswered ✓

 

The SBC generating error message "SIP 513 Message Too Big " for the INVITE it recieve from core which has multiple via & record routes. Noticed in the debug logs that message length exceeds. But after 16 attempt SBC accept the 17the message (same message lenth) and forward to the egress core. Question is, why SBC accept the 17th message, where is the message length configured ? How can I change message length to avoid 513 messages ?

 

The first message SBC reject with 513 is at

17:33:39:792

The last message SBC reject with 513 is at

17:33:42:405

SBC accepts the same INVITE and forward to the core at

17:33:42:527

 

Apr 10 17:33:42.408 [SIP] INVITE 1 process-req: length 6268 exceeds max of 6000

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