Acme Packet (MOSC)

MOSC Banner

Multiple early dialogue support

in Acme Packet (MOSC) 5 commentsAnswered

AP4600 running on 9.2

For an outgoing call there can be multiple early dialogue messages returned from remote side.

in some situations it is possible that remote side sends 183 session progress with SDP defining codec X and then second 183 session progress with SDP defining codec Y.

This happens when remote side has 2 possible destinations for the call (ie, 2 devices with different capabilities).

the second 183 session progress has new tags, so it should be considered as second dialogue message for the same initial call.

SBC logs "missing transcoding resources" and drops the call.

Is it possible to set up configuration that would pass both 183 session progress messages through SBC and not attempt transcoding?

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center