[Freeswitch-users] SBC In-band DTMF

[support at ecn.net.au]

Yes, we read that and tried to set that when attempting multiple configurations (attempting to pass inband dtmf).

Currently we can't get Freeswitch in an SBC role to pass the inband in the media stream at all (see earlier email) - also having odd issues with start_dtmf when accessing Asterisk IVR's (again very odd).  the only difference we can see (between FS and our legacy openser) is the Invite pushed on the bleg on Openser included the fmtp:18 annexb=no directive (as per the telco's SDP to us); however on FS it doesn't forward these (and we can't seem to force FS to add these attributes to the SDP on the bleg).

Again the start_dtmf issues exists only in 1.2 and 1.3 FS , in the 1.0.6 the issue is not present (is this a bug possibly?)

Any ideas?

Kind Regards,

Mark

________________________________________
From: Paul Cupis [paul at cupis.co.uk]
Sent: Friday, 18 January 2013 8:26 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] SBC In-band DTMF

On Fri, Jan 18, 2013 at 01:57:36AM +0000, Steven Ayre wrote:
>      <param name="rfc2833-pt" value="0"/>
>
>    What're you hoping to do here? This sets the payload type value. 0 is a
>    valid pt. This won't disable it, it'll instead use the value 0. That
>    happens to be the one for G711, so if that codec is enabled you're just
>    going to get a conflict.

If the rfc2833-pt is set to a value <96 it is outside the allowed range
for dynamic payload negotiation and FS will not offer RFC2833 support
in the SDP.

ref: sofia_glue.c

Regards,