Skip to main content
Participant
February 28, 2013
Question

Invalid DTMF mode

  • February 28, 2013
  • 1 reply
  • 1215 views

Hello,

I have upgraded my adobe server from Flash Media Gateway (4.5) to Adobe Media Gateway (5.0).

Since this upgrade, dtmf does not work the same.

When using Flash Media Gateway (and Server), an incoming call or outgoing call was able to send DTMF from FMS.

When using Adobe Media Gateway (and Server), only outgoing calls are able to send DTMF from FMS. Incoming calls are not able to send DTMF anymore.

Here an extract of the log when failure:

2013-02-28::15:48:18.365 DEBUG CALLLEG 5884 [LEG ID:4] - Read DTMF 1

2013-02-28::15:48:18.365 ERROR SIPLEG 5884 [LEG ID:3] - Invalid DTMF mode

This is very strange as the test protocol is exactly the same and the only change is the upgrade to Adobe Media Gateway (and Server). I did a configuration diff to see what is different.... and nothing is different except for adobe name instead of flash name.

When Adobe Media Gateway starts, I have the following logs

2013-02-28::15:20:45.526 DEBUG SIP 5828 DTMF Mode not set for profile sipPhone... setting it to rfc2833

2013-02-28::15:20:45.529 DEBUG SIP 5828 DTMF Mode not set for profile sipPhone2... setting it to rfc2833

2013-02-28::15:20:45.532 DEBUG SIP 5828 DTMF Mode not set for profile sipGateway... setting it to rfc2833

2013-02-28::15:20:45.532 DEBUG SIP 5828 DTMF Mode not set for profile sipVideoPhone... setting it to rfc2833

rfc2833 is the correct value but i do not have this warning with Flash Media Gateway.

Is there a way to change the DTMF mode value for a profile ?

Here an extract of the kind of code executed by the FMS (and AMS) to generate a DTMF :

var info = new Object();

info.type = "leg.message.type.dtmf";

info.data = "1";

application.legService.sendLegMessage(this.legID, info);

I have look into many forum and did not find the answer.

Do you have an idea ?

Thanks,

This topic has been closed for replies.

1 reply

Participant
March 22, 2013

The following logs

             2013-02-28::15:20:45.526 DEBUG SIP 5828 DTMF Mode not set for profile sipPhone... setting it to rfc2833

2013-02-28::15:20:45.529 DEBUG SIP 5828 DTMF Mode not set for profile sipPhone2... setting it to rfc2833

2013-02-28::15:20:45.532 DEBUG SIP 5828 DTMF Mode not set for profile sipGateway... setting it to rfc2833

2013-02-28::15:20:45.532 DEBUG SIP 5828 DTMF Mode not set for profile sipVideoPhone... setting it to rfc2833

are logged by AMG when ‘dtmfmode’ configuration is missing from sip.xml

The ‘dtmfmode’ config was added in sip.xml as part of FMG 4.5.2 and corresponding logs were added in case this config was missing or incorrect.

Setting the proper dtmfmode configuration for required ProfileIDs (as explained by following example) in sip.xml should resolve the problem of above logs.

<Sip>

     <Profiles>

          <Profile>

               <profileID> sipPhone </profileID>

               <userName>  </userName>

               <password> </password>

               <displayName> </displayName>

               <remoteSipHost> sip-phone-ip:5060 </remoteSipHost>

               <context> sipPhoneContext </context>

               <supportedCodecs>

                    <codecID> G711u </codecID>

               </supportedCodecs>

               <dtmfmode>rfc2833</dtmfmode>

          </Profile>

     </Profiles>

</Sip>