Hi,
Thank you for your reply Kristian.
I actually spent couple of hours with a tech support person from Broadvox.
He recommended that I use 'rfc2833' for 'dtmf-type' since that was most reliable one. Then he was capturing traffics going in and out of my trunk and verified that signal were sent from Broadvox trunk in the same way for both AT&T and T-Mobile. I believed him since when I click from my T-Mobile cell phone, he could tell me which numbers I click when my FS was either not getting any or getting only some digits.
Thing I really don't understand is that it really works perfectly fine when I call the FS from T-Mobile, but it does not when FS calls T-Mobile.
Does anyone know if there is any configuration I can change to control this?
For Kristian : I think I can get the SIP + RTP capture using WireShark. Can you help me if I send you the capture file?
Best regards,
Phil Kim
-----Original Message-----
From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Kristian Kielhofner
Sent: Monday, October 03, 2011 12:07 PM
To: FreeSWITCH Users Help
Subject: Re: [Freeswitch-users] DTMF Problem with T-Mobile carrier
Phil,
Broadvox is known to do quite a few things that can affect DTMF
handling in non-straightforward ways. This isn't a criticism of
Broadvox, it's just very common for carriers mixing upstreams
(especially when using Sonus).
How far have you debugged this with Broadvox? At minimum you'll
probably need a full SIP+RTP capture of the incoming call (especially
RFC2833 events) for anyone to help.
On Mon, Oct 3, 2011 at 10:33 AM, Phil Kim <phil.kim at valiant.com> wrote:
> Hello everybody,
>
>
>
> I really need some help here!
>
>
>
> I'm trying to use FS for making both inbound and outbound calls through
> Broadvox.
>
> Everything works perfectly except one particular situation with DTMF
> problem.
>
> In case of inbound calling (I'm calling FS), everything works fine. Call
> connects and I can send DTMF to FS and FS recognized those 100% (Testing
> with softphone from my desktop, SIP phone in the office, and all wireless
> carriers)
>
> However, I am having trouble with outbound calling. I have set it up to
> where FS makes an outbound call to certain number and once the call is
> answered, we start playing some custom IVR.
>
> Here, it works fine with softphone from my desktop, SIP phones in the
> office, AT&T, and Verizon. But for some reason FS will not recognize the
> DTMF coming from T-Mobile cell phones.
>
> Anyone has any idea? Below are my current setting from external.xml which
> was recommended by Broadvox.
>
>
>
> <param name="codec-prefs" value="PCMU,G729"/>
>
> <param name="dtmf-type" value="rfc2833"/>
>
> <param name="auto-rtp-bugs" value="clear"/>
>
> <param name="pass-rfc2833" value="true"/>
>
> <param name="inbound-late-negotiation" value="true"/>
>
>
>
> <param name="sip-trace" value="no"/>
>
> <param name="sip-capture" value="no"/>
>
> <param name="rfc2833-pt" value="101"/>
>
> <param name="sip-port" value="$${external_sip_port}"/>
>
> <param name="dialplan" value="XML"/>
>
> <param name="context" value="public"/>
>
> <param name="dtmf-duration" value="1000"/>
>
> <param name="inbound-codec-prefs"
> value="$${global_codec_prefs}"/>
>
> <param name="outbound-codec-prefs"
> value="$${outbound_codec_prefs}"/>
>
> <param name="hold-music" value="$${hold_music}"/>
>
> <param name="rtp-timer-name" value="soft"/>
>
>
>
>
>
>
>
> Best regards,
>
>
>
> Phil Kim
>
>
>
> The information contained in this e-mail message, and any attachment
> thereto, is the property of Valiant and is confidential and may not be
> disclosed without our express permission. If you are not the intended
> recipient or an employee or agent responsible for delivering this message to
> the intended recipient, you are hereby notified that you have received this
> message in error and that any review, dissemination, distribution or copying
> of this message, or any attachment thereto, in whole or in part, is strictly
> prohibited. If you have received this message in error, please immediately
> notify us by telephone, fax or e-mail and delete the message and all of its
> attachments.
>
> Thank you.
>
> Every effort is made to keep our network free from viruses. You should,
> however, review this e-mail message, as well as any attachment thereto,
> for viruses. We take no responsibility and have no liability for any
> computer virus which may be transferred via this e-mail message.
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
--
Kristian Kielhofner
FreeSWITCH-users mailing list
FreeSWITCH-users at 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 information contained in this e-mail message, and any attachment
thereto, is the property of Valiant and is confidential and may not be
disclosed without our express permission. If you are not the intended
recipient or an employee or agent responsible for delivering this message to
the intended recipient, you are hereby notified that you have received this
message in error and that any review, dissemination, distribution or copying
of this message, or any attachment thereto, in whole or in part, is strictly
prohibited. If you have received this message in error, please immediately
notify us by telephone, fax or e-mail and delete the message and all of its
attachments.
Thank you.
Every effort is made to keep our network free from viruses. You should,
however, review this e-mail message, as well as any attachment thereto,
for viruses. We take no responsibility and have no liability for any
computer virus which may be transferred via this e-mail message.