Certain Verizon customers are unable to call me.

[mike770]

I recently had my telephone number ported from verizon and certain verizon customers, not all, are unable to call me. They hear absolutely nothing. No ringtone, no busy signal, nothing.

I called Viatalk tech support and I was told that I should call Verizon on monday to have my "translations" purged out of their system.

Has anyone else had this problem. I know some Ex-Vonage customers have had the same problems. I didn't think this could happen with Verizon.

Just my luck. I really can't wait to have my Viatalk account totally trouble free. The WAF ( Wife Acceptance Factor )is really starting to sink.:(

[abaldish]

I recently had my telephone number ported from verizon and certain verizon customers, not all, are unable to call me. They hear absolutely nothing. No ringtone, no busy signal, nothing.

I called Viatalk tech support and I was told that I should call Verizon on monday to have my "translations" purged out of their system.

Has anyone else had this problem. I know some Ex-Vonage customers have had the same problems. I didn't think this could happen with Verizon.

Just my luck. I really can't wait to have my Viatalk account totally trouble free. The WAF ( Wife Acceptance Factor )is really starting to sink.:(


My number is an original Verizon number, when I ported to vonage, they had to do some type of purging on there side. Now that I am moving the number over here this coming week, I will have to call Vonage to do the same so it is not cached in there system.

[mike770]

My number is an original Verizon number, when I ported to vonage, they had to do some type of purging on there side. Now that I am moving the number over here this coming week, I will have to call Vonage to do the same so it is not cached in there system.

Was it a simple phone call to Verizon that took care of the problem?

[abaldish]

Was it a simple phone call to Verizon that took care of the problem?

depends on who answers the phone there, lol i know it took about 24hrs for mine to clear up.

[mike770]

Thanks alot!

[jnuzzi]

I had a similar issue when I ported from Vonage. I had to call them and ask them to remove my number from their database. Only after this was completed could other Vonage users call my number.

[DracoFelis]

I recently had my telephone number ported from verizon and certain verizon customers, not all, are unable to call me. They hear absolutely nothing. No ringtone, no busy signal, nothing.

I called Viatalk tech support and I was told that I should call Verizon on monday to have my "translations" purged out of their system.
I know it puts us poor customers in the middle, but ViaTalk is correct on this point. When you have a number that works (and can be called) by some telcos, but fails when called by other telcos, the problem is almost always with the telco that can't call your number (vs the company that you have your number with). So ViaTalk really isn't in a position to "fix" this issue, because it's not their end of the call that is acting up. :(

So ViaTalk gave you the correct advance (even if your wife might not see it that way). Since the problem is that the calling telco (in this case Verizon) hadn't yet properly updated their phone equipment to send the calls to ViaTalk, than the "fix" had to occur with the calling telco as well. So having some Verizon customer call their tech support about not being able to properly reach your phone number, really is the proper advice in this situation. It may be a PITA for the poor customer caught in the middle, but as soon as those routing tables get updated the problem should go away. So this issue will get better as time goes on (and will often "fix itself", if you just wait a few weeks for the telcos to update their routing tables on their own)!

BTW:
This is really a problem with any "number porting", not with VoIP per se. i.e. you might have run into exactly the same issue, had you ported your number to a different telco/POTS service (instead of porting to ViaTalk, like you did), because it is the porting" process itself that requires the update to the various telco's "routing tables", and until those telcos get their routing tables updated you will have problems with people being able to call you...

[mike770]

I know it puts us poor customers in the middle, but ViaTalk is correct on this point. When you have a number that works (and can be called) by some telcos, but fails when called by other telcos, the problem is almost always with the telco that can't call your number (vs the company that you have your number with). So ViaTalk really isn't in a position to "fix" this issue, because it's not their end of the call that is acting up. :(

So ViaTalk gave you the correct advance (even if your wife might not see it that way). Since the problem is that the calling telco (in this case Verizon) hadn't yet properly updated their phone equipment to send the calls to ViaTalk, than the "fix" had to occur with the calling telco as well. So having some Verizon customer call their tech support about not being able to properly reach your phone number, really is the proper advice in this situation. It may be a PITA for the poor customer caught in the middle, but as soon as those routing tables get updated the problem should go away. So this issue will get better as time goes on (and will often "fix itself", if you just wait a few weeks for the telcos to update their routing tables on their own)!

BTW:
This is really a problem with any "number porting", not with VoIP per se. i.e. you might have run into exactly the same issue, had you ported your number to a different telco/POTS service (instead of porting to ViaTalk, like you did), because it is the porting" process itself that requires the update to the various telco's "routing tables", and until those telcos get their routing tables updated you will have problems with people being able to call you...



Thanks for the clarification...

As it turns out I had my sister and my mother open a "Trouble Ticket" with Verizon to fix the problem. They are the only one, that I can tell, that are having the problem.

[chas3]

A friend of mine had this same trouble with people in a small private phone company area could not call the new VT line. Like said above, that phone company never did the database updates.
Guess just about the same thing if someone didn't update a few DNS servers when a website IP changes.
It is amazing that this porting stuff works as well as it does.

[mike770]

Well the "Trouble Tickets" opened by my family members that could not reach me fixed the problem.

[DracoFelis]

Well the "Trouble Tickets" opened by my family members that could not reach me fixed the problem.
Glad to hear they got it fixed! And in most cases the problem will "stay fixed" (for calls from that telco) once they fix it right the first time. So hopefully you will be able to win back some of your wife's trust. ;)

[mike770]

When I show my wife the saving that switching to ViaTalk gave us,she'll be happy. :)

[connervt]

Yeah, now she knows how much more she can spend shopping... :eek:

[mike770]

Yeah, now she knows how much more she can spend shopping... :eek:

Maybe I should keep her clueless on the savings. LOL :D