Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Phones and DTMF issue

Status
Not open for further replies.

TheZCom

Programmer
Nov 2, 2005
122
US
Hello everyone. I have a IP 406v2 running 3.1(65) with 2 remote locations. Each remote location has 4 5610s without a local IPO. Voice quality is pretty good and customer is using a VPN to each remote site. However, IP Phone users cannot navigate an auto attendant, IVR, etc. For example, caller wants to enter an account number at a favorite shipping company, but DTMF does not seem to pass. I have tried G.711 and G.729 codecs with 'Out of Band DTMF' on and off (for each). Has anybody dealt with an issue like this? Any input would be greatly appreciated. Z
 
Check your codec set.... I had the same problem, untill I changed the codec sets under codec set 1 like so:

(The actual problem is some codec sets will can not process MOH, DTMF, etc...)

change ip-codec-set 1 Page 1 of 2

IP Codec Set

Codec Set: 1

Audio Silence Frames Packet
Codec Suppression Per Pkt Size(ms)
1: G.711MU n 2 20
2: G.729 n 2 20
3:
4:
5:
6:
7:


Media Encryption
1: none
2:
3:
 
Also, you may want to check out Tech bulletin 71, 3.2 GA.
The fix for CQ28193 references DTMF tones with IP Phones in certain situations not working.
You may want to upgrade your site and test.
 
have you upgraded the IP Phones? i had the same problem and it didnt matter wich codec or DTMF setting was used. upgrading the firmware on the phones fixed it for me. this was pre 3.2 so maybe that will fix it too.
 
The phones are using the firmware that is issued with the 3.1 (65) admin suite. I am considering upgrading to 3.2 (54). I will keep you all posted. Z
 
Yes, it is defenatly a 3.1 issue. I had the same problem only on ip hardphones. So Upgraded to 3.2.54 and issue is resolved.
 
I don't doubt that the problem would be fixed with an upgrade to 3.2(54). However, I removed a LCR entry (I only had one programmed) and that provided a temporary fix. I just thought I'd report the fix despite it sounding crazy. I'll upgrade this cusotmer down the road. Thanks for all of your replies! Z
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top