Calls completing but no audio

**GPM** · 05-13-2009 11:23 AM

I had exactly the same problem yesterday afternoon. After much testing, temporarily connecting the ATA directly to the DSL modem, re-connecting and re-booting router, changing servers it suddenly started working again. Ultimately nothing was changed in my set up. Last correspondence indicated that it probably was due to the outage reported yesterday.

**Xponder1** · 05-13-2009 11:29 AM

Originally Posted by GPM

I had exactly the same problem yesterday afternoon. After much testing, temporarily connecting the ATA directly to the DSL modem, re-connecting and re-booting router, changing servers it suddenly started working again. Ultimately nothing was changed in my set up. Last correspondence indicated that it probably was due to the outage reported yesterday.

Ya well I am still without service. They have made test calls. Nothing has changed at all about my setup. They suggested that running X-Lite might be the cause so I shut it down and still have the issue. Funny thing is I CAN hear audio IF I answer with X-Lite. The ATA has no audio on inbound calls only. Oh and I have already done the usual reboot the router ATA ect. What ever is wrong its not on my end.

I see you have an XLite client currently registered on our system.
It has been registered around 45 minutes. Did the call come in when Xlite was registered/signed-on? If so, I believe that XLite may have been the culprit.

So I shut down X-Lite and the problem remained.

We've noticed a ring abnormalcy but nothing really shot out to us when reviewing your SIP traces.
What I'll do is escalate your ticket over to our Seniors where the issue will be more thoroughly looked into. You can expect a followup shortly.

Guess we will see what happens.
In case you support folks need it.

Tracing route to central01.voipwelcome.com [67.228.251.106]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Access_Denied [192.168.10.1]
2 9 ms 8 ms 9 ms 10.33.128.1
3 14 ms 9 ms 9 ms COX-68-12-8-157-static.coxinet.net [68.12.8.157]

4 10 ms 7 ms 8 ms ge-7-0-1-mx02.mtc1.tul.ok.cox.net [68.12.18.246]

5 70 ms 9 ms 8 ms xe-0-3-0-dsr02.rd.tul.ok.cox.net [68.12.18.4]
6 42 ms 28 ms 23 ms dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
7 20 ms 32 ms 16 ms po-1.r02.dllstx09.us.bb.gin.ntt.net [129.250.2.1
54]
8 22 ms 16 ms 17 ms te2-1.cer02.dal01.dallas-datacenter.com [157.238
.224.70]
9 16 ms 15 ms 15 ms po1.dar02.dal01.dallas-datacenter.com [66.228.11
8.203]
10 16 ms 40 ms 17 ms po2.fcr04.dal01.dallas-datacenter.com [66.228.11
8.218]
11 17 ms 17 ms 18 ms central01.voipwelcome.com [67.228.251.106]

Trace complete.

Kind of feel helpless because I have no idea what to do to help resolve it.

EDIT- After 30 seconds it goes to a sound that sounds like a pots line left off the hook.
Also because of this thread http://forums.voipo.com/showthread.p...1976#post11976 I turned off simul ring and still have the issue.

**burris** · 05-13-2009 11:50 AM

My last caller-maybe 1 1/2 hours ago- had to call 3 times before I could hear them to continue the call..

**Xponder1** · 05-13-2009 11:50 AM

Originally Posted by burris

My last caller-maybe 1 1/2 hours ago- had to call 3 times before I could hear them to continue the call..

That is exactly what I have been waiting to hear thank you.

**Russell** · 05-13-2009 06:49 PM

Originally Posted by burris

My last caller-maybe 1 1/2 hours ago- had to call 3 times before I could hear them to continue the call..

Since Tim asks if anyone else is having issues and I don't believe I saw a follow-up to Burris' issue, can I assume that it's fixed? Since I experienced something similar a couple of days ago, I'm most curious as to how Burris' issue was resolved.

**burris** · 05-13-2009 07:37 PM

Originally Posted by Russell

Since Tim asks if anyone else is having issues and I don't believe I saw a follow-up to Burris' issue, can I assume that it's fixed? Since I experienced something similar a couple of days ago, I'm most curious as to how Burris' issue was resolved.

Mine only happened the 3 times (that I am aware of)just before noon today.

Dylan said he would look into it. I mentioned that if the issue had not been raised in the forum, I would have totally ignored it. I am aware and understand the fleeting problems with any VOIP service and accept the occasional burp. Unless my service is completely down, I don't get too excited. If a feature has a problem, I can wait until it's fixed as I use only a handful of basics.
I think that many of my trouble reports are to make support aware of a problem that may be brewing. Most of the time it's nothing worth wasting bandwidth on.

**Russell** · 05-13-2009 07:56 PM

Originally Posted by burris

Mine only happened the 3 times (that I am aware of)just before noon today.

Dylan said he would look into it. I mentioned that if the issue had not been raised in the forum, I would have totally ignored it. I am aware and understand the fleeting problems with any VOIP service and accept the occasional burp. Unless my service is completely down, I don't get too excited. If a feature has a problem, I can wait until it's fixed as I use only a handful of basics.
I think that many of my trouble reports are to make support aware of a problem that may be brewing. Most of the time it's nothing worth wasting bandwidth on.

I think it's good to raise even the little burps in the forum. Until I saw the other posts I was seriously pondering Tim's suggestion about port forwarding, even though my router has been flawless with the PAP2T from ViaTalk and (until these glitches) the VOIPo PAP2T. Seeing that several others are having the issue seems to point that the issue is not at my end. It's also beneficial to the provider - if just one person reports it the inclination would be to "blame" the customer's setup and if the cause is elsewhere such "blame" only causes frustration both to the support person trying to help and the customer.

**scott2020** · 05-13-2009 08:02 PM

Here is my log file from when I have had trouble with incoming calls.

Code:

[2009-05-13 14:50:04] VERBOSE[2911] logger.c: -- Incoming call: Got SIP response 483 "Too Many Hops" back from 67.228.251.106
[2009-05-13 15:04:34] NOTICE[2911] chan_sip.c: Peer 'VOIPoIn' is now UNREACHABLE! Last qualify: 37
[2009-05-13 15:04:34] NOTICE[2911] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 48
[2009-05-13 15:04:44] NOTICE[2911] chan_sip.c: Peer 'VOIPoIn' is now Reachable. (37ms / 2000ms)
[2009-05-13 15:04:44] NOTICE[2911] chan_sip.c: Peer 'VOIPo' is now Reachable. (38ms / 2000ms)