View Full Version : <!doctype Html
abward
02-26-2009, 08:17 PM
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!!!!
Xponder1
02-26-2009, 08:28 PM
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......
abward
02-26-2009, 08:34 PM
Yeah, but wife is not laughing. She is the one that tried to answer the phone.
WAF = WAF - 1
scott2020
02-26-2009, 08:54 PM
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.
abward
02-26-2009, 09:18 PM
I have a VOIPo supplied PAP2T
VOIPoTim
02-26-2009, 09:29 PM
Was this just the one call?
abward
02-26-2009, 09:43 PM
So far, yes. The call in question was at 21:05. The next call that came in at 21:37 was fine.
abward
02-26-2009, 10:00 PM
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.
VOIPoTim
02-26-2009, 10:18 PM
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.
abward
02-27-2009, 05:25 AM
I have VoiceMail turned off.
abward
02-27-2009, 07:30 AM
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
VOIPoTim
02-27-2009, 12:00 PM
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:
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?
abward
02-27-2009, 12:21 PM
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
burris
02-27-2009, 12:26 PM
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..
chpalmer
02-27-2009, 12:27 PM
With that model I second that... disable spi
sr98user
02-27-2009, 12:27 PM
You might want to disable SPI and see if it works.
abward
02-27-2009, 12:29 PM
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.
sr98user
02-27-2009, 12:31 PM
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.
burris
02-27-2009, 12:39 PM
Ok, the SPI's have it (attempt at joke). SPI turned off. Anything else wrong?
Do you need all those ALG settings?
Why not take them out...reboot the router and ATA and see what happens.
abward
02-27-2009, 12:46 PM
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.
abward
02-27-2009, 12:48 PM
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.
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.
bretski
02-27-2009, 12:51 PM
I also noticed that your PAP2T is running a pretty old firmware. You might ask support about upgrading to 5.1.6(LS).
sr98user
02-27-2009, 01:00 PM
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.
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.
abward
02-27-2009, 01:02 PM
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?
abward
02-27-2009, 01:05 PM
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
VOIPoTim
02-27-2009, 01:09 PM
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.
abward
02-27-2009, 01:13 PM
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?
burris
02-27-2009, 01:24 PM
I also noticed that your PAP2T is running a pretty old firmware. You might ask support about upgrading to 5.1.6(LS).
The 3.1.15(LS) wcame with the PAP2Ts that VOIPo sent us..
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.
VOIPoTim
02-27-2009, 01:26 PM
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?
sr98user
02-27-2009, 01:26 PM
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.
burris
02-27-2009, 01:29 PM
And, don't forget to reboot the router after you turn it off..
abward
02-27-2009, 01:32 PM
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.
sr98user
02-27-2009, 01:34 PM
Like burris says, power down adapters and router. Turn the router on and then the adapter.
abward
02-27-2009, 01:37 PM
And, don't forget to reboot the router after you turn it off..
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.
VOIPoTim
02-27-2009, 01:40 PM
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.
They'll always be doing that. It won't cause any issues.
The SPI being the issue was with mixing up the traffic locally on your network.
VOIPoTim
02-27-2009, 01:41 PM
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
NY Tel Guy
02-27-2009, 01:43 PM
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?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.
bretski
02-27-2009, 01:53 PM
The 3.1.15(LS) wcame with the PAP2Ts that VOIPo sent us..
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.
The very reason I suggested *asking* about it. :)
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.
Montano
02-27-2009, 01:54 PM
So all the problems were on his local network ?
abward
02-27-2009, 01:54 PM
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!!!!
burris
02-27-2009, 02:00 PM
The very reason I suggested *asking* about it. :)
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.
I could do this myself, but I'm still gun shy from having the original HT286 upgraded and then downgraded and then upgrading and downgrading on the HT502.
On my own SPA2102, I always upgraded it myself whenever new firmware appeared.
The PAP2T up was never suggested to me and I'm always reluctant to fool with a product that's not mine. Tweaking is one thing, but firmware is another.
Thanks for mentioning this. I will ask, although I can't imagine a box running any more reliably than this one....for me.
sr98user
02-27-2009, 02:03 PM
abward,
After the reboot, is incoming working for you?
bretski
02-27-2009, 02:16 PM
I could do this myself, but I'm still gun shy from having the original HT286 upgraded and then downgraded and then upgrading and downgrading on the HT502.
On my own SPA2102, I always upgraded it myself whenever new firmware appeared.
Totally understandable. I went through several up/downs on my HT502 as well.
The PAP2T up was never suggested to me and I'm always reluctant to fool with a product that's not mine. Tweaking is one thing, but firmware is another.
Thanks for mentioning this. I will ask, although I can't imagine a box running any more reliably than this one....for me.
No prob. After years in the tech industry, I'm with you on firmware upgrades. I'm a pretty firm believer in "if it ain't broke..."
OT, and FWIW: aside from my ongoing problem with CWCID, I am *very* pleased with the PAP2T.
quattrohead
02-27-2009, 02:29 PM
I just switched back to the HT286 because of HT502 issues inside my router.
I called support and got right through to James (i think) and he got me running again.
After a quick tweak of some settings to make them current and changing the port to 5080 so it stays well away from PP, everything is running smooth again.
The HT502 has its place on a simple network, but not in an "IT" type environment that most of us are running !!!!
abward
02-27-2009, 02:32 PM
abward,
After the reboot, is incoming working for you?
Yep, the phone rang just as I was reading your post. And, hold on to your hat, I was actually able to answer it.
So, I am rehersing:
Wife: Honey, what did you do today?
Me: Not much...
fisamo
02-27-2009, 02:35 PM
Abward--
To confirm, CallVantage uses the ports you posted for all of their devices, except the D-link DVG-1120M. If you have anything other than a huge gray brick for your CallVantage ATA (the 1120M--the model# is also on the upper right corner of the front panel), you're probably having a port conflict.
It sounds like Tim has switched your ports for you, so you should not have this issue any longer. FWIW, the 1120M is the ATA that I have from ATTCV, which is probably why I haven't had similar conflict issues between Voipo and ATTCV.
abward
02-27-2009, 02:39 PM
My CallVantage box is the Centillium MTA-1. So, sounds good.
Morals of the whole story:
1. If you have another ATA, make sure you tell VOIPo so they can port around it.
2. Make sure you check your router settings for ALG and SPI.
Maybe these should go into the FAQs.
abward
03-02-2009, 03:33 PM
Just got a call and the called id name was <null>, with an Unknown Number for the number.
bretski
03-02-2009, 06:01 PM
That's normal for some anonymous calls, and often from PBX systems. It see it quite a bit.
abward
03-04-2009, 07:16 AM
FYI,
I now have reason to believe that the port 5060 conflict may have been coming from a soft phone on my company PC. It uses Lotus Sametime Connect, and I just noticed that it talks on port 5060. It still could have been the CallVantage adapter, for all I know.
VOIPoTim
03-15-2009, 07:07 PM
If anyone sees this today, please see http://forums.voipo.com/showthread.php?goto=newpost&t=1278 for info.
Kaelin
03-15-2009, 07:16 PM
This happened to me today. <!doctype html for the callerId and unable to pickup the call.
I do not have any other ATAs. I do have that same router though (DIR-655) and SPI is turned off but not the ALGs. I'll switch those off and see if it makes a difference. I've only had this problem once and I noticed it was on a call that should have come through as a "private number". Everything was working fine before and I have received calls successfully afterwards.
Edit: Actually this wasn't a "private number". The person normally calls with callerID blocked but the number came through this time. It just had the <!doctype html in the name. I'm thinking it was just a coincidence and this happened due to Tim's previous post. Although this call came in at 3:04 PM EST. Maybe they ran a little longer?
If anyone sees this today, please see http://forums.voipo.com/showthread.php?goto=newpost&t=1278 for info.
This did happen for me. I am "kindof" ok with getting the <!DOCTYPE HTML, but I could not answer the call on either line1 or line2. I did get the number and was able to call the caller back.
It would be great if a caller ID Name issue like this wouldn't impact my ability to answer the call.
The call was at 2:25 Central time on 3/15.
Dan