[jeffml]

When dialing my BV number from Cingular I receive a "can not be completed" message. I can call the number from Vonage, Stanaphone, Nboom, and Cox but not through my cell phone. Cingular says it is a problem on the receiving end (don't they always).

I've enabled Do Not Disturb so as to eliminate any ATA issues. I've sent an email to support but I have a feeling this is the start of a lot of finger pointing.

Has anyone else had problems like this?

[scottr]

I have the same problem. I first noticed this last week, and found the time to report the issue today. (I'm able to receive calls on my Broadvoice number from both SBC and TDS PSTN networks.)

First I called Cingular. After a fairly lengthy debug, they told me to contact my provider.

Then, I emailed Broadvoice and gave them the details. It took about as long to detail the problem and ship the email as it took to do the debug with Cingular. BV responded within 5 minutes but unfortunately directed me to tell Cingular to fix their routing issue.

I'm not quite sure who I should get irate with first. Probably Cingular.

[mberlant]

The problem is almost certainly within Cingular. You need to tell them that you cannot complete calls with them to 311-555-xxxx exchange, at least when you are in ZZZ city. Their engineers will have to investigate their routing tables and will probably find an omission or a typo in the line that points to your BV exchange. It will take them a couple of days to fix, and you'll be in business.

Since you can call this same exchange from other providers it is not at all likely to be BroadVoice's problem.

[PhoneBoy]

Come to think of it, I can't call my BroadVoice number from my Cingular phone either...

[scunyngham]

I had a similar problem last week with VP. I could call any of my VP numbers direct but except from any Verizon line in my immediate area. In the testing Verizon from other states could call fine. I took a day to find but the problem was in the database 2 levels above VP at one of their upline providers.

BTW, the VP support was great in this as most others problems.

[scottr]

In fact, I did tell Cingular that it was likely to be a routing issue to the specific area code and exchange, but their 2nd level support said "not our problem." (I was dee-niiiiiiied...)

I've asked BV support to take a look at this thread and to escalate to their upline provider for the exchange in question. I'm about to call Cingular and ask them to do the same.

[jeffml]

Originally Posted by scottr

I've asked BV support to take a look at this thread and to escalate to their upline provider for the exchange in question. I'm about to call Cingular and ask them to do the same.

I'm currently on hold with AT&T/Cingular Support but just in case I don't get anywhere again with them....

520-208-xxxx is the exchange I'm having problems with.

[mberlant]

When Cingular (or whoever) on the sending end says, "Not my problem," ask them to call you on your BV line using their service.

[PhoneBoy]

Problem cleared this morning without me calling. Go figure.

[mberlant]

My money would be on Cingular finally updating their routing tables.