Verizon customers cant call me!???

[JBradM]

Ok here is the problem. I have recently switched to Cingular nationwide plan and was assigned a number with the prefix 483. I am assuming that this is a new prefix for this area becasue I have not talked to anyone or seen anyones phones with this! The probelm is customers from verizon are not able to call me......they get the error message "your call cannot be completed as dialed please check the number and try again"? I have tryed it with my parents and sisters phone who both have verizon and they do not work.....cingular said there was nothing wrong, verizon said they dont know!???!?!?!? so what do you think is the problem? I really want to get up and working or do something like change the number. Do yo uthink the prefix is the problem? Just to let you know, I know for a fact taht other cingular customers can call me as well as landline phones, i havent yet tryed other carriers. Please give me some feedback ASAP!

[JBradM]

Just to let you know I live in Florence, AL!

Try having verizon customers dial your home area code (the area code of the city in which you will be billed) before your number. This still may not work, but its a shot.

[JBradM]

Sorry forgot to post this, we have tryed calling my phone with and without the area code, still I get the same message.! Thanks though

[Jack]

Interesting one (go into a verizon store and make sure that your phone is programmed right)

Jack

[coalminer]

I had a similar probem with a Sprint number I had, the exchange was so new that people in the Alltell wireline customers could not call me, their call would get routed to the number in the 440 area code instead of 216 which was what I had. Couldnt really blame it on Sprint though, they did try to help, but was out of their control. After many calls to Alltel they finally updated their databases to make that call get routed correctly. Also had a friend that had a Nextel phone that couldnt call another friend with a Cingular phone, same thing, Nextel had to update their database to recongize that prefix in that area code. More than likely the problem will eventually correct itself, but you might be able to call Verizon and tell them that their system does not recognize that prefix, might be able to get it fixed quicker.

[roamer1]

Yes, it sounds like the prefix is a problem. This is something that Verizon needs to fix...they should be opening trouble tickets when their customers call about it...

-SC

[JBradM]

Well I talked with the cingular and verizon people it is verizons problem basically what it is the prefix hasnt been added to the system yet so the computer doesnt regonize it or something lik ethat! I am sure it will be fixed soon but I didnt want to wait so i changed the phone number to something that works! haha! It seems to me they should add the prefix and have it ready to go before anything ever is introduced!

[img]i/expressions/face-icon-small-blush.gif[/img] Your provider should be really embrassed for this problem! As a former Bell Employee all cell phones work off local switching equipment in the land line companies switching centers! It seems that the local operating company (in this area most likely BellSouth) did not do their job by programming the switch to accept the new area codes and exchanges.
This is a very comman problem and in no way the fault of the wireless carrier! It is the fault of the local land line carrier and when I did this work the wireless carriers called us all the time to get our switches corrected!

This is a major problem in areas where new area codes and exchanges are being put in all the time!

[cryogenic]

Roamer1 lives in GA, I wonder if he's seen any similar issues with Atlanta.... They were constantly adding area codes and exchanges there for awhile.

[WirelessBeachBum]

Most likely a problem in the translations, sounds like your number is not loaded in a switch somewhere, sometimes it can be the wireless carrier or the landline, technically when a new exchange is released other companies have 90 days to load into their systems, however there are so many new prefixes half the time these do not get loaded until someone calls to complain, I've even ran into issues where copanies with larger PBX's don't have the exchange loaded as a local exchange, and have to call using the area code.