Call Pilot 150 DTMF from AA 1

[LKev]

I know this problem has been run into the ground, but need someone to try to tie it all together.

Have a callpilot 150 version 2.1, From cell phones DTMF is hit and miss. Sometimes users get "invalid extension" or routed to the wrong extension because all of the digits were not handed off.

My question is on Nortel's site there is an updated firmware which is DSP....A8 I read the readme doc but it does not describe if the update cures the problem with Short tones(DTMF). What issues does this firmware upgrade address?

Is there a way to adjust the DTMF timing on the callpilot through the telset?

I know there are many postings dating back as far as 05 about this problem. Has anyone had this problem and did they use that firmware I mentioned above to cure the problem, or did they use another way like a telset programming adjustment.

Kevin

 

[gforce9]

Kevin,
A few things:

Nortel released an A6 patch, then A7, then A8 awhile later.......all supposing to help the DTMF issue. I haven't run into a DTMF issue in awile, so I can't speak directly to the A8's effectiveness. As for cell phones, digit recognition problems are not exclusive to Nortel or to Norstar; it is usually the signal strength at any particular milisecond or short tones on the cell phone itself. I remember DTMF issues back to the time of the 300lb Startalk 100's/330's of the late 80's/early 90's that doubled as extra weight in the trunk for winter driving. Which 2.1 s/w are you running; it was in 2.10.06.00 (or somewhere around there) that the A7 patch came out. Certainly loading A8 won't hurt anything. I know customers want cell phones to be as reliable as POTS, but that will probably never happen. I hope there is something in there that helps.

 

[LKev]

Thanks for the response G. Yeah the cell phones are becomming a real pain in the ass, and Caller ID. Just man up and answer the call or let it go to voicemail. I will give that firmware a try. I'll update the post when I get some result information. Thanks again.

Kevin

 

[curlycord]

I have same issue with 2.0.47
A8 update did not help.

Anyone figure this one out or is 3.1 known as the fix?

thanks


=----(((((((((()----=
curlycord

http://www.curlycord.com