Call from home VOIPO phone. Wrong caller-id showing up on my display at work.
In the morning when there were issues, I was attempting to make test calls and out of the 4 test calls, one had the (same) wrong caller-id.
Printable View
Call from home VOIPO phone. Wrong caller-id showing up on my display at work.
In the morning when there were issues, I was attempting to make test calls and out of the 4 test calls, one had the (same) wrong caller-id.
This has happened for me few times before. I ended up creating a ticket and they notify the upstream carrier.
Just tried two test calls to work. First call showed the same consistent wrong number. Second call came as Unknown. A co-worker of mine has VOIPo and when he calls his number at work (we all have individual lines) he sees the exact same number for caller id (same consistent wrong number) that I do.Quote:
Originally Posted by sr98user
VOIPo said they are passing the correct caller id info. But somehow the carrier connecting the long distance call is not sending the info correctly. For me, the behavior was not seen for all calls. Just some calls.
This (wrong caller-id) seems to have started relatively recently.
In my case, all calls were local, and the wrongly-passed CID number was local, but a different rate center than mine or the number I was calling. (e.g. a Raleigh number was shown, but my voipo number is in Apex, I was calling Durham)...
Edit to add: Haven't seen the problem in several days.
Mine are all in the RDU area too. Just tried calling work and it showed up as Unknown.Quote:
Originally Posted by fisamo
Are the first 6 digits of the number 919-424? If so, send me a PM with the rest of the number, if you'd like to know if it's the same number. (Not sure if that will help with the troubleshooting on Voipo's end.)
424-6412 is what I and my co-worker see.
Exactly the number I saw. Did you ever call that number? I haven't.
No never called it. The ticket I opened seems to have addressed both issue - slow calling and wrong caller-id. What is interesting is all was well before some recent change on the VOIPo side - I can only conclude that the "upstream" carrier was recently changed and that change resulted in the poor performance (long time for it to ring) and wrong caller-id. fiasmo, when did you notice this issue? And, also did it take a long time for you calls to complete?Quote:
Originally Posted by fisamo
I noticed the wrong CID issue about 2 weeks ago. As for calls taking a while to complete, that's been a sporadic problem. I think that in some cases, the call is completing in a normal period of time but the early ringback isn't heard on the Voipo line. I say this, because my wife called me at work once (in the past few weeks), and though my desk phone rang a few times before I picked up, she said she heard no ringing before my voice... I didn't feel it worth bothering support over, so I didn't submit a ticket.
Nice to hear that. By which I mean that I'm glad that I'm not the only one experiencing the issue. I'm assuming that it deals with these mysterious upstream carriers: should I conclude that VOIPo changed the one that affects us about a couple of weeks ago to one with lower "quality"? Some explanation of what fiasmo and I experienced would be most welcome.Quote:
Originally Posted by fisamo