RESOLVED ! Unable to dial out of PSTN line from a remote Obi throuh AA
RonR:
QBZappy,
Those changes won't fix the current problem as the existing DigitMap ultimately lets anything through with the 'xx.' rule at the end. While there may be optimizations that can be done later to accommodate the non-US dialing formats and to speed things up, it's a bad idea to be making unnecessary changes when something is not working and you're trying to get to the root cause. If you accidentally introduce new problems before you find and fix the old ones, it just makes the job harder.
Assuming Obitalk has the same corruption in his Auto Attendant DigitMap and OutboundCallRoute that I'm seeing in mine, I think the problem is that calls from the Auto Attendant are being routed out the OBiTALK port instead of the LINE port (hence no call completion). I didn't notice the corruption right away as I use custom DigitMap's and CallRoute's instead of the defaults.
QBZappy:
RonR,
Hi, Don't you sleep? :D
I was scratching my head wondering where you were getting those values. It did not match up with my default values for the settings you were describing. My values where not corrupted.
It might be a good time to introduce an idea where people with issues could provide some basic info about their OBi configurations according to some template design. This designed form should be a sticky where everyone can refer to it. (Please post your question in the following format) This would make the process of trouble shooting more efficient without resorting to the back and forth. What do you think would be the minimum info you would like to see to get a big picture.
RonR:
QBZappy,
My guess is Obihai introduced this problem in the non-Gmail account beta release that I and a number of others received. Did you not request nor receive this particular update? If Obitalk doesn't have the corrupted (or whatever they are) Auto Attendant entries then the mystery may still not be solved.
jimates:
I wanted to compare the maps in the two firmware versions but I can't access my #2 obi's web interface. I get an xml error message
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
The stylesheet does not contain a document element. The stylesheet may be empty, or it may not be a well-formed XML documen...
This is what I have on my beta version, which is what Ron has.
DigitMap
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**9(Mpp))
OutboundCallRoute
{([1-9]x?*(Mpli)):pp},{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp}
QBZappy, post yours from the standard FW
QBZappy:
Default setting on my OBi: SoftwareVersion= 1.1.0 (Build: 1892)
Voice Services->Auto Attendant->DigitMap=
([1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))
Voice Services->Auto Attendant->OutboundCallRoute =
{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
Navigation
[0] Message Index
[#] Next page
[*] Previous page