Obi1062 and VOIPo Can't make PTSN outbound calls - just VOIPO

[jmwolfe]

Hello Obi Forum...

After several days of believing that maybe Obihai and/or Voipo can resolve my issue, I have finally given up and am ready to solve the issue the easy forum way!

I have searched here and after an hour, still haven't seen my issue, so I am hoping it's not a N00b thing that I have missed.

I just switched off of Verizon and decided to take the plunge into SIP and save a lot of $$. I went with VoiPO, and started out with X-Lite softphone. It worked great, could call out, etc. but the latency was too high, plus my wife wanted  real phone. I picked up a sweet deal on an Obi1062.    

Phone and PCs are behind a Verizon Gateway router (FIOS 75Mbps) and am pretty familiar with router/firewall stuffs. Sadly, this new router, as reliable as it has been, is not very fully featured: No ALG or SPI related features or any way to prioritize phone traffic that i can see via the web admin interface. From what I have read, I should not have to muck with a modern router all that much.

PROBLEM:  The phone registers just fine, but can only make outbound calls to my other VOIPO number, not any PTSN. It appears the INVITE request is not getting through. I can see the logarithmic tries occurring and then finally giving up after 32s or so. The call is not showing in my VOIPO logs. VOIPO is pretty much giving me the BYOD-brushoff, and Obihai's support response was weak. They each want the other to fix the problem. VOIPO says I should remove the leading 1 and see what happens (but acknowledging that it should not make any difference).

Via my router, I tried putting the phone in the DMZ, and also tried explicitly opening up UDP 6600-6780 for RTP but it didn't appear to make much difference so I reset those configs to the default.

I have been configuring via Obitalk. Outside of the normal default Obitalk config, I have enabled ICE and keep-alives and of course the basic SIP provider info, using the VOipo template from the list.

After days of trying various things, I set up a KIWI syslogd and turned on SIP debugging. Here's just the message column from a single outbound call attempt (read from bottom to the top). The calling phone # is masked out here as 508XXXYYYY, and IPs are also masked. The destination phone # never made it to the exchange.

Look forward to your assistance.

OBI: SIP/2.0 200 OK Call-ID: 617c0fdcdecd0a43-58b7@50.97.129.82 CSeq: 179 NOTIFY Content-Length: 0 From: sip:mwi@50.97.129.82;tag=69104600 To: sip:508XXXYYYY@67.2X8.1X2.2:5060 Via: SIP/2.0/UDP 67.2X8.1X2.2;branch=z9hG4bKb6bf.0a4f7b04.0;received=67.2X8.1X2.2;rport=5060 Via: SIP/2.0/UDP 50.97.129.82;branch=z9hG4bK.1397cc2bb94575;rport=53325;alias Via: SIP/2.0/UDP 50.97.129.82;rport

OBI: sendto 43e4b602:5060(389)

OBI: NOTIFY sip:508XXXYYYY@192.168.1.163:5060 SIP/2.0 Via: SIP/2.0/UDP 67.2X8.1X2.2;branch=z9hG4bKb6bf.0a4f7b04.0 Via: SIP/2.0/UDP 50.97.129.82;branch=z9hG4bK.1397cc2bb94575;rport=53325;alias Via: SIP/2.0/UDP 50.97.129.82;rport From: sip:mwi@50.97.129.82;tag=69104600 To: sip:508XXXYYYY@67.2X8.1X2.2:5060 Call-ID: 617c0fdcdecd0a43-58b7@50.97.129.82 Max-Forwards: 9 CSeq: 179 NOTIFY Event: message-summary Content-Type: application/simple-message-summary Content-Length: 101 Messages-Waiting: Yes Message-Account: sip:508XXXYYYY@67.2X8.1X2.2:5060 Voice-Messages: 1/0 (1/0)

OBI: RxFrom:43e4b602:5060

OBI: SIP/2.0 200 OK Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62347 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: ;tag=50bb2a71d8d027d80525a88d4628ce8d.12a4 Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-efff2eb2;rport=5060;received=192.168.1.163 Contact: ;q=0;expires=60 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9436 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: SIP/2.0 100 Trying Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62347 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-efff2eb2;rport=5060;received=192.168.1.163 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9436 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: REGISTER sip:sip.voipwelcome.com:5060 SIP/2.0 Call-ID: d98d1bf0aa92c86b@192.168.1.163 Content-Length: 0 CSeq: 62347 REGISTER From: ;tag=SP17feb9a543f7b3f6a Max-Forwards: 70 To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-efff2eb2;rport Authorization: Digest algorithm=MD5,nc=00000001,qop=auth,cnonce="76d398cf",nonce="58b70f4d000158a120e8393bb57fda528be285398274181c",realm="sip.voipwelcome.com",response="644bc55d9652f0cfac0bc39af8234133",uri="sip:sip.voipwelcome.com:5060",username="508XXXYYYY" User-Agent: OBIHAI/OBi1062-5.0.4.4003 Contact: ;expires=60;+sip.instance="" Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE Supported: replaces, eventlist, record-aware

OBI: sendto 43e4b602:5060(863)

OBI: SIP/2.0 401 Unauthorized Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62346 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: ;tag=50bb2a71d8d027d80525a88d4628ce8d.d8f8 Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-bddf6ad0;rport=5060;received=192.168.1.163 WWW-Authenticate: Digest realm="sip.voipwelcome.com", nonce="58b70f4d000158a120e8393bb57fda528be285398274181c", qop="auth" Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9434 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: SIP/2.0 100 Trying Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62346 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-bddf6ad0;rport=5060;received=192.168.1.163 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9434 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: REGISTER sip:sip.voipwelcome.com:5060 SIP/2.0 Call-ID: d98d1bf0aa92c86b@192.168.1.163 Content-Length: 0 CSeq: 62346 REGISTER From: ;tag=SP17feb9a543f7b3f6a Max-Forwards: 70 To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-bddf6ad0;rport Authorization: Digest algorithm=MD5,nc=00000002,qop=auth,cnonce="0ad8c795",nonce="58b70f2f000153ac1c6b97220cfde72efbc1c050c7ac0840",realm="sip.voipwelcome.com",response="97acc53c2268b59ca26b9171f968c68d",uri="sip:sip.voipwelcome.com:5060",username="508XXXYYYY" User-Agent: OBIHAI/OBi1062-5.0.4.4003 Contact: ;expires=60;+sip.instance="" Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE Supported: replaces, eventlist, record-aware

OBI: sendto 43e4b602:5060(863)

OBI: SIP/2.0 200 OK Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62345 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: ;tag=50bb2a71d8d027d80525a88d4628ce8d.dbf8 Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-283f14a3;rport=5060;received=192.168.1.163 Contact: ;q=0;expires=60 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9435 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: SIP/2.0 100 Trying Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62345 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-283f14a3;rport=5060;received=192.168.1.163 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9435 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: REGISTER sip:sip.voipwelcome.com:5060 SIP/2.0 Call-ID: d98d1bf0aa92c86b@192.168.1.163 Content-Length: 0 CSeq: 62345 REGISTER From: ;tag=SP17feb9a543f7b3f6a Max-Forwards: 70 To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-283f14a3;rport Authorization: Digest algorithm=MD5,nc=00000001,qop=auth,cnonce="0ad8c795",nonce="58b70f2f000153ac1c6b97220cfde72efbc1c050c7ac0840",realm="sip.voipwelcome.com",response="83d49d881537da6e78c8a3137228f4d3",uri="sip:sip.voipwelcome.com:5060",username="508XXXYYYY" User-Agent: OBIHAI/OBi1062-5.0.4.4003 Contact: ;expires=60;+sip.instance="" Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE Supported: replaces, eventlist, record-aware

OBI: sendto 43e4b602:5060(863)

OBI: SIP/2.0 401 Unauthorized Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62344 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: ;tag=50bb2a71d8d027d80525a88d4628ce8d.665c Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-6fffe5c0;rport=5060;received=192.168.1.163 WWW-Authenticate: Digest realm="sip.voipwelcome.com", nonce="58b70f2f000153ac1c6b97220cfde72efbc1c050c7ac0840", qop="auth" Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9437 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: SIP/2.0 100 Trying Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62344 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-6fffe5c0;rport=5060;received=192.168.1.163 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9437 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: REGISTER sip:sip.voipwelcome.com:5060 SIP/2.0 Call-ID: d98d1bf0aa92c86b@192.168.1.163 Content-Length: 0 CSeq: 62344 REGISTER From: ;tag=SP17feb9a543f7b3f6a Max-Forwards: 70 To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-6fffe5c0;rport Authorization: Digest algorithm=MD5,nc=00000002,qop=auth,cnonce="e7db7d5b",nonce="58b70f1100014f2755f7eac8e658a75749b461991964aff6",realm="sip.voipwelcome.com",response="b6093ae4e813e05e7e64b6f79ded6a3b",uri="sip:sip.voipwelcome.com:5060",username="508XXXYYYY" User-Agent: OBIHAI/OBi1062-5.0.4.4003 Contact: ;expires=60;+sip.instance="" Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE Supported: replaces, eventlist, record-aware

OBI: sendto 43e4b602:5060(863)

OBI: SIP/2.0 200 OK Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62343 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: ;tag=50bb2a71d8d027d80525a88d4628ce8d.b3a3 Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-7e7389b2;rport=5060;received=192.168.1.163 Contact: ;q=0;expires=60 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9437 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: SIP/2.0 100 Trying Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62343 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-7e7389b2;rport=5060;received=192.168.1.163 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9437 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: REGISTER sip:sip.voipwelcome.com:5060 SIP/2.0 Call-ID: d98d1bf0aa92c86b@192.168.1.163 Content-Length: 0 CSeq: 62343 REGISTER From: ;tag=SP17feb9a543f7b3f6a Max-Forwards: 70 To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-7e7389b2;rport Authorization: Digest algorithm=MD5,nc=00000001,qop=auth,cnonce="e7db7d5b",nonce="58b70f1100014f2755f7eac8e658a75749b461991964aff6",realm="sip.voipwelcome.com",response="bcc16b40e272f34db205024bf8002783",uri="sip:sip.voipwelcome.com:5060",username="508XXXYYYY" User-Agent: OBIHAI/OBi1062-5.0.4.4003 Contact: ;expires=60;+sip.instance="" Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE Supported: replaces, eventlist, record-aware

OBI: sendto 43e4b602:5060(863)

OBI: SIP/2.0 401 Unauthorized Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62342 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: ;tag=50bb2a71d8d027d80525a88d4628ce8d.80f9 Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-b7561de8;rport=5060;received=192.168.1.163 WWW-Authenticate: Digest realm="sip.voipwelcome.com", nonce="58b70f1100014f2755f7eac8e658a75749b461991964aff6", qop="auth" Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9437 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: SIP/2.0 100 Trying Call-ID: d98d1bf0aa92c86b@192.168.1.163 CSeq: 62342 REGISTER From: ;tag=SP17feb9a543f7b3f6a To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-b7561de8;rport=5060;received=192.168.1.163 Server: Kamailio (1.4.5-notls (x86_64/linux)) Content-Length: 0 Warning: 392 67.2X8.1X2.2:5060 "Noisy feedback tells: pid=9437 req_src_ip=1X8.20.1X1.72 req_src_port=5060 in_uri=sip:sip.voipwelcome.com:5060 out_uri=sip:sip.voipwelcome.com:5060 via_cnt==1"

OBI: RxFrom:43e4b602:5060

OBI: REGISTER sip:sip.voipwelcome.com:5060 SIP/2.0 Call-ID: d98d1bf0aa92c86b@192.168.1.163 Content-Length: 0 CSeq: 62342 REGISTER From: ;tag=SP17feb9a543f7b3f6a Max-Forwards: 70 To: Via: SIP/2.0/UDP 192.168.1.163:5060;branch=z9hG4bK-b7561de8;rport Authorization: Digest algorithm=MD5,nc=00000002,qop=auth,cnonce="4fbf6888",nonce="58b70ef300014a2924aa821d0080c34ea35be4878d0afcea",realm="sip.voipwelcome.com",response="b05c53fca03d356d6b4a50db9d0c437c",uri="sip:sip.voipwelcome.com:5060",username="508XXXYYYY" User-Agent: OBIHAI/OBi1062-5.0.4.4003 Contact: ;expires=60;+sip.instance="" Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE Supported: replaces, eventlist, record-aware

OBI: sendto 43e4b602:5060(863)

[drgeoff]

What do you hear, and when, if you dial a POTS number?

What does the 1062's Call History show? Access that by pointing a browser to the Obi's IP address on your LAN.

What is the format of your other VOIPO number which you can reach?

[jmwolfe]

When dialing a POTS number, I hear the DTMF tones of the buttons and then no ring tone or any other sound for about 30 seconds. Then you get the 3 tones each raising in pitch -- the sound you usually hear on POTS phone lines when the call cannot be completed, usually followed by "If you'd like to make a call, please hang up and try your call again. Code XX-YYY". The 1062 then shows "Call Failed" and a small 900 next to that.

Call history shows "From PH1" and "To SP1 (destination phone #)". The status shows just as Call Ended.

The reachable VOIP # is 1-xxx-yyyy.. just the regular POTS number.

[drgeoff]

That spoken message is not being generated by the 1062 and the Call History shows that the called number is being sent to SP1.  I'd say the phone is working OK and configured OK and the problem is with VOIPO or further along the route from them to the PSTN network.

I do note that their answer to the BYOD question is yes but no support.

[jmwolfe]

BTW I do not hear a spoken message... I was just referring to the message one hears on a regular US POTS line when you say dial a number that doesn't exist. It's the same tone pattern.  Doubt if that changes your diagnosis, but in just in case...

So I guess I can try using a regular phone with their ATA and see if that works... if it does, it seems like I'm just out of luck?

The odd thing is, why would X-Lite work okay? I would think it would also fail if it were something basic, right?  I still think this superPhone is sending something that VoipO just doesn't expect.

[jmwolfe]

@drgeoff, I did test with the provider-supplied ATA, and outbound calling worked fine. :/

I reset to a factory settings just to clear the air, deleted it from ObiTalk and started over. As I expected, I still can't make outgoing PTSN calls.

I can see the 407 auth challenge come in, which after some more study I see is quite expected, and it appears the phone may not be responding in a way that the provider expects.

I've also taken a wireshark capture from my other computer that is running X-Lite with another VOIPO-provided phone #, and short of any other answers from folks here, will have to compare header by header until I find the missing piece.  The problem is of course that my wife has already fallen in love with the phone!

I'm also considering switching to ANVEO, or at least just trying the free account and see if the OBI is happier with it. Unfortunately, I'm past my 30 day cancel period with VOIPO, so I am determined to exhaust every possible option before giving up.

I've attached my syslog capture.

[azrobert]

Does VOIPO use SRV records? If it does, you need to enable SRV support on your OBi1062.

Service Providers -> ITSP x SIP -> X_DnsSrvAutoPrefix: Checked

[jmwolfe]

Thanks @azrobert.  Not sure, but enabling didn't fix/change anything.

[jmwolfe]

Did anyone look at the syslog? Is there no hope? :/

Is there some self-directed step I did not take? I'm ready, willing, and able.

Do you guys think pawing through wireshark headers is going to yield anything? I am unforunately a little new to SIP so I'm grasping at straws here.

Thanks,
Jesse

[azrobert]

OBi devices often have problems with SIP ALG. I just scanned the following thread and didn't see a solution.

http://www.dslreports.com/forum/r30447011-Woah-FiOS-G1100-Quantum-Router-no-good-for-VoIP

This thread suggests using a different port:
http://www.dslreports.com/forum/r30759880-FiOS-G1100-Quantum-Router

[drgeoff]

I'm really puzzled that you can make calls to your other VOIPO number which you say has the same format as the PSTN calls which fail.  And you say that the Call History shows both the other VOIPO number and failing PSTN numbers being sent identically mangled or unmangled to the same SP.

[jmwolfe]

Thanks guys for all your help. @azrobert's links helped identify the issue. It was indeed the new FIOS Gateway 1100 router which has SIP ALG permanently enabled! I thought I needed this router to get the 75M/75M speeds, but that was not true. I reinstalled my old router, and the phone Just Worked, and with a CAT5 cable was delivering 80M/75M. I could not believe it.

I went into the router admin and saw that SIP ALG is disabled.  Router is going back to Verizon unless everyone complains about poor wireless throughput... then I'll add it behind the old actiontec as a wifi access point.

Thanks again!

Jesse

[SteveInWA]

Thanks guys for all your help. @azrobert's links helped identify the issue. It was indeed the new FIOS Gateway 1100 router which has SIP ALG permanently enabled! I thought I needed this router to get the 75M/75M speeds, but that was not true. I reinstalled my old router, and the phone Just Worked, and with a CAT5 cable was delivering 80M/75M. I could not believe it.

I went into the router admin and saw that SIP ALG is disabled.  Router is going back to Verizon unless everyone complains about poor wireless throughput... then I'll add it behind the old actiontec as a wifi access point.

Thanks again!

Jesse

Jeeeeez, that was a hair-puller.  Glad you figured it out.  I'm a long-time FiOS customer.  I do not use FiOS TV; if you do, then you may need to keep your Verizon-supplied router attached.  Otherwise, there is no reason to use it under normal circumstances (their techs can supposedly do some remote diagnostics with that router, so you may want to keep it for that eventuality).  The main benefit of upgrading to a new router (of any brand), would be to take advantage of new features, such as 802.11ac WiFi and gigabit Ethernet speed, etc.  I have not used a FiOS-supplied router in many years.  The FiOS ONT (Optical Network Terminal) provides the WAN Ethernet link, just like a cable modem would, for example.  You can plug any router into that WAN connection.

[jmwolfe]

Thanks, Steve.  Fortunately, I don't have FIOS TV.

If I understand correctly, and just for future folks who find the thread you would have to have Verizon put the network signal on the ONT jack, right? By default it's going to the coax. 

Good idea to hold onto the router for diagnostics, but that's 10 bucks a month for that. They can do some with the actionTec. I may mess with it more later, but finally my wife has a phone that works and with an netgear powerLine wifi extender, I have good wifi everywhere it's needed.

[SteveInWA]

Boy, they're treating their customers like the cable companies now, charging a monthly equipment fee!  I live east of Seattle, in a location that was originally a General Telephone--GTE-->Verizon Northwest area, now sold off to Frontier.  Verizon installed FiOS here and then gave up the rollout -- too expensive to run all the fiber underground.  They give away the routers with the service.  I've never had a MOCA (internet over coax) connection, perhaps because I never had FiOS TV.  They ran an Ethernet cable directly from the ONT to my in-house LAN.  So, I can't speak from experience on how your location handles that.