Acme Packet (MOSC)

MOSC Banner

INFO - rfc2833 interworking issue

edited Aug 23, 2012 12:05PM in Acme Packet (MOSC) 1 commentAnswered ✓

Hi all,

 

we have a Huawei<->NN3800<->Avaya scenario.  We received DTMF in INFO messages from the Huawei and we wanted to receive only RFC2833 RTP in the Avaya Session Manager. To force the INFO-to-RFC2833 interworking, we set the rfc2833-mode to preferred. After this change the INFO kept being sent to the Avaya, which replied with a 415 Unsupported Media.

 

To prevent the SBC from sending the INFO besides the RFC2833 we were recommended to create an HMR to remove the INFO from the Allow header. We created the HMR below and it worked as expected,  no response sent to the Huawei contained "

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