Acme Packet (MOSC)

MOSC Banner

How to force SBC to convert INFO into RFC2833?

in Acme Packet (MOSC) 3 commentsAnswered

Hello fellows.

I met a problem: DTMFs do not work when sent in direction from called to calling party. Called party sends DTMFs in out-of-band mode, as INFO methods, although both calling and called party support RFC2833. Since pt 101 is presented on both sides of SBC the condition for INFO/RFC2833 conversion is not met, so SBC simply forwards INFO methods from B to A. Calling party does not support INFO method and rejects it with 488.

I wonder is there any additional option to force SBC to convert INFOs into RFC2833 if INFO method is not supported on one call leg?

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