[Resolved 8/1/10] 5 - 90 Min into the call and drops out

[beverly]

5 - 10 - 90 mins into the call and it drops out for some reason... been experiencing this for the last two weeks. everything was working fine before that. haven't changed anything. did a reboot. reloaded firmwares, re-did everything. and the same thing is still happening.. anyone else experiencing this problem?


Roger's Internet
10mb down, 512k up
Linksys WRT54GS Router v1.1 (DD-WRT v24-sp2 (07/22/09) mega - build 12548M NEWD Eko)
(MJPROXY running in the back)
Linksys PAP2T
Line 1 MagicJack
Line 2 FreePhoneLine

5060 UDP - 6062 UDP ports open, 13000-13002 UDP port open
Tryed different ports 5060, 5061,5660,6000,6001,6060,6061

Result: Calls drop about 10 mins into conversation

[Aaron]

We are experiencing this problem as well. Our configuration is very similar.

ATA: Linksys PAP2T
Router: Linksys BEFW11S4

Problem 1 - Some calls drop after 10 minutes or so.
Problem 2 - For about 20% of all our calls, we cannot hear the other party. This happens on inbound as well as outbound calls. When calling out, the audio usually cuts off after one or two rings and then it doesn't come back. Although we can't tell, the call is sometimes answered and the other party can hear us calling, "Hello? Hello?" Yet we hear nothing.

[joc_cro]

Same problem here...

Also my PAP2T, reboot frequently for no reason and some time I have a tone some time not.

If anybody have a solution it will be great!!

[Aaron]

As a follow-up, I took the router out of the loop and connected the ATA directly to my Rogers modem. Seemed okay for a while but I found there are still issues.

1. User calls and I answer but the call is not connected.
2. I call my cell and after two rings, the cell shows the call is aborted but it continues to ring on the calling end.
3. I call my cell and sometimes it shows the number 416-642-0882 is calling. That's not my number. This happens at least 30% of the time.

Could the PAP2T causing these problems?

[FONGO_steve]

As a follow-up, I took the router out of the loop and connected the ATA directly to my Rogers modem. Seemed okay for a while but I found there are still issues.

1. User calls and I answer but the call is not connected.
2. I call my cell and after two rings, the cell shows the call is aborted but it continues to ring on the calling end.
3. I call my cell and sometimes it shows the number 416-642-0882 is calling. That's not my number. This happens at least 30% of the time.

Could the PAP2T causing these problems?

Number 3 isn't cause by the PAP2. Very (and I mean very) rarely will a call from our network go through a carrier that isn't passing CID, and it just passes one of our BTN's instead.

1&2 seem unique though.. I'm leaning towards device setup, but let's see what others say.

[Aaron]

I purchased the ATA pre-configured from fpl. I updated Line 1 settings according to the following guide when I started experiencing the trouble last week.
http://forum.freephoneline.ca/viewtopic.php?f=15&t=310
That didn't help. Since then, I've switched to Line 2. It's been almost 24 hours on Line 2 now and no apparent issues so who knows.

Also, as for the calls coming from the BTN, I checked my cell phone and 12 out of 37 showed this number.

[beverly]

is there another FPL proxy server that i could use instead of the default one? (PM me for this one)for service provider reason's

[FONGO_steve]

is there another FPL proxy server that i could use instead of the default one? (PM me for this one)for service provider reason's

We only have the one

[bendez]

I am having the EXACT same problem. 10-15 mins into the call, and the call drops. I am also using PAP2T ATA.

Any advice??

[Jake]

There are a few people here mentioning that they have the same problem. There could be a common connection other than FPL.

It could be worth people having this problem to list.

1. Their ISP
2. Area code they are calling from
3. Area code they are calling to
4. The phone company they are calling to if known (Rogers, Bell, Rogers Mobile, Telus, etc)
5. If it happens on incoming calls, outgoing calls, or both.
6. ATA used (if any)
7. If the same thing happens if the softphone is used.

Just a thought

[beverly]

1. Their ISP

Rogers

2. Area code they are calling from

613 (Local)

3. Area code they are calling to

613 (Local)

4. The phone company they are calling to if known (Rogers, Bell, Rogers Mobile, Telus, etc)

Rogers Home Phone {everyone i call (that has dropped out) has rogers home phone, haven't talked long enough to a person on bell mobility}

5. If it happens on incoming calls? outgoing calls, or both.

Both

6. ATA used (if any)?

Yes

7. If the same thing happens if the softphone is used?

Never Tryed (don't use it)

8. How long has been happening?

Been happening for 3 4 weeks now

[beverly]

bump... still happening

[FONGO_kris]

What speed are you getting with Rogers? Could you try with the software phone and see if it's happening? -- What kind of ATA do you have?

[beverly]

10.5Mbps 512k up
Linksys PAP2T
Last night i called my sis on her phone which is land line or videotron (Quebec Cable) and 5.02 min(2010-02-16 19:16:10.0 2010-02-16 19:21:12.0) into the call, it cuts out... a minute later my dad called

Phone won't get used much if i go software...

but later (next 2 days) i'm going to re-flash the firmware on the router and/or try another router..
another weird thing is when i use all my bandwidth (newsgroups) it doesn't happen at all, but only when no bandwidth is used

[FONGO_steve]

10.5Mbps 512k up
Linksys PAP2T
Last night i called my sis on her phone which is land line or videotron (Quebec Cable) and 5.02 min(2010-02-16 19:16:10.0 2010-02-16 19:21:12.0) into the call, it cuts out... a minute later my dad called

Phone won't get used much if i go software...

but later (next 2 days) i'm going to re-flash the firmware on the router and/or try another router..
another weird thing is when i use all my bandwidth (newsgroups) it doesn't happen at all, but only when no bandwidth is used

Let me know how using the new router goes.. I'm wondering if it's something wonky with the router's QoS. Weird that it works well under heavy bandwidth usage, but doesn't when not. Has me puzzled...

[beverly]

i don't even have QoS enabled

[dmac]

I am having same problem with calls dropping out after 3-4 mins.It happens with both incoming and outgoing calls. I am using the softphone version at the moment just to see if this service is going to work. Also I cannot seem to get extensions on phone menus to work. Need help.

[Aaron]

I am still having this problem as well. I had previously mentioned a couple other issues (early Feb) but since switching to Line 2, those have cleared up. The only thing that's still happening is the calls dropping. The duration of the call varies. Sometimes it dies after 5 minutes and sometimes it lasts much longer.

Hey I think I found a workaround, never talk for more than 5 minutes straight.

[brendany]

I have exactly this problem.

Kris/Steve are there any logs that the users affected can provide to at least narrow in on the source of the problem. ATA, router, FPL servers?

Is there an enhanced logging/diagnostic mode on the PAP2 ATA that can be enabled.

The service is great overall - this is the only problem.

[brendany]

I just took a look at the call logs. I'm not sure if this has any bearing on the situation because there is only once instance of this in the current month (although there have been many instances of dropped calls). But just in case:

Call from my FPL which Connected and then Dropped 3:25 minutes later
1905<My FPL Number> 1905<Dest. Number> 03:25 2010-02-19 15:42:06.0 2010-02-19 15:45:31.0

Failed Call (likely me trying to call back but getting a busy/VM from the destination)
1905<My FPL Number> 1905<Dest. Number> 2010-02-19 15:45:53.0 Normal completed call Normal call clearing

Failed Call (likely me trying to call back but getting a busy/VM from the destination)
1905<My FPL Number> 1905<Dest. Number> 2010-02-19 15:46:08.0 Normal completed call Normal call clearing

Failed Call - this is the only instance of this error description
1905<My FPL Number> 1905<Dest. Number> 2010-02-19 15:46:31.0 Network error Invalid call reference value

Successful Incoming Call (the person I was talking to called back)
1905<Dest. Number> 1905<My FPL Number> 10:24 2010-02-19 15:46:36.0 2010-02-19 15:57:00.0

[volenin]

Experiencing the same issue: dropped calls anywhere from 15 to 60 minutes into the call. Originally had WRT54G router with Tomato firmware, QoS enabled with the SPA 2102 ATA given its own dedicated class and exclusive use of at least 40Kb upload bandwidth. Later on connected the ATA directly to the Cable modem, removed ALL network devices (wireless & wired) so that ATA had exclusive use of the network - the same issue persisted.

My config: [Rogers 10Mb / 1Mb internet connection] ---> [Linksys Cable Modem] ---> [Linksys WRT54G router with Tomato firmware] ---> [Linksys 2102 ATA gateway]

Seems like there are a lot of users experiencing this problem right now...

FPL!!!! - please resolve this issue!!!!

[volenin]

Ok. For those ones interested in debugging this issue, I've just found an option to enable the SIP debugging on SPA 2102 ATA. I'll PM the full debug log next time I get disconnected.

In order to enable debugging you need:

1) remote syslog server (you can either find a free Syslog server you can install on your windows desktop) OR if you have (*)nix box, just enable remote syslog there
2) login to your SPA as 'admin', then switch to 'advanced' settings
3) on Voice -> System tab under the Misc settings, type in the IP of the box running the syslog server under BOTH 'Syslog' and 'Debug' server options. Set 'Debug Level' to 3.
3.1) Coudln't see the difference in the debug levels, but I guess it won't hurt to set it to maximum
4) Under the Voice -> Line tab (whichever line you are using), locate 'SIP Debug Option' under the 'SIP Settings' section. Set it to 'Full', as I have no idea what other options would exclude from the trace
5) Don't forget to 'Submit all changes'
6) after router reboots, open your Syslog server log file. You should see smth like that:

Code: Select all

Feb 20 11:32:47 192.168.1.1 kernel: ACCEPT IN=br0 OUT=vlan1 SRC=192.168.1.xx DST=208.65.240.142 LEN=60 TOS=0x18 PREC=0xA0 TTL=249 ID=43215 PROTO=UDP SPT=16468 DPT=35506 LEN=40 
Feb 20 11:53:46 192.168.1.1 kernel: ACCEPT IN=br0 OUT=vlan1 SRC=192.168.1.xx DST=209.81.9.7 LEN=76 TOS=0x00 PREC=0x00 TTL=249 ID=10964 PROTO=UDP SPT=12055 DPT=123 LEN=56 
Feb 20 12:09:24 192.168.1.15 System started: ip@192.168.1.xx, reboot reason:W4
Feb 20 12:09:24 192.168.1.15 System started: ip@192.168.1.xx, reboot reason:W4
Feb 20 12:09:20 192.168.1.1 kernel: ACCEPT IN=br0 OUT=vlan1 SRC=192.168.1.15 DST=209.81.9.7 LEN=76 TOS=0x00 PREC=0x00 TTL=249 ID=11 PROTO=UDP SPT=6400 DPT=123 LEN=56 
Feb 20 12:18:25 192.168.1.15 NOTIFY sip:voip.freephoneline.ca SIP/2.0  Via: SIP/2.0/UDP 192.168.1.xx:5060;branch=xxxxxxxxxx  From: John Smith <sip:1416xxxxxxx@voip.freephoneline.ca>;tag=5dddd2ff51o0  To: <sip:voip.freephoneline.ca>  Call-ID: xxxxxxxxx@192.168.1.xx  CSeq: 6 NOTIFY  Max-Forwards: 70  Contact: John Smith <sip:1416xxxxxxx@192.168.1.xx:5060>  Event: keep-alive  User-Agent: Linksys/SPA2102-5.2.10  Content-Length: 0   
Feb 20 12:18:25 192.168.1.xx SIP/2.0 480 Temporarily Unavailable  Via: SIP/2.0/UDP 192.168.1.xx:5060;branch=xxxxxxxxx;rport=5060;received=99.225.251.xxx  From: John Smith <sip:1416xxxxxxx@voip.freephoneline.ca>;tag=ddddda452ff51o0  To: <sip:voip.freephoneline.ca>;tag=dddddddddd  Call-ID: ddddddd@192.168.1.15  CSeq: 6 NOTIFY  Server: Sip EXpress router (0.9.6 (i386/freebsd))  Content-Length: 0   

Kris/Steve - I'll PM you the full log in a minute.... While the line is idle, I keep on seeing the 'Temporarily Unavailable' entries every 2 min. What does that mean?...

Vlad

[brendany]

Just to add to volenin's comments, I also am running slogsrv against my PAP2 ATA.

I made a couple of outgoing calls while watching the logs in both cases, this seems to be an interesting entry (See the bold, red text). In both cases the call dropped for no apparent reason (well maybe the apparent reason is the BYE command).

TP Parser error: 34
[0:5060]<<208.65.240.142:5060
[0:5060]<<208.65.240.142:5060

BYE sip:1905<My Number>@<My WAN IP Address>:5060 SIP/2.0
Via: SIP/2.0/UDP 208.65.240.142;branch=xxxx4bK52bd.a3e4d7bb4fa985f670e589b8baae9941.0
Via: SIP/2.0/UDP 208.65.240.142:5061;branch=xxxx4bK702c45a88f03e94b1b979a842407226c;rport=5061
Max-Forwards: 16
From: <sip:905<Destination Number>@voip.freephoneline.ca>;tag=xxxxb1613fa9250d955fbaf0a17de98bi
To: "<My Name>" <sip:1905<My Number>@voip.freephoneline.ca>;tag=xxxxc747257131d5o0
Call-ID: xxxxa1af-3e7bda8d@192.168.x.x
CSeq: 100 BYE
Contact: Anonymous <sip:208.65.240.142:5061>
Expires: 300
User-Agent: Sippy
cisco-GUID: xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx
h323-conf-id: xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx

[Jake]

My config: [Rogers 10Mb / 1Mb internet connection] ---> [Linksys Cable Modem] ---> [Linksys WRT54G router with Tomato firmware] ---> [Linksys 2102 ATA gateway]

beverly has Rogers also.

Do the other people that have this problem have Rogers as their ISP? It could be that they are doing something to make the call drop.

[volenin]

Hmm... That's possible, but I don't think Rogers does anything to drop the VoIP calls.... Would be good to collect the stats though.