RESOLVED ! Unable to dial out of PSTN line from a remote Obi throuh AA
Obitalk:
Can someone provide be he;lp is troubleshooting the following issue:
I'm placing a call from a US based Obi device to a Remote Obi device in a different country.
I initiate the call via **9 and the obi device number
I receive the automated attendent and press 2 and then followed by **8 and the PSTN number
I hear the tone of Obi trying to initiate the call (ie. ringing tone)
But the call never completes.
In order to troubleshoot:
I requested someone at the remote location to pickup the phone of the remote obi device and dial **8 and the PSTN number
The person is able to successfully place the call
What would be the issue in dialing the remote obi from US and completing the PSTN call out of the remote Obi device in remote country.
Any help would be appreciated.
QBZappy:
Hi,
It would help pinpoint problem if you show your OBiTALK InboundCallRoute
Obitalk:
Thank you QBZappy
Here is my ObiTalkInBoundCallRoute
{(290700000|200111222|200222333)>(xx.):SP1},{(290700000|200111222|200222333):aa},{ph}
MichiganTelephone:
Question: Did you configure both devices using the OBiTALK portal or did you configure them manually? If you configured the remote unit manually, then what you may need to do is go to the remote unit's Voice Services, Auto Attendant menu and check these things (these are probably NOT the problem, but just to be sure):
Is the default checkbox still checked for DigitMap?Is the default checkbox still checked for OutboundCallRoute?One thing I'm thinking might be an issue is if you are calling numbers that do not share NANP dial patterns. By default the OBi assumes a NANP (USA/Canada) dial pattern. So when you dial a number, it might not be sending the digits to the PSTN port that you think it is. A way to check that would be to look at the Call History (under the status section) and look to see if you can find the failed calls. See if the numbers it called were the actual numbers you dialed. You might find that it chopped off some digits or something.
If it's the latter problem I'm not sure offhand which pattern would have to be modified to fix it, but I'll wait for your response before I say any more. It might be helpful, though, to see an actual example of a number you're trying to call (**8 and then what? You can replace the last few digits with X's) and also what actually appeared in the call history.
QBZappy:
Obitalk,
Your complete configuration is not clear from your post. I will try to guide you assuming a simple configuration setup. If you keep it simple and only have the Pots line and the OBi service at the far end. You should set Outbound Settings->Attendant PrimaryLine=PSTN line. Set as the primary line you will not need to press **8 to dial out from the AA. You hear the ringing tone. Gives the impression the call is going through. This setup will at least simplify the trouble shooting by giving you the ability to direct dial after you get past the AA. What country is the far end OBi located in?
Look in the Setup Wizard section of the OBi unit:
What is your "Outbound Settings->Attendant PrimaryLine" setting?
{290381063>(xx.):sp2},{(290381063|200883755):aa},{ph} <-- Is the setting of the OBi at the far end?
What is the digitmap of the far end OBi "Physical Interfaces->LINE Port->DigitMap" ? Configure this into a format which makes sense in the region where the far end OBi is located.
Let us know you results.
Navigation
[0] Message Index
[#] Next page