On Sep 9, 2008, at 2:02 PM, Daniel Melnechuk wrote: > > On Aug 25, 2008, at 11:58 PM, Daniel Melnechuk wrote: > >> On Aug 13, 2008, at 6:10 PM, Kristijan Vrban wrote: >> >>> hello, do you have DTMF inband (in audio)? activ in your ATA? >>> Disable it. >>> Try RTP (RFC2833) only. Any differences? >>> >>> Kristijan >>> >>> Daniel Melnechuk schrieb: >>>> Dear CallWeaver Users, >>>> >>>> Had a Linksys PAP2T-NA ATA which started putting loud beeps into >>>> the >>>> incoming and outgoing sound channels. Not every call, and seemingly >>>> random as to when it would start and how often they would be. Then >>>> it >>>> started saying "Transferring call" during my phone call and would >>>> drop >>>> the call i had. Then the PAP2T died completely. >>>> >>>> While the PAP2T was getting funky before it died, i went back to >>>> using >>>> a softphone (X-Lite). Absolutely no beeps or transfers. It was >>>> then i >>>> suspected the PAP2T. I had also updated to the latest release of CW >>>> 1.2.0.1 but that did not help. >>>> >>>> After the PAP2T died, i figured it was just the PAP2T. So it was in >>>> warranty and i got it replaced with a SPA2102 that also does T.38 >>>> (my >>>> sip service provider is adding T.38). >>>> >>>> Not more than a few calls after configuring the SPA2102, it started >>>> to >>>> beep too; randomly on some calls, etc. I have not gotten the >>>> "transferring call" thing yet. >>>> >>>> And all during this time, calls with softphones on multiple >>>> computers >>>> do NOT get any beeps of this kind at all. >>>> >>>> The only configuration to the SPA2102 other then setting IP >>>> address, >>>> account, IP of callweaver, is that i have changed is the length and >>>> patterns of the distinctive rings (it has 9 of them). I set which >>>> ring >>>> pattern i want in the SIP header based on incoming calls by setting >>>> var ALERT_INFO before dialing an extension. >>>> >>>> Questions: >>>> >>>> 1. Has anyone experienced this problem of getting beeps with >>>> Linksys >>>> SPA2102 or PAP2T in use with Callweaver? >>>> >>>> 2. Does anyone have any idea why the SPA2102 could be making these >>>> beeps? >>>> >>>> Any thoughts appreciated. >>>> >>>> Peace, >>>> Dan >> > >> Hi Kristijan! >> >> Yes, i had the DTMF set to "AUTO" in ATA which would let it try >> whatever it wants i guess. I set it to just RTP and almost completely >> has cured the beeps. Thank you! >> >> Since you responded, i have heard beeps just once and my partner has >> once got the "Transferring Call" and then dropped phone call. I am >> going to test turning off features in the ATA to see if that goes >> away >> too. Since the problem only happens on the analog phones and ATA (and >> not softphones) the problem must be there... >> >> Thanks again. I'll report back about "Transferring call" and if >> successful in not having that happen again. Of course waiting for >> something not to happen can take a while! >> >> Peace, >> Dan > > Ok, so the beeps are still there after setting to use AVT(RTP) for in > the SPA2102. But then i found this link: > > > http://www.dslreports.com/forum/r20613336-Linksys-SPA2102R-Firmware-Update-525 > > that talked about firmware 5.2.5 and that a setting had changed to > help with random beeps (yay!): > > DTMF strict mode did not stop all “talk-off” beeps. Now the signal > level threshold for qualifying DTMF digits is set higher to prevent > false DTMF detection. (CSCso34152) > NOTE: The recommended settings for AVT transmission are as follows: > DTMF Tx Method: AVT > DTMF Tx Mode: Strict > DTMF TX Strict Hold Off time: 70 > > So i checked and long story short, i already have version 5.2.5 of > firmware but my "DTMF TX Strict Hold Off time" was set to 40. So i set > it to 80 (not 70) ms to make sure i don't get beeps anymore. With > small amount of testing it is looking good. Will report back if beeps > come back and what else i have tried. > > Peace, > Dan
Happy to report that all beeps are gone with the "DTMF TX Strict Hold Off time" set to 80 in my SPA2102. I might try relaxing to 70 but as they say, don't fix what isn't broken, and better is the enemy of good. But i just can't keep wondering if 10 ms makes a difference. What is interesting about this all is that the detection circuits trying to listen for DTMF on the analog line in the SPA2102 are detecting the dual frequencies needed when the analog phone buttons were not being touched. Is it the case that human speech generates enough frequencies and presumably long enough (40 ms) tones to be interpreted as DTMF? Or was there some noise on the line? In either case, it is interesting to note that i didn't get as many random beeps as did my partner on her line. And also interesting is that many of the beeps were only heard by the caller on the other end of the line. Anyway, SPA2102 works without beeps now and i can get on to testing T. 38 with the SPA2102. My sip provider tsgglobal.com (talklite.net was my provider previously but merged with them) has outgoing T.38 already but DIDs from Level3 are being reconfigured to support T.38 (which i have) "soon" while DIDs from Global Crossing (which i don't have) already have T.38. Will report back about that later on SPA2102 and CallWeaver. The above in no way constitutes an endorsement of tsgglobal.com, just relating facts in regards to T.38 availability in case anyone is looking for T.38 sip provider. Again, i have not tested with them yet for T.38 with SPA2102 and CallWeaver. Peace, Dan _______________________________________________ Callweaver-users mailing list Callweaver-users@callweaver.org http://lists.callweaver.org/mailman/listinfo/callweaver-users
