On Tue, 2010-02-16 at 19:56 -0600, Eric Varsanyi wrote: > > The issue was the Polycom default setting of 127 for > tone.dtmf.rfx2833Payload. There should be no problem (per the spec) > negotiating 127 and the SDP headers in the INVITE and the OK seem > correct (to my eye and wireshark's decoders concur), but it ends up > not working though voip.ms (or to a linksys SPA3102 FXO) reliably. > > If I override the default sipXecs setting of 127 to 101 voip.ms calls > work fine (and the SPA3102 FXO DTMF works as well). > > I have pcap traces (outside the firewall) showing the telephony events > being emitted correctly (at dynamic ID 127) by the polycom, they just > don't make it through voip.ms. > > I'd like to suggest it would be worth changing the default to '101' in > phone.xml in the polycom plugin just to avoid bogons with various > apparently broken implementations elsewhere. I have a patch for this > if there is interest.
That's worth filing an issue on... we should check with Polycom to see if there's a reason they've chosen that default. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
