Certain call combinations return a busy signal - Obi 100 with Vitelity

[RichardC]

I have an Obi 100 on a Vitelity subaccount, and most of the outgoing calls work fine.  However, certain calls within my own area code (706) are always getting a busy signal.  Prefixes 963 and 391 don't work, but a couple of test calls to 886 prefix connect normally.

Is there something here that looks like a special code to the Obi, and keeps it from passing the digits?  Again, that 's numbers starting with 706963, and 706391.

Anyone have any ideas?

Thanks
Richard

[Mango]

You can check your OBi's call history, and Vitelity's call history, to determine how far the calls are going.  From there you'll know where to troubleshoot next.

[cluckercreek]

It sounds to me that those areas affected are due to high connect costs. I have that problem with TDS Telecom areas, all local calls, which I even have to pay Google Voice to connect as well as Vestalink.