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!!!!
Senior Member
<!doctype Html
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!!!!
Senior Member
Re: <!doctype Html
lol just lol......Originally Posted by abward
Senior Member
Re: <!doctype Html
Yeah, but wife is not laughing. She is the one that tried to answer the phone.
WAF = WAF - 1
Senior Member
Re: <!doctype Html
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.
Senior Member
Re: <!doctype Html
I have a VOIPo supplied PAP2T
Man with a Plan
Senior Member
Re: <!doctype Html
So far, yes. The call in question was at 21:05. The next call that came in at 21:37 was fine.
Senior Member
Re: <!doctype Html
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.
Last edited by abward; 02-26-2009 at 10:03 PM.
Man with a Plan
Senior Member
Re: <!doctype Html
I have VoiceMail turned off.
Posting Permissions
Reply With Quote
Bookmarks