Dial plan explanation
RonR:
Quote from: TomTN on May 13, 2011, 01:45:40 pm
911: not tested, but add "|911|" to the digital map anyway
No change is needed for 911. 911 is already handled at the top-most level of PHONE Port DigitMap and sent to the LINE Port automatically. |911| should not be added to the LINE Port DigitMap.
Quote from: TomTN on May 13, 2011, 01:45:40 pm
611, 511, 411: working (add "|611|511|411|" to the digital map)
Your very explicit list didn't include these. :)
Quote from: TomTN on May 13, 2011, 01:45:40 pm
toll free: 11 digits or 10 digits : working
Just for info...
11-digit toll free numbers are going to Bell South.
10-digit toll free numbers are going to Google Voice
If you want 10-digit toll free numbers to also go to Bell South, that's doable.
Quote from: TomTN on May 13, 2011, 01:45:40 pm
calls to 407 local area code: sometimes recieving error msg
"We are sorry your call did not go through". But, If I try to dial it again the 2nd, the 3rd, or the 4th time, the call will eventually go thru.
I seriously doubt this is a DigitMap problem. This sounds like a DTMF dialing problem between the OBi and Bell South. When this error occurs, review the Call History and verify it shows the correct number was dialed. If the correct number was dialed, it's probably a DTMF problem.
Quote from: TomTN on May 13, 2011, 01:45:40 pm
calls to 321 area code numbers: if 321 exchanges are local, then the call go thru.
if 321 exchanges are local toll or long distance, then need to dial them as long distance call; otherwise recieving msg "we are sorry. when placing local call, it's neccessary to dial 1 plus area code plus seven digits number to complete this call."
If you have a relatively small number of 321 local exchanges, it may be possible to do something, but this could get messy real fast if the list is long.
TomTN:
Quote from: RonR on May 13, 2011, 03:05:45 pm
Quote from: TomTN on May 13, 2011, 01:45:40 pm
911: not tested, but add "|911|" to the digital map anyway
No change is needed for 911. 911 is already handled at the top-most level of PHONE Port DigitMap and sent to the LINE Port automatically. |911| should not be added to the LINE Port DigitMap.
Quote
ok. "|911|" removed from the digital map.
Quote from: TomTN on May 13, 2011, 01:45:40 pm
611, 511, 411: working (add "|611|511|411|" to the digital map)
Your very explicit list didn't include these. :)
Quote from: TomTN on May 13, 2011, 01:45:40 pm
toll free: 11 digits or 10 digits : working
Just for info...
11-digit toll free numbers are going to Bell South.
10-digit toll free numbers are going to Google Voice
If you want 10-digit toll free numbers to also go to Bell South, that's doable.
Quote
I got this part.
Quote from: TomTN on May 13, 2011, 01:45:40 pm
calls to 407 local area code: sometimes recieving error msg
"We are sorry your call did not go through". But, If I try to dial it again the 2nd, the 3rd, or the 4th time, the call will eventually go thru.
I seriously doubt this is a DigitMap problem. This sounds like a DTMF dialing problem between the OBi and Bell South. When this error occurs, review the Call History and verify it shows the correct number was dialed. If the correct number was dialed, it's probably a DTMF problem.
Quote
can you tell me how to troubleshoot DTMF if this prob. occur again?
Quote from: TomTN on May 13, 2011, 01:45:40 pm
calls to 321 area code numbers: if 321 exchanges are local, then the call go thru.
if 321 exchanges are local toll or long distance, then need to dial them as long distance call; otherwise recieving msg "we are sorry. when placing local call, it's neccessary to dial 1 plus area code plus seven digits number to complete this call."
If you have a relatively small number of 321 local exchanges, it may be possible to do something, but this could get messy real fast if the list is long.
Quote
if recieve error msg, then I dial it as long distance.
RonR:
Here's an updated DigitMap so that all toll free calls go to Bell South:
(411|511|611|1800xxxxxxx|1888xxxxxxx|1877xxxxxxx|1866xxxxxxx|1855xxxxxxx|
<1>800xxxxxxx|<1>888xxxxxxx|<1>877xxxxxxx|<1>866xxxxxxx|<1>855xxxxxxx|011xx.|
321xxxxxxx|407xxxxxxx|<**1>1xxxxxxxxxx|<**11>xxxxxxxxxx)
Can you determine which 321 area code exchanges are local to you? If so and the list isn't too big, we should be able to make everything work automatically.
There's supposed to be a new firmware update soon to correct some DTMF problems. I'd wait for it before trying anything yourself. If you get the error again, check the Call History to make sure the OBi had dialed the correct number.
TomTN:
thanks for the newly updated digital map.
I just look up area codes exchanges that local to my number in yellow pages, and here it is:
407 ->= 300 exchanges
321 ->= 120
352 ->= 16
surprise.
not ALL of 407 area codes exchanges are local to me, but only of 300 listed in the yellow pages.
Wish that somehow Obi box can automatically route local exchange to my PSTN,
and the rest to Google voice
Waiting for the DTMF fix in the new firmware.
what you think?
RonR:
Quote from: TomTN on May 13, 2011, 07:39:51 pm
thanks for the newly updated digital map.
I just look up area codes exchanges that local to my number in yellow pages, and here it is:
407 ->= 300 exchanges
321 ->= 120
352 ->= 16
surprise.
not ALL of 407 area codes exchanges are local to me, but only of 300 listed in the yellow pages.
Wish that somehow Obi box can automatically route local exchange to my PSTN,
and the rest to Google voice
Waiting for the DTMF fix in the new firmware.
what you think?
There's no way to configure 436 special cases. Unless there's a short list of non-local exchanges (to go the other direction), I'm out of ideas.
Navigation
[0] Message Index
[#] Next page
[*] Previous page