Outgoing Calls dropped at 32 seconds on Verizon DSL

**FarmerMike** · 08-26-2009 09:05 AM

I have spent lots (probably too much) time on dslreports researching (this and other issues). I'll look again now that I have more of an understanding why the calls are being dropped. Vonage has their ACK timeout set at 60 seconds. Here is what one of their evangelists said in response to a similar problem:

The issue is exactly what I described to you in my initial response. On outbound phone calls, when the call is connected at the far end, a SIP 200 OK message is sent to your telephone adapter and this is where the audio stream starts. However, in the SIP protocol this 200 OK requires an ACK to let the far end know you received the 200 OK. Vonage is not receiving this ACK from you but we know your getting the 200 OK since you have 2 way audio when the call starts. Vonage continues to send a 200 OK for 3 retries and is not successful. At the 60 second mark, when the Gateway has not received an ACK from you, the call is disconnected.

As for the inbound calls, I am not seeing an issue however it may still be the same. On an inbound call, the signaling is the opposite. So when you pick up, you send a 200 OK which starts the audio stream and the Gateway send back an ACK which I can see. But, it is possible your device is not getting the ACK which I can't see from the proxy logs. It might not retry the 200 OK messages like the Gateways do.

I have tried several softphones, all have the same problem drop outgoing at 32 seconds (still going thru my actiontec). The Verizon Actiontec has a special version of the firmware that does not provide for bridge mode, so they have dumbed down a questionable product even more. As soon as I have the "backup" box from VZ, I will flash my current one with the non-Verizon firmware - if I brick it, no loss, one has to go back anyway.

**caseydoug** · 08-26-2009 09:23 AM

FarmerMike, I re-read your first post, and I see that this happens with a softphone also, and now you mention that it happens with Vonage. So it looks like is is not a problem with the PAP2, nor is it unique to VOIPo. Since this does not happen with all Actiontec modem/routers, you may be right that this has something to do with the special firmware loaded by Verizon. What we don't know is whether the problem is built in to the router functions or the modem functions of the Actiontec. In either case, loading the default firmware may well give you an answer. Keep us posted.

**FarmerMike** · 08-26-2009 09:42 AM

The Vonage report I copied was form their forums, it was not me he was responding to, but the same issue.

I should have both my backup VZ actiontec and a Westell 6100 (from ebay) here in a few days, then we can resolve this. Sometime in the evening/night when I have some free time and family internet use is minimal I will try re-configuring the Actiontec to see if I can get it to work as a mostly transparent bridge with the VZ firmware (no nat, no dhcp).

**caseydoug** · 08-26-2009 06:26 PM

The problem is that with transparent bridging you will still need a router if more than one computer will be using the internet connection. But it certainly would work for testing (unless the problem is with the VZ firmware itself). If Verizon uses PPPoE, I don't see how you can do without NAT and DHCP using the PAP2, since that device is not capable of doing the PPPoE login. However, you could let your computer do the login (I believe there is a built-in Windows PPPoE client), and then test the VoIP connection using a soft phone.

**FarmerMike** · 08-26-2009 07:17 PM

The quick update - new Verizon modem/router/wireless showed up today (next day UPS). BUT it is NOT the same unit, they sent me a Westell 7500 (with VZ firmware). Afters some messing to get the modem activated, I set up the port forwarding. The softphone worked, pap2t would not connect. I changed the static ip to dhcp on the pap2t (I had set the port forwarding using mac address) and all is working. Now I can finally use Voipo, it has taken 22 days to get up and running including 2 pap2t devices and a change in the VZ modem/router. The Westell offers much better control and even a stronger wireless signal (even with only an integrated antenna).

In the next few days I will be trying to get the Actiontec Verizon unit to actually work. I do have another router/wireless box to use if I can make the Actiontec into just a bridge.

I don't know if it was pure chance that I was shipped a Westell or the fact that when talking to VZ support I reported voip not working. Perhaps they know the AT have problems with voip and swap them when the customer complains.

I'll post an update after I mess with the Actiontec, I'm sure others will be handed that box by Verizon and want to use voip.

**Russell** · 08-26-2009 08:28 PM

Originally Posted by FarmerMike

The quick update - new Verizon modem/router/wireless showed up today (next day UPS). BUT it is NOT the same unit, they sent me a Westell 7500 (with VZ firmware). Afters some messing to get the modem activated, I set up the port forwarding. The softphone worked, pap2t would not connect. I changed the static ip to dhcp on the pap2t (I had set the port forwarding using mac address) and all is working. Now I can finally use Voipo, it has taken 22 days to get up and running including 2 pap2t devices and a change in the VZ modem/router.

Nice to hear that all appears to work with the new box. I'm sure you must pretty pleased after all the frustration.

**caseydoug** · 08-26-2009 11:50 PM

Yeah, good job. As I said before, I don't think it's the Actiontec itself, but possibly Verizon's firmware or configuration. I'll be interested to see whether you can get it working with that device.

**dswartz** · 08-27-2009 09:22 AM

farmer, silly question for you: you said it wouldn't work with a static IP. this is very surprising. now for the silly part (forgive me, but i don't know your level of networking savvy). you set a static IP, but did you remember to set the default gateway for the pap2t? if not, it would not be able to reach any outside host.

**FarmerMike** · 08-27-2009 04:47 PM

Yes, the default gateway was set correctly with the static ip. The PAP2T did connect with the static IP using the Actiontec, but not with the Westell. As soon as I changed the PAP2T back to dhcp it connected in seconds. Perhaps the westell is not be routing numbers outside of it's dhcp range, I didn't look too closely at the routing tables.

**dswartz** · 08-28-2009 06:34 AM

Originally Posted by FarmerMike

Yes, the default gateway was set correctly with the static ip. The PAP2T did connect with the static IP using the Actiontec, but not with the Westell. As soon as I changed the PAP2T back to dhcp it connected in seconds. Perhaps the westell is not be routing numbers outside of it's dhcp range, I didn't look too closely at the routing tables.

another silly question: static IP worked with the AT, but not the westell. did you reboot the pap2t, or did you just unplug the AT and plug in the westell? i ask because if the latter, the pap2t was most likely still using the old MAC address for the AT in its ARP table, whereas changing to dhcp would have likely flushed all of that.