Why use INFO when it's only method I know Cisco won't speak (2833, kpml, sub/notify)?

Here's the CME snippet for FS trunk I have. FS sends 2833 tones to CME btw.

dial-peer voice 100 voip
 description ** TO FS **
 destination-pattern .T
 b2bua
 session protocol sipv2
 session target sip-server
 session transport udp
 dtmf-relay rtp-nte
 codec g711alaw
 no vad




On Mon, May 23, 2011 at 4:07 AM, Mike Taylor <mtaylor@employees.org> wrote:
Hi,

This is driving me nuts. 
I have a Cisco CME (a few actually) where I cannot get DTMF to work.

Does someone happen to have the magic recipe of SIP/Dialplan profiles and Cisco config to make DTMF <relay> work?

I spent several very very painful days trying to get RFC2833 to work, using FS to try and generate the tones itself. I ended up with all sorts of codec mismatches, delay,distortion and some really mangled DTMF tones…

So, now I'm back to;

PSTN----CiscoGW----<external>----FS----<internal>----<CUST PABX>---Phone

Where <CUST PABX> is 3 CMEs that won't talk DTMF
30+ other vendor's gateway's that WILL do DTMF…

Context External and internal are both set to dtmf-type info (or dtmf_type info) 

DTMF works FROM the Cisco GW towards our network, doesn't 


So, does anyone have a magic solution?
 Because Cisco TAC say they see DTMF being sent (as rtp-nte), when I need INFO or in-band.



Thanks,
Mike

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org