This is the second time I've run into this exact same class of problem so I thought it merited a post and/or JIRA if appropriate.
Making outbound calls from Polycom 650's and 335's to *some* target numbers via voip.ms result in either completely non working outbound DTMF or flakey DTMF; it seems to depend on the called party and or the route voip.ms chooses. 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. My environment: SVN 17896 designer build, Polycom 3.2.2 firmware on 650's and 335's. -Eric Varsanyi _______________________________________________ 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/
