Acme Packet (MOSC)

MOSC Banner

Busy signaling on 183 Messages

edited Nov 4, 2014 3:51PM in Acme Packet (MOSC) 2 commentsAnswered ✓

Hello,

I would like to discuss about an scenario we are facing. Our customer is sending us 183 messages with 'Reason: Q.850; cause=17' instead of 486 message when the caller is busy. So, the SBC manage the 183 as a regular 183 Session Progress and pass it to the next hop, which acts in the same way as the SBC, keeping the call active far from release the call due to a busy user.

Is it normal to use a 183 message to do so? Customer told us they receive this message from a Gateway prior his PBX but we havent much info.
Could the SBC manage this message by its own means? For example, by answering it after its reception.

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