OBiTALK Community

General Support => On-Topic: Obihai and OBi Products => Topic started by: ChrisThompson on April 04, 2011, 12:59:16 PM

Title: Problems with DTMF tones
Post by: ChrisThompson on April 04, 2011, 12:59:16 PM
I'm having a problem with the OBI110 handling DTMF tones from my handset.  I noticed this today when I was calling into a conference call line and the line kept telling me the code was invalid.

At first I thought the problem was that I was calling through the Google Voice line, so I called back using **8 to dial through the POTS line (connected to MagicJack).  I watched the MagicJack screen as I dialed the number.  When I dialed, the OBI did send the correct number to the MagicJack to be dialed.  However, once the connection was made, when I pressed a key on the phone, the number didn't always show up in MagicJack.  If I use my phone to key in "123456789", the MagicJack shows it only recognized the keys "124679".

I know this isn't a problem with MagicJack, because I've been using it for years and have never had an issue with it not recognizing the DTMF tones from my handset when it's directly connected to the MagicJack.
Title: Re: Problems with DTMF tones
Post by: jimates on April 04, 2011, 04:13:38 PM
try it again only instead of pressing **8, press #. This should connect the handset directly to the line port (MJ) without the Obi in play.

Confirm it works ok like that then troubleshoot the Obi.
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on April 04, 2011, 04:29:09 PM
Okay. I tested by hitting #, waiting for the dial-tone and dialing the number.  During the dialing sequence, I can watch the numbers come up in the MJ interface just fine.  However, again, once the call is connected, only about 40% of the time does the dialed number show up in the MJ interface.

For example, I was dialing a room code (say 123456), I would have to push each number 1-6 times before it would show up in the MJ interface.  Once each number showed up, the conference call number recognized the correct room number.  In other words, I had to dial "11112233344566#" for the conference call number to recognize "123456#".

Further testing shows the same problem happens with dialing out over Google Voice on SP1, though I can't watch exactly what numbers are actually recognized.  Using the OBI test number (222-222-222), I can hear each DTMF tone as I press each number, but if I don't give sufficient time between each press, the tones won't play or they are cut off (a very short tone) or distorted.

With this new information in mind, I called back via MJ and found that if I left a 1.5-2 second delay between each number press, that the tone would get properly registered.

So it appears that the problem is that you cannot dial a numbers on a connected call without providing a full 2 second delay between each number.  This is a fairly serious issue for anyone that uses their phone to call services that request information dialed via tones.  A lot of support numbers request you enter your account number, last 4 SS#, telephone number, or other info on the phone.  With this issue, I can never be 100% certain that anything I've dialed has actually been recognized as a valid entry by the recipient.
Title: Re: Problems with DTMF tones
Post by: jimates on April 04, 2011, 04:37:57 PM
well, pressing # is supposed to be the equivalent of the phone plugged directly into the Line device (MJ).

I would send an email to support@obihai.com

link to this thread, include your obi number
Title: Re: Problems with DTMF tones
Post by: victorr on April 05, 2011, 10:39:55 PM
I have the same issue.
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on April 05, 2011, 10:48:51 PM
I sent an email to support and sent more detailed information.  I haven't heard back yet.
Title: Re: Problems with DTMF tones
Post by: LeftRight on April 06, 2011, 10:12:39 PM
One more test that you can do is to directly connect your phone to MJ. Are the digits easily recognized by MJ after call is connected?
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on April 07, 2011, 12:23:01 AM
I have been using the same phone with the same MagicJack for more than a year, and previous to that I had a different phone connected to the same MagicJack for at least 2 years.  DTMF tones work just fine when the phone is connected directly.

Note that the DTMF problem occurs when calling over Google Voice as well as using **8 or # to dial out over the Line port, so even taking MJ out of the equation the problem exists.  MJ softphone allows me to monitor how the port is recognizing the tones whereas with Google Voice I have no way of knowing what the other end is recognizing, so it's a good diagnostic tool.
Title: Re: Problems with DTMF tones
Post by: RonR on April 07, 2011, 12:02:21 PM
Just for clarification...

**8 and # do not give a hard-wired/physical connection between the OBi PHONE Port and LINE Port.  It's a bridged or logical connection, and I imagine audio, DTMF, etc. are still going through all the normal OBi components as usual.  I don't know, but it's possible DTMF is being decoded on the PHONE Port and regenerated on the LINE Port in this scenario.

You can get a hard-wired/physical connection between the OBi PHONE Port and LINE Port by removing power from the OBi.  There's a relay that drops out, forcing this connection for fail-safe purposes.
Title: Re: Problems with DTMF tones
Post by: LeftRight on April 07, 2011, 06:58:58 PM
As RonR said, power off OBi unit will give a physical connection between phone port and line through relay, so double check if you can get same DTMF performance as directly connecting your phone.

Dial # will bypass OBi unit, i.e., NO DTMF detection on the PHONE port and NO regeneration on the LINE port, though there is a A/D, D/A path, and you may tune channel RX/TX gain to see if that make a difference. Ideally, you should see same DTMF performance as you remove power from the OBi ...
Title: Re: Problems with DTMF tones
Post by: RonR on April 07, 2011, 07:13:51 PM
Quote from: LeftRight on April 07, 2011, 06:58:58 PMDial # will bypass OBi unit, i.e., NO DTMF detection on the PHONE port and NO regeneration on the LINE port ...

There is DTMF detection (but insufficient evidence to go out on a limb about DTMF regeneration) after dialing '#'.  SYSLOGing clearly shows the DTMF detection going on.
Title: Re: Problems with DTMF tones
Post by: ajayhere24 on April 12, 2011, 09:04:21 AM
I am having a similar issue too. If anyone figures out a solution to it, please do let me know.

thank you,
Ajay
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on April 12, 2011, 09:08:17 AM
I'm still having the problem.  I haven't yet tested it with the OBi unplugged.
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on May 02, 2011, 09:59:26 AM
With the OBI110 unplugged, dialing DTMF tones through the Line works just fine.  I really hope this is a software issue and not a hardware issue because I use my phone for conference calls almost every day and really need to be able to dial tones to enter the conference ID number.
Title: Re: Problems with DTMF tones
Post by: infounlim on May 02, 2011, 01:19:00 PM
Same issue here.
Title: Re: Problems with DTMF tones
Post by: Kaizer on May 04, 2011, 11:44:38 PM
i have obi with gv as sp1. i'm experiencing the same issue with using a calling card for international calls. obi via gv connects to the local call center. the other end has a hard time validating the pin that i must enter. a certain pause between each digit is required but i've only had 1 successful try.
Title: Re: Problems with DTMF tones
Post by: RonR on May 05, 2011, 08:42:42 AM
Kaizer,

It's been suggested that enabling the following setting may help:

Service Providers -> ITSP Profile x -> General -> X_UseFixedDurationRFC2833DTMF : (checked)
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on May 05, 2011, 09:53:00 AM
That setting is enabled on both my SIP accounts.
Title: Re: Problems with DTMF tones
Post by: RonR on May 05, 2011, 09:59:23 AM
The suggestion was originally made in the context of Google Voice DTMF problems, but I suspect it can't hurt to have it enabled in any case.

I haven't experienced any DTMF problems with either Google Voice or SIP providers and haven't found this setting to make a difference either way, but let's hope it helps Kaiser.
Title: Re: Problems with DTMF tones
Post by: earthtoobi on May 05, 2011, 06:20:42 PM
i used to have similar issues in the past especially when entering conference PIN number.
Making it to in-band DTMF solved my problems.

(Even after the above setting i have issues once in a  while when i type in PIN numbers real fast,but i don't consider it a problem.)
Title: Re: Problems with DTMF tones
Post by: obi-master on May 06, 2011, 10:15:24 AM
Having the same issue. Can Obi support comment on this
Title: Re: Problems with DTMF tones
Post by: Kaizer on May 06, 2011, 02:15:16 PM
Quote from: obi-master on May 06, 2011, 10:15:24 AM
Having the same issue. Can Obi support comment on this

I incorporated RonR's suggestion and :

Service Providers -> ITSP Profile x -> General -> DTMFMethod -> InBand

If you are on auto provisioning, uncheck obitalk settings, uncheck default then change to InBand

Working so far.
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on May 06, 2011, 02:17:30 PM
Unfortunately, this doesn't address the issue of DTMF tone issues when dialing out of the LINE port using **8 or #.
Title: Re: Problems with DTMF tones
Post by: OBiSupport on May 06, 2011, 02:58:23 PM
There are a couple of places where a DTMF tone can get lost or go undetected.  Here are a couple things to try if you are having issues getting DTMF tones to a far-end peer (VoIP and/or PSTN).

1.  Change the DTMF transmit method to in-band.
Service Providers > ITSP Profile X > General > DTMFMethod = InBand

2.  Increase the audio gain setting for audio (DTMF) generated by the phone attached to the OBi PHONE port.
Physical Interfaces > PHONE Port > Port Settings > ChannelRxGain = 5
The "5" recommendation is arbitrary. Find a setting that works for your environment. Setting this too high could result in the OBi caller hearing their echo and/or the far end experiencing audio cut-out or the OBi caller being just too plain loud.
Note:  Only applicable to DTMF tones when "InBand" signalling is invoked.

3. Increase the LINE port audio gain setting.
Physical Interfaces > LINE Port > Port Settings > ChannelTxGain = 5
Again, the "5" recommendation is arbitrary.

4. Increase the DTMF playback level on the LINE port.
This is for those cases where a call is being bridged from VoIP to the LINE port or the LINE port is the Primary Line to Call Out (or **8 is used to make a call from the OBi PHONE port or AA).
Physical Interfaces > LINE Port > Port Settings > DTMFPlaybackLevel = 0
The "0" recommendation is arbitrary.

Title: Re: Problems with DTMF tones
Post by: Kaizer on May 07, 2011, 12:54:33 AM
well i got ahead of myself. changing to inband resulted in cell phone calls to obi for 2 stage calling to break. AA does not recognize the DTMF (from sprint or verizon). so this:

Service Providers -> ITSP Profile x -> General -> X_UseFixedDurationRFC2833DTMF : (checked)

didn't help either.

I guess I'm left with only this option to play with?

2.  Increase the audio gain setting for audio (DTMF) generated by the phone attached to the OBi PHONE port.
Physical Interfaces > PHONE Port > Port Settings > ChannelRxGain = 5
The "5" recommendation is arbitrary. Find a setting that works for your environment. Setting this too high could result in the OBi caller hearing their echo and/or the far end experiencing audio cut-out or the OBi caller being just too plain loud.
Note:  Only applicable to DTMF tones when "InBand" signalling is invoked.
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on May 10, 2011, 11:36:52 AM
Here's what's going on from syslog when dialing via "#" direct to the line port. These tones are not always recognized by recipient:

May 10 12:24:26  [DSP]: ---- H/W DTMF ON (level:3) : 6 @ 209421 ms----
May 10 12:24:26  [DSP]: ---- H/W DTMF OFF @ 209551 ms ----
May 10 12:24:26  [DSP]: ---- H/W DTMF ON (level:3) : 6 @ 210071 ms----
May 10 12:24:26  [DSP]: ---- H/W DTMF OFF @ 210201 ms ----
May 10 12:24:28  [DSP]: ---- H/W DTMF ON (level:3) : 0 @ 211321 ms----
May 10 12:24:28  [DSP]: ---- H/W DTMF OFF @ 211451 ms ----
May 10 12:24:29  [DSP]: ---- H/W DTMF ON (level:3) : 5 @ 212821 ms----
May 10 12:24:29  [DSP]: ---- H/W DTMF OFF @ 212951 ms ----
May 10 12:24:29  [DSP]: ---- H/W DTMF ON (level:3) : 8 @ 213191 ms----
May 10 12:24:30  [DSP]: ---- H/W DTMF OFF @ 213321 ms ----
May 10 12:24:30  [DSP]: ---- H/W DTMF ON (level:3) : 1 @ 213591 ms----
May 10 12:24:30  [DSP]: ---- H/W DTMF OFF @ 213721 ms ----
May 10 12:24:30  [DSP]: ---- H/W DTMF ON (level:3) : 2 @ 213961 ms----
May 10 12:24:30  [DSP]: ---- H/W DTMF OFF @ 214091 ms ----


Here's what happens when dialing via Google Voice (SP1) with the "InBand" setting enabled.  These tones do appear to be recognized by the recipient:

May 10 12:25:57  RTP: Start->480ed57e:19295(80);0;0;0:0:0;1(42)
May 10 12:25:57  RTP: Skt Connected
May 10 12:25:58  RTP: PeerRflxAddr=480ed57e:19295
May 10 12:26:02  [DSP]: ---- H/W DTMF ON (level:3) : 6 @ 305990 ms----
May 10 12:26:02  [RTP] DTMF RFC -- dgt: 6, c_dgt:
May 10 12:26:02  [DSP]: ---- H/W DTMF OFF @ 306110 ms ----
May 10 12:26:04  [DSP]: ---- H/W DTMF ON (level:3) : 6 @ 307700 ms----
May 10 12:26:04  [RTP] DTMF RFC -- dgt: 6, c_dgt:
May 10 12:26:04  [DSP]: ---- H/W DTMF OFF @ 307830 ms ----
May 10 12:26:05  [DSP]: ---- H/W DTMF ON (level:3) : 0 @ 308870 ms----
May 10 12:26:05  [RTP] DTMF RFC -- dgt: 0, c_dgt:
May 10 12:26:05  [DSP]: ---- H/W DTMF OFF @ 309000 ms ----
May 10 12:26:07  [DSP]: ---- H/W DTMF ON (level:3) : 5 @ 310700 ms----
May 10 12:26:07  [RTP] DTMF RFC -- dgt: 5, c_dgt:
May 10 12:26:07  [DSP]: ---- H/W DTMF OFF @ 310830 ms ----
May 10 12:26:08  [DSP]: ---- H/W DTMF ON (level:3) : 8 @ 311420 ms----
May 10 12:26:08  [RTP] DTMF RFC -- dgt: 8, c_dgt:
May 10 12:26:08  [DSP]: ---- H/W DTMF OFF @ 311550 ms ----
May 10 12:26:08  [DSP]: ---- H/W DTMF ON (level:3) : 1 @ 312050 ms----
May 10 12:26:08  [RTP] DTMF RFC -- dgt: 1, c_dgt:
May 10 12:26:08  [DSP]: ---- H/W DTMF OFF @ 312180 ms ----
May 10 12:26:09  [DSP]: ---- H/W DTMF ON (level:3) : 2 @ 312730 ms----
Title: Re: Problems with DTMF tones
Post by: ChrisThompson on May 10, 2011, 11:50:55 AM
I applied the suggested settings by OBisupport and it does appear that DTMF tones are better recognized now.  I still get the occasional dropped number, especially when dialing quickly, but it works significantly better.
Title: Re: Problems with DTMF tones
Post by: AndyJ on May 11, 2011, 09:31:06 AM
It looks like something changed in the 1.2.1(2283) firmware. DTMF was actually working fine for me with the default settings before the upgrade, but is now very inconsistent after the upgrade. Sometimes it works, sometimes it doesn't (more often not).
Title: Re: Problems with DTMF tones
Post by: GC_convertee on May 13, 2011, 07:30:32 PM
Hi I have the same problem (but have had it sporadically with using SIP / Sipgate / GV before I had the obitalk too)
ie dialing into conference calls, etc

Once I hooked up the obitalk110, I tried to dial into the secondary google voice account configured, to muck around with the voicemail features-in GV's ivr menu, but Google Voice wouldn't recognize my PIN.

I have decent Panasonic cordless phones kx-tga939t
When I press and hold the buttons on the handset, the dtmf tone stays on as long as I press the button.
But when I listen on the other end (via a cellphone or something), it's only a short dtmf tone, no matter how long I hold down the panasonic buttons

So it seems that my cordless phone does really have press-and-hold-dtmf tones
1. Does anyone know of a dect cordless sys that has press and hold
2. Is there gain or other settings to increase the dtmf tones on the receiving end?

Note I've only configed the obitalk thru the web portal and not directly via web admin, I read they can conflict

Also I do not have a landline to test and the phone is hooked up correctly

Thanks
G
Title: Re: Problems with DTMF tones
Post by: haiml on May 18, 2011, 05:20:25 PM
try this  to test DTMF:
http://www.testcall.com/222-1111.html
Title: Re: Problems with DTMF tones
Post by: RonR on May 18, 2011, 05:41:44 PM
Quote from: haiml on May 18, 2011, 05:20:25 PM
try this  to test DTMF:
http://www.testcall.com/222-1111.html

If you have iNum calling configured, they also have a number that repeats your DTMF digits back :  883510000000092
Title: Re: Problems with DTMF tones
Post by: azrobert on May 21, 2011, 12:56:22 PM
My DTMF problem was on SP1/GV and started after installing Build 2283.  DTMF tones work perfectly on SP2/SipSorcery with the default settings.

Changing "ITSP Profile A/General/DTMFMethod=InBand" seemed to fix the problem until today when I called my cell phone number to listen to a voice message.  My cell phone provider failed to recognize any DTMF tones.

Changing "Phone Port/DTMRxMode=Software" fixed the problem with my cell phone.

It seems OBiHai's quality control is lacking.  They should do no harm when providing a firmware upgrade.
Title: Re: Problems with DTMF tones
Post by: slk23 on June 02, 2011, 11:23:33 AM

"Phone Port/DTMRxMode=Software" fixed the problem for me too.  I'm using a regular phone and not a cell phone.  It was working fine before the firmware update.

Quote from: azrobert on May 21, 2011, 12:56:22 PM
My DTMF problem was on SP1/GV and started after installing Build 2283.  DTMF tones work perfectly on SP2/SipSorcery with the default settings.

Changing "ITSP Profile A/General/DTMFMethod=InBand" seemed to fix the problem until today when I called my cell phone number to listen to a voice message.  My cell phone provider failed to recognize any DTMF tones.

Changing "Phone Port/DTMRxMode=Software" fixed the problem with my cell phone.

It seems OBiHai's quality control is lacking.  They should do no harm when providing a firmware upgrade.

Title: Re: Problems with DTMF tones
Post by: zoomin on June 04, 2011, 04:36:23 PM
Quote from: OBiSupport on May 06, 2011, 02:58:23 PM
There are a couple of places where a DTMF tone can get lost or go undetected.  Here are a couple things to try if you are having issues getting DTMF tones to a far-end peer (VoIP and/or PSTN).

1.  Change the DTMF transmit method to in-band.
Service Providers > ITSP Profile X > General > DTMFMethod = InBand

2.  Increase the audio gain setting for audio (DTMF) generated by the phone attached to the OBi PHONE port.
Physical Interfaces > PHONE Port > Port Settings > ChannelRxGain = 5
The "5" recommendation is arbitrary. Find a setting that works for your environment. Setting this too high could result in the OBi caller hearing their echo and/or the far end experiencing audio cut-out or the OBi caller being just too plain loud.
Note:  Only applicable to DTMF tones when "InBand" signalling is invoked.

3. Increase the LINE port audio gain setting.
Physical Interfaces > LINE Port > Port Settings > ChannelTxGain = 5
Again, the "5" recommendation is arbitrary.

4. Increase the DTMF playback level on the LINE port.
This is for those cases where a call is being bridged from VoIP to the LINE port or the LINE port is the Primary Line to Call Out (or **8 is used to make a call from the OBi PHONE port or AA).
Physical Interfaces > LINE Port > Port Settings > DTMFPlaybackLevel = 0
The "0" recommendation is arbitrary.




I'm having troubles dialing out on my land line (AT&T).

Only rarely a call goes through. Most of the times, I get a message from AT&T "Your call cannot be completed at this time."

I have the latest firmware and a unit reset to factory defaults. I did try to tinker with the settings suggested above, but still cannot get it to work consistently.

Is there anything that I can do to fine tune it? Any way to make DTMF tones longer? They seem to be too short compared to what my phone is putting out.

Thanks!
Title: Re: Problems with DTMF tones
Post by: RonR on June 04, 2011, 04:39:33 PM
Quote from: zoomin on June 04, 2011, 04:36:23 PM
Any way to make DTMF tones longer? They seem to be too short compared to what my phone is putting out.

Physical Interfaces -> Line Port -> DialDigitOnTime
Title: Re: Problems with DTMF tones
Post by: zoomin on June 04, 2011, 05:41:14 PM
Quote from: RonR on June 04, 2011, 04:39:33 PM
Quote from: zoomin on June 04, 2011, 04:36:23 PM
Any way to make DTMF tones longer? They seem to be too short compared to what my phone is putting out.

Physical Interfaces -> Line Port -> DialDigitOnTime


Great! And you know what? It actually did the trick!

I set DialDigitOnTime to 300 (was 200), and DialDigitOffTime to 50 (was 200).

Did 5 calls and all 5 went through fine!

So, if anyone else is having similar issue, I strongly recommend playing with these values. :)

Thanks, RonR!
Title: Re: Problems with DTMF tones
Post by: Dale on October 12, 2011, 12:58:04 PM
same problem here using GV.
I found that if i held down the numbers for longer it would work. I looked in vain for DialDigitOffTime in the Phone settings for an Obi100 but could not find that parameter.

Changed

Physical Interfaces -> PHONE -> PortDTMFRxMode to Software
an intitial test seemed better but the Rx suggests this is to do with receiving...
Now trying Service Providers > ITSP Profile X > General > DTMFMethod = InBand
Title: Re: Problems with DTMF tones
Post by: Dale on October 13, 2011, 08:56:43 AM
it helped, but again today I had to hold down the keys longer to get them to work...

is there a DialDigitOnTime  setting for the PHONE port?  (i cant see it)
Title: Re: Problems with DTMF tones
Post by: ShermanObi on October 13, 2011, 11:20:58 AM
@Dale
A software update may be the remedy.
Please dial ***6 from the phone attached to your OBi.
If there is a software update, press 1 and hand-up.
Your OBi will automatically download the latest firmware and restart.
This usually takes no more than 2 minutes.
Title: Re: Problems with DTMF tones
Post by: Dale on October 18, 2011, 12:12:35 PM
all my obi boxes are fully up to date.
Title: Re: Problems with DTMF tones
Post by: Dale on October 27, 2011, 11:06:04 AM
DTMF tones are not always working for me now today

Obi: 100
HardwareVersion   3.4      
SoftwareVersion   1.3.0 (Build: 2586)

Service Providers > ITSP Profile X > General > DTMFMethod = InBand
Physical Interfaces > Phone > DTMFRxMode = Software

I set
Physical Interfaces > PHONE Port > Port Settings > ChannelRxGain = 5
Physical Interfaces > PHONE Port > Port Settings > ChannelTxGain = 5

and first test worked. so I will see if this fix sticks...

is there a DialDigitOnTime  setting for the PHONE port?  (I cant see it)
Title: Re: Problems with DTMF tones
Post by: bob61 on March 16, 2012, 09:30:33 AM
Quote from: OBiSupport on May 06, 2011, 02:58:23 PM
There are a couple of places where a DTMF tone can get lost or go undetected.  Here are a couple things to try if you are having issues getting DTMF tones to a far-end peer (VoIP and/or PSTN).

1.  Change the DTMF transmit method to in-band.
Service Providers > ITSP Profile X > General > DTMFMethod = InBand

I'm using GV and this suggestion solved problem for me with dialing into office voice mail and conferences.  However I still have problem when dialing into Google Voice for my voicemail, GV doesn't recognize any of the tones (such as "*" to access main menu).  I've used the other suggestions in your message as well but has not resolved problem with GV system.  Any additional suggestions?

BTW, my box is current with latest update (from yesterday).

Thanks.
Title: Re: Problems with DTMF tones
Post by: Stewart on March 16, 2012, 10:34:35 AM
Quote from: bob61 on March 16, 2012, 09:30:33 AMHowever I still have problem when dialing into Google Voice for my voicemail, GV doesn't recognize any of the tones (such as "*" to access main menu).
Some users have reported that setting PHONE Port -> DTMFRxMode to Software and setting ITSP Profile X -> General -> DTMFMethod back to Auto (the default), solved all their DTMF woes. YMMV.
Title: Re: Problems with DTMF tones
Post by: bob61 on March 16, 2012, 11:37:49 AM
Quote from: Stewart on March 16, 2012, 10:34:35 AM
Quote from: bob61 on March 16, 2012, 09:30:33 AMHowever I still have problem when dialing into Google Voice for my voicemail, GV doesn't recognize any of the tones (such as "*" to access main menu).
Some users have reported that setting PHONE Port -> DTMFRxMode to Software and setting ITSP Profile X -> General -> DTMFMethod back to Auto (the default), solved all their DTMF woes. YMMV.
Thanks for the suggestion.  However it didn't help for my problem.   Pretty frustrating.
Title: Re: Problems with DTMF tones
Post by: SteveL on November 08, 2012, 04:09:23 AM
DTMF tones don't transmit for me on Sipgate. I'm using the default setup. For example, pressing *3 to forward the call or *5 to conference, does nothing.