I've got an application that doesn't seem to work well with DTMF coming in (supposedly using rfc2833) from some phones - notably Samsung S3s. I have told my carrier to use rfc2833. I have put dtmf-type="rfc2833" into my SIP profile. I see "a=fmtp:101 0-16" in the session progress message I was wondering what this message "Activate Buggy RFC2833 Mode" means! When a normal user hits a DTMF key, we get this in the log: 2013-07-25 13:26:19.308267 [DEBUG] switch_rtp.c:3917 RTP RECV DTMF 1:744 2013-07-25 13:26:19.308267 [DEBUG] switch_channel.c:471 RECV DTMF 1:744 Does this all indicate that rfc2833 is working?! Anyone else had trouble with S3s?
RTP RECV DTMF is indeed the log when an RFC 2833 DTMF is received. On Thu, Jul 25, 2013 at 9:33 AM, Alex Lake <alex@digitalmail.com> wrote:
I've got an application that doesn't seem to work well with DTMF coming in (supposedly using rfc2833) from some phones - notably Samsung S3s.
I have told my carrier to use rfc2833. I have put dtmf-type="rfc2833" into my SIP profile.
I see "a=fmtp:101 0-16" in the session progress message
I was wondering what this message "Activate Buggy RFC2833 Mode" means!
When a normal user hits a DTMF key, we get this in the log:
2013-07-25 13:26:19.308267 [DEBUG] switch_rtp.c:3917 RTP RECV DTMF 1:744 2013-07-25 13:26:19.308267 [DEBUG] switch_channel.c:471 RECV DTMF 1:744
Does this all indicate that rfc2833 is working?!
Anyone else had trouble with S3s?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
The model of cellphone should be irrelevant for these types of issues. However, different cellular networks handle DTMF differently. If you see different results with different phones, is it because they are on different networks. Regards, Steve On 07/25/2013 09:33 PM, Alex Lake wrote:
I've got an application that doesn't seem to work well with DTMF coming in (supposedly using rfc2833) from some phones - notably Samsung S3s.
I have told my carrier to use rfc2833. I have put dtmf-type="rfc2833" into my SIP profile.
I see "a=fmtp:101 0-16" in the session progress message
I was wondering what this message "Activate Buggy RFC2833 Mode" means!
When a normal user hits a DTMF key, we get this in the log:
2013-07-25 13:26:19.308267 [DEBUG] switch_rtp.c:3917 RTP RECV DTMF 1:744 2013-07-25 13:26:19.308267 [DEBUG] switch_channel.c:471 RECV DTMF 1:744
Does this all indicate that rfc2833 is working?!
Anyone else had trouble with S3s?
Interesting idea, but I don't think so. Will check...
The model of cellphone should be irrelevant for these types of issues. However, different cellular networks handle DTMF differently. If you see different results with different phones, is it because they are on different networks.
Regards, Steve
On 07/25/2013 09:33 PM, Alex Lake wrote:
I've got an application that doesn't seem to work well with DTMF coming in (supposedly using rfc2833) from some phones - notably Samsung S3s.
I have told my carrier to use rfc2833. I have put dtmf-type="rfc2833" into my SIP profile.
I see "a=fmtp:101 0-16" in the session progress message
I was wondering what this message "Activate Buggy RFC2833 Mode" means!
When a normal user hits a DTMF key, we get this in the log:
2013-07-25 13:26:19.308267 [DEBUG] switch_rtp.c:3917 RTP RECV DTMF 1:744 2013-07-25 13:26:19.308267 [DEBUG] switch_channel.c:471 RECV DTMF 1:744
Does this all indicate that rfc2833 is working?!
Anyone else had trouble with S3s?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2242 / Virus Database: 3204/6020 - Release Date: 07/25/13
ooh! You're right.... Samsung S2 on Three fails 100% but put a T-Mobile sim in there and it works 100%... But you can *hear* tones, so I wonder what's going on?
The model of cellphone should be irrelevant for these types of issues. However, different cellular networks handle DTMF differently. If you see different results with different phones, is it because they are on different networks.
Regards, Steve
On 07/25/2013 09:33 PM, Alex Lake wrote:
I've got an application that doesn't seem to work well with DTMF coming in (supposedly using rfc2833) from some phones - notably Samsung S3s.
I have told my carrier to use rfc2833. I have put dtmf-type="rfc2833" into my SIP profile.
I see "a=fmtp:101 0-16" in the session progress message
I was wondering what this message "Activate Buggy RFC2833 Mode" means!
When a normal user hits a DTMF key, we get this in the log:
2013-07-25 13:26:19.308267 [DEBUG] switch_rtp.c:3917 RTP RECV DTMF 1:744 2013-07-25 13:26:19.308267 [DEBUG] switch_channel.c:471 RECV DTMF 1:744
Does this all indicate that rfc2833 is working?!
Anyone else had trouble with S3s?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2242 / Virus Database: 3204/6020 - Release Date: 07/25/13
And just for clarification, what do I have to do to get inband DTMF working? I know that I have to do the "start-dtmf" thing, but do I have to change anything in the SIP profile to encourage originating networks not to try anything clever?
This is from the default.xml file: <!-- This is an example of how to auto detect if telephone-event is missing and activate inband detection --> <condition field="${switch_r_sdp}" expression="a=rtpmap:(\d+)\stelephone-event/8000" break="never"> <action application="set" data="rtp_payload_number=$1"/> <anti-action application="start_dtmf"/> </condition> -Avi On Fri, Jul 26, 2013 at 2:05 PM, Alex Lake <alex@digitalmail.com> wrote:
And just for clarification, what do I have to do to get inband DTMF working? I know that I have to do the "start-dtmf" thing, but do I have to change anything in the SIP profile to encourage originating networks not to try anything clever?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
This will amuse some of you.... I found the answer to my problem was that we hadn't actually answered the phone call! So when the IVR launched, it did a "pre-answer" (whatever that is) which seemed to work, but it wasn't very good at detecting DTMF. Putting an answer action in solved the problem.
Oh. I think it's written somewhere on the wiki that DTMF during pre_answer is unpredictable, it sometimes works and sometimes doesn't... -Avi
Depends on the carrier, FreeSWITCH itself has no issues with it.. some/many carriers block it to avoid people running ivrs before answer to avoid toll charges. On Sep 12, 2013, at 1:04 PM, Avi Marcus <avi@avimarcus.net> wrote:
Oh. I think it's written somewhere on the wiki that DTMF during pre_answer is unpredictable, it sometimes works and sometimes doesn't... -Avi
Interesting! I always thought that pre-answer was B->A audio path only, and often didn't work on mobiles at all. On 12/09/2013 18:28, Michael Jerris wrote:
Depends on the carrier, FreeSWITCH itself has no issues with it.. some/many carriers block it to avoid people running ivrs before answer to avoid toll charges.
On Sep 12, 2013, at 1:04 PM, Avi Marcus <avi@avimarcus.net> wrote:
Oh. I think it's written somewhere on the wiki that DTMF during pre_answer is unpredictable, it sometimes works and sometimes doesn't... -Avi
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2242 / Virus Database: 3222/6160 - Release Date: 09/12/13
AT&T in the US is a classic offender. For example, call their conferencing service at 800-232-1234. You've got to get through at least one level of digit-pressing before the call actually connects. Sometimes several. - Jeff On Thu, Sep 12, 2013 at 4:11 PM, Alex Lake <alex@digitalmail.com> wrote:
Interesting! I always thought that pre-answer was B->A audio path only, and often didn't work on mobiles at all.
On 12/09/2013 18:28, Michael Jerris wrote:
Depends on the carrier, FreeSWITCH itself has no issues with it.. some/many carriers block it to avoid people running ivrs before answer to avoid toll charges.
On Sep 12, 2013, at 1:04 PM, Avi Marcus <avi@avimarcus.net> wrote:
Oh. I think it's written somewhere on the wiki that DTMF during pre_answer is unpredictable, it sometimes works and sometimes doesn't... -Avi
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2242 / Virus Database: 3222/6160 - Release Date: 09/12/13
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
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
The carriers pretty much had to do this. Back when IVR meant PC + Dialogic card + SCO Unix + application it was very very easy to end up not actually answering the calls, especially when using T1RBS. Most people had no idea their app was not answering the calls until the telco complained. Regards, Steve On 09/13/2013 01:28 AM, Michael Jerris wrote:
Depends on the carrier, FreeSWITCH itself has no issues with it.. some/many carriers block it to avoid people running ivrs before answer to avoid toll charges.
On Sep 12, 2013, at 1:04 PM, Avi Marcus <avi@avimarcus.net> wrote:
Oh. I think it's written somewhere on the wiki that DTMF during pre_answer is unpredictable, it sometimes works and sometimes doesn't... -Avi
participants (6)
-
Alex Lake
-
Avi Marcus
-
Christopher Rienzo
-
Jeff Pyle
-
Michael Jerris
-
Steve Underwood