I just got a call and we tried to answer, but the phone kept on ringing, and we could not answer it. Also, the called id said "<!DOCTYPE HTML" for the name, and the correct number.
Something is confusing my phone with a web browser!!!!
Printable View
I just got a call and we tried to answer, but the phone kept on ringing, and we could not answer it. Also, the called id said "<!DOCTYPE HTML" for the name, and the correct number.
Something is confusing my phone with a web browser!!!!
lol just lol......Quote:
Originally Posted by abward
Yeah, but wife is not laughing. She is the one that tried to answer the phone.
WAF = WAF - 1
Are you using one of VOIPo's adapters? When I saw this happening, it was on my Asterisk box using a caller ID lookup script. It was doing HTML scrapes to Whitepages.com looking up caller ID names. I doubt VOIPo does that though. Just a thought.
I have a VOIPo supplied PAP2T
Was this just the one call?
So far, yes. The call in question was at 21:05. The next call that came in at 21:37 was fine.
I am curious about the weird caller id, but I am a bit more concerned that we were unable to answer the call.
One more detail, that I neglected to put in earlier, both lines were ringing when this happened.
Do you know if you had any voicemails where this could have been a MWI light notification? I've seen a case before where the notification caused a ring.Quote:
Originally Posted by abward
I have VoiceMail turned off.
Just happened again. Both lines rang, but I could not answer line 1. I picked up line 2 and could answer. I look now at the caller id on line 1 and there is no record of a call. Line 2 has the called id ok on it.
This needs to be fixed, TODAY.
Edit: Ticket opened
Looking at your registration I see a problem:Quote:
Originally Posted by abward
Linksys/PAP2T-3.1.15(LS)
sip:919XXXX@192.168.1.102:5060 sip:69.XXX.XXX.XX:29382 udp:74.52.58.50:5060 2009-02-27 17:58:16
Linksys/PAP2T-3.1.15(LS) sip:919XXXX@192.168.1.102:5061 sip:69.XXX.XXX.X:5061 udp:74.52.58.50:5060 2009-02-27 17:58:16
Notice on your first line, your router is randomizing the port. On the 2nd line it is not. So likely the NAT binding are getting messed up.
Do you have ALG enabled on it?
What about that tells you it is randomizing the port?
I am not familiar with ALG, but perhaps this is it?
http://www.wardpreston.net/images/router_page.jpg
This is a Dlink DIR-655
Maybe get rid of SPI for openers..Quote:
Originally Posted by abward
With that model I second that... disable spi
You might want to disable SPI and see if it works.
Ok, the SPI's have it (attempt at joke). SPI turned off. Anything else wrong?
Edit: Could be coincidence, but the net is sluggish to me now. I will try rebooting all boxes.
If your Line 1 port is 5060, and if it is being used by another node in your network, then it might pick a different outgoing global port.
Do you need all those ALG settings?Quote:
Originally Posted by abward
Why not take them out...reboot the router and ATA and see what happens.
OK. IPSec might be the only one I need, due to my company's VPN. I can try turning the other two off (the help file doesn't say anything about these so I don't know what they do) in a couple of hours, after I finish a big upload.
Thanks all.
I have a CallVantage box on my network too. I wonder if it is interfering? I cannot seem to get into it (well, maybe I can if I hook a laptop up to it with a wire into the LAN port) to see what port it is using, and I don't see anything in the router log.Quote:
Originally Posted by sr98user
I also noticed that your PAP2T is running a pretty old firmware. You might ask support about upgrading to 5.1.6(LS).
If its using port 5060 (which is a good possiblity), then your router will pick another outgoing global port. But you router should map the traffic on inbound correctly. I am guessing maybe your firewall is blocking the traffic for the incoming traffic.Quote:
Originally Posted by abward
Screw my big upload. I turned off all 4 of the ALG settings and I am back up. My VPN works fine. Less is more!
I guess time will tell now, unless Brandon comes up with a tweak to try.
Tim,
Any comment on the firmware level?
sr98user,
Hmmmmm, I do see this in the log. Why are two different addresses trying to go to port 5060?
Blocked incoming UDP packet from 74.55.77.234:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:03:12 2009 Blocked incoming UDP packet from 74.55.77.234:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:03:07 2009 Blocked incoming UDP packet from 174.132.131.131:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:03:06 2009 Blocked incoming UDP packet from 174.132.131.131:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:03:03 2009 Blocked incoming UDP packet from 208.43.97.218:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:03:02 2009 Blocked incoming UDP packet from 208.43.97.218:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:55 2009 Blocked incoming TCP packet from 64.12.165.99:5190 to 69.134.160.41:3398 as ACK received but there is no active connection
[INFO] Fri Feb 27 14:02:54 2009 Blocked incoming UDP packet from 68.109.3.50:24844 to 69.134.160.41:35658
[INFO] Fri Feb 27 14:02:52 2009 Blocked incoming UDP packet from 208.43.132.146:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:02:51 2009 Blocked incoming UDP packet from 208.43.132.146:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:50 2009 Blocked incoming UDP packet from 67.228.251.106:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:02:49 2009 Blocked incoming UDP packet from 67.228.251.106:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:37 2009 Blocked incoming UDP packet from 66.229.37.221:16237 to 69.134.160.41:39362
[INFO] Fri Feb 27 14:02:28 2009 Blocked incoming UDP packet from 74.55.77.234:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:02:27 2009 Blocked incoming UDP packet from 74.55.77.234:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:21 2009 Blocked incoming UDP packet from 174.132.131.131:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:02:20 2009 Blocked incoming UDP packet from 174.132.131.131:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:20 2009 Blocked incoming UDP packet from 68.109.3.50:24844 to 69.134.160.41:35658
[INFO] Fri Feb 27 14:02:16 2009 Blocked incoming UDP packet from 208.43.97.218:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:02:15 2009 Blocked incoming UDP packet from 208.43.97.218:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:05 2009 Blocked incoming UDP packet from 67.228.251.106:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:02:04 2009 Blocked incoming UDP packet from 208.43.132.146:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:02:04 2009 Blocked incoming UDP packet from 67.228.251.106:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:03 2009 Blocked incoming UDP packet from 208.43.132.146:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:02:02 2009 Blocked incoming UDP packet from 92.32.243.239:36134 to 69.134.160.41:3711
[INFO] Fri Feb 27 14:01:55 2009 Blocked incoming TCP packet from 64.12.165.99:5190 to 69.134.160.41:3398 as ACK received but there is no active connection
[INFO] Fri Feb 27 14:01:49 2009 Blocked incoming UDP packet from 68.109.3.50:24844 to 69.134.160.41:35658
[INFO] Fri Feb 27 14:01:43 2009 Blocked incoming UDP packet from 74.55.77.234:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:01:42 2009 Blocked incoming UDP packet from 74.55.77.234:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:01:36 2009 Blocked incoming UDP packet from 174.132.131.131:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:01:35 2009 Blocked incoming UDP packet from 174.132.131.131:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:01:29 2009 Blocked incoming UDP packet from 208.43.97.218:5060 to 69.134.160.41:5061
[INFO] Fri Feb 27 14:01:28 2009 Blocked incoming UDP packet from 208.43.97.218:5060 to 69.134.160.41:51216
[INFO] Fri Feb 27 14:01:26 2009 Blocked incoming UDP packet from 68.109.3.50:24844 to 69.134.160.41:35658
[INFO] Fri Feb 27 14:01:19 2009 Blocked incoming UDP packet from 67.228.251.106:5060 to 69.134.160.41:5061
More than likely that's the issue. It's possible it's just getting the 2 lines mixed up and 1/2 the data is going to one, 1/2 the other.
I am sorry, what do you mean Tim, the router config, or the CallVantage adapter?
Should I be switched to another port (assuming VOIPo can do that), to stay away from the CallVantage traffic?
The 3.1.15(LS) wcame with the PAP2Ts that VOIPo sent us..Quote:
Originally Posted by bretski
I wouldn't touch it until Tim wants to upgrade it..Besides, I have the same box and with the exception of the radius problem, it hasn't missed once.
I mean the config.
If you know what port Callvantage is using though, we should definitely try to avoid that port and can change it.
Does anyone here know what it uses?
Once it fails connecting with one SIP server, the phone adapter checks the next SIP server using the DNS SRV record, I believe. That's probably why east01, west01, sip, central01 are all trying to talk to your adapter. I think if you turn off SPI, you should be good to go. If it still does not work, then change the local port for Line1 from 5060 to something like 5062.
And, don't forget to reboot the router after you turn it off..
sr98user,
I see. SPI is turned off, so I don't know why they are all still trying to talk to it.
I guess support needs to change my port number. I don't seem to have access to it at the User level.
Like burris says, power down adapters and router. Turn the router on and then the adapter.
I had done a soft boot, but I just did a hard boot to be safe. Hard booted the PAP2T and CallVantage boxes too. Looks like all of the VOIPo servers are still hitting my box.Quote:
Originally Posted by burris
They'll always be doing that. It won't cause any issues.Quote:
Originally Posted by abward
The SPI being the issue was with mixing up the traffic locally on your network.
It looks nice and clean now.
Linksys/PAP2T-3.1.15(LS) sip:919XXX@192.168.1.102:5060 sip:X:5060 udp:74.52.58.50:5060 2009-02-27 19:41:12
Linksys/PAP2T-3.1.15(LS) sip:919XXX@192.168.1.102:5061 sip:X:5061 udp:74.52.58.50:5060 2009-02-27 19:41:12
When I had CallVantage and Voipo adapters on the same router, I often experienced incoming and outgoing issues. I dropped CallVantage so now I do not know what ports they use anymore.Quote:
Originally Posted by abward
The very reason I suggested *asking* about it. :)Quote:
Originally Posted by burris
One of the very first things the support team did (when I received a PAP2T) was upgrade me from 3.1.15 to 5.1.6. Their recommendation.
So all the problems were on his local network ?
CallVantage box is my work supplied box, so nothing I can do about it.
A search in Google says the CallVantage box uses: ports 5620, 5060-5061, and 10000-20000 all UDP
Tim, should we try me on a different port, to be safe?
Edit: Brandon has put me to firmware 5.1.6, and on ports 5076 and 5078. Now we watch it for a few days.
Thanks to all of you for helping me through this!!!!