OBiTALK Community

General Support => Day-to-Day Use => Topic started by: Obitalk on March 12, 2011, 09:10:22 AM

Title: RESOLVED ! Unable to dial out of PSTN line from a remote Obi throuh AA
Post by: Obitalk on March 12, 2011, 09:10:22 AM
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.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 12, 2011, 09:58:16 AM
Hi,

It would help pinpoint problem if you show your OBiTALK InboundCallRoute
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 12, 2011, 10:33:10 AM
Thank you QBZappy

Here is my ObiTalkInBoundCallRoute

{(290700000|200111222|200222333)>(xx.):SP1},{(290700000|200111222|200222333):aa},{ph}
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: MichiganTelephone on March 12, 2011, 11:57:56 AM
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):
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.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 12, 2011, 01:14:48 PM
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.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 12, 2011, 08:15:12 PM
Thanks for the input MichiganTelephone,

I configured both devices using the OBiTALK portal.
DitiMap default is still checked
OutboundCallRoute default is still checked
The remote destination I'm trying to dial is Sri Lanka

These are the two different logs:

This is the call history when the person tried dialling the phone using **8 (The call was successful)

Terminal ID PHONE1 LINE1
Peer Name   
Peer Number **80776512345 0776512345
Direction Outbound Outbound
07:41:13 New Call 
07:41:18  Call Connected
07:41:39 End Call

This is the log when I dial through the auto attendant:

Terminal ID AA1 LINE1
Peer Name   
Peer Number 0771234567 0771234567
Direction Outbound Outbound
08:39:09 New Call 
08:39:14  Call Connected
08:39:14 New Peer: P2P1:Name=USLINE#1     Number=200123456 Transfer Target
08:40:00 End Call

The call log although says connected, on the second example, I'm still not able to connect.

===============================================================================

Thanks for the input QBZappy,

I took the advice and made the changes though OBiTALK portal.

Now the Autoattendant Primary Line is set to PSTN Line

I'm trying to dial Sri Lanka (The phone number is 7 digits long)

But in this particular instance for testing purpose I'm trying to dial a mobile number and it needs to be prefixed by a 0 then followed by 776512345

So I'm dialling 0776512345 after pressing 2 when the AA answers

Look in the Setup Wizard section of the OBi unit:
What is your "Outbound Settings->Attendant PrimaryLine" setting? This is set to PSTN Line

{(290712345|200512345|200212345)>(xx.):LI},{(290712345|200512345|200212345):aa},{ph}

What is the digitmap of the far end OBi "Physical Interfaces->LINE Port->DigitMap" ? The digitmap is as follows: (xxxxxxxS4|1xxxxxxxxxx|xx.)

===================================================================================

I still haven't had any luck connecting via the line port using AA
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 12, 2011, 08:55:33 PM
You show the peer number on the AA1 log entry as being different from the PHONE1 log entry.  Are they actually different or was that accidental in your effort to obscure the real number?
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 12, 2011, 09:45:53 PM
I just spotted something fishy in two Auto Attendant default settings.


Go to:

Voice Services -> Auto Attendant -> DigitMap

and uncheck default.  Then delete this part at the beginning of the line:

[1-9]x?*(Mpli)|

Go to:

Voice Services -> Auto Attendant -> OutboundCallRoute

and uncheck default.  Then delete this part at the beginning of the line:

{([1-9]x?*(Mpli)):pp},


Then try your call via the Auto Attendant.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: MichiganTelephone on March 12, 2011, 09:49:45 PM
I understand that you've obscured the actual numbers here, but in order for the test to be valid you must try calling the same number that was successfully called from the phone port.  Otherwise you may run into a situation where the one number works fine and the other one won't go through, and that's the problem.

Other than that, it sure looks like it's actually calling the number you dialed. So my suspicion is that the problem may be with the called number, not with the way the device is routing the call.  Try calling two or three different numbers, preferably one or two different landlines and one or two different mobiles.  If the issue isn't with the called number, then I'm stumped.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 12, 2011, 11:26:04 PM
Obitalk,

1) improve your "Physical Interfaces->LINE Port->DigitMap" (Digitmap for calls made on this trunk Mli)

Current setting=(xxxxxxxS4|1xxxxxxxxxx|xx.)
Consider setting=(77xxx xxxxS4|077xxx xxxxS4|xx.)  <--(Not sure if you want other area codes in the dial plan)

Explanation:
7 digit phone number with 2 digit (landline calls) or 3 digit (cellular calls) area code.
I placed what I am just assuming the more general user dialing senario first on the left (you reverse this if cell calling is more common). Next the 3 digit cellular dial plan. Then a general dial plan to catch everthing else.



2) For ease of use, consider placing frequently called numbers in the speed dial. After AA picks up you would just press "speed dial number+#"
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 13, 2011, 12:01:03 AM
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.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 13, 2011, 07:45:31 AM
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.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 13, 2011, 11:00:38 AM
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.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: jimates on March 13, 2011, 11:52:25 AM
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
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 13, 2011, 12:09:54 PM
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}

Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: MichiganTelephone on March 13, 2011, 12:15:08 PM
From SoftwareVersion   1.1.0 (Build: 1892), these are the default settings on my devices:

Voice Services -> Auto Attendant -> DigitMap
OBi110:
([1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))
OBi100:
([1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**9(Mpp))

Voice Services -> Auto Attendant -> OutboundCallRoute
OBi110:
{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
OBi100:
{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp}
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: jimates on March 13, 2011, 01:14:04 PM
He probably doesn't have the beta fw so it shouldn't need editing.

I don't know why they would need to be different anyways.

DigitMap
1.1.0
([1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))
beta
([1-9]x?*(Mpli)|[1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**9(Mpp))

OutboundCallRoute
1.1.0
{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
beta
{([1-9]x?*(Mpli)):pp},{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp}

I notice there is no rule for **8 in the beta.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 13, 2011, 03:00:23 PM
jimates,

Default settings: SoftwareVersion=1.1.0 (Build: 1892)

Physical Interfaces->PHONE Port->DigitMap->=

([1-9]|[1-9][0-9]|911|**0|***|#|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))


Physical Interfaces->PHONE Port->OutboundCallRoute->=

{(<#:>|911):li},{**0:aa},{***:aa2},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 13, 2011, 06:30:00 PM
Quote from: jimates on March 13, 2011, 03:29:18 PMI changed my settings on the Phone Port. I noticed no difference, there is still a 20 second delay in the outgoing call.
Let's move the discussion of dialing delays to:

http://www.obitalk.com/forum/index.php?topic=337.0

and keep this thread on topic to Obitalk's problem.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 14, 2011, 10:20:36 PM
Thanks for input RonR, MichiganTelephone, QBZappy and Jimates

My auto attendant digit map is as follows:

([1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))

And my outbound call route is as follows:

{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}

So I guess this mean I don't need to change anything correct ?

I have made a little bit of progress. (The changes that were incorporated were the one suggested by QBZappy so that I don't have to dial **8 and just dial directly)

When I try dialling out of the auto attendant at the remote obi, the phone number that I dialled rings and also had the correct caller id. But I cannot hear the voice at the other end nor I cannot hear them either. Also the call gets disconnected and I get back the dial tone.

Any suggestions would be appreciated.

Thanks
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 14, 2011, 10:37:07 PM
Quote from: Obitalk on March 14, 2011, 10:20:36 PMMy auto attendant digit map is as follows:

([1-9]|[1-9][0-9]|<00:$1>|0|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))

And my outbound call route is as follows:

{0:ph},{(Mpli):pli},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp}

So I guess this mean I don't need to change anything correct ?
Correct.

The mystery continues, I guess.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 14, 2011, 11:10:45 PM
Obitalk,

Hi,

Can you get a screen capture of the "Call Status" OBi web page while the call is ringing, and of the call history. There might be some useful info in there. (From both OBi's) Attach it as an image on your post. JPG image works well.

Are the OBi's at both ends behind one or 2 routers?

Try this:
Port forward the configured RTP ports configured in the OBi web page to the each of the OBi units:
ITSP Profile A or B->RTP->LocalPortMin         
ITSP Profile A or B->RTP->LocalPortMax
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: QBZappy on March 15, 2011, 07:22:55 AM
Obitalk,

I remembered you are dialing **9, meaning you are using the OBitalk service and not a SIP account to call the other OBi. Then port forwarding the Min and Max port numbers I made reference to should not make any difference in your setup.

I think the OBi severs work like a "mediation server" all the OBis can connect to their server. If two OBis want to call each other the OBi server will negotiate the connection between the two units and presumably leaves the call path leaving the two OBi units to be peer to peer environment. I think this is why it is not necessary to port forward the OBi service. It resolves the NAT issue in this way. A similar technique is used by various other services. I can think of the Hamachi VPN which works this way.

I think this is the first time this topic has been brought up. Maybe the OBi people can confirm if this is the underlying concept of the OBi service.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: OBiSupport on March 15, 2011, 10:25:59 AM
Obitalk,

Please confirm that at this time, you can dial another OBi number and
exchange audio fine ?
The only problem right now, is calling out via PSTN on another OBi ?

Can you please email support@obihai.com on this ?
Please indicate the OBi number where you are calling from, and also
the OBi number of the unit that is calling out via PSTN.

-Obihai Support Team
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 15, 2011, 02:24:58 PM
Hi ObiSupport,
Last time I called the remote Obi I let the AA continue by pressing '1' and was able to talk to the person at the other end. That was about 5 or 6 days ago. I will make sure I can still do the same and update the staus. Also I have noticed that sometime on the OBiTALK Service Status it indicates Backing Off most of the time while the US based Obi always indicates Normal Mode

I will email Obisupport the requested Obi Numbers.

Thank you
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 15, 2011, 08:46:30 PM
Another symptom I have noticed is that once the call fails to connect through the PSTN line, I'm unable to access the remote Obi web interface for 5-10 mins. Thanks
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 15, 2011, 08:51:21 PM
Is there anyone there who can watch it and try to use it locally while it's in that state.  It would be interesting to know if it's rebooting after 5 - 10 minutes and that's what brings it back to life.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 16, 2011, 05:30:51 AM
Obisupport,

I can confirm that both parties can hear audio and the call is ok when dialling **9 to the remote Obi.

Thanks
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 16, 2011, 06:04:32 AM
RonR

I think you are on the right track. I think the remote Obi rebooted after the PSTN called failed.

See below:

HardwareVersion 2.8 
SoftwareVersion 1.1.0 (Build: 1892) 
SystemTime 05:47:15 01/-40176/2010, Monday 
UpTime 0 Days 0:17:15 (6)

Uptime of 17mins. I couldn't access it for approximately 15mins.

Thanks
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 16, 2011, 10:23:49 AM
Quote from: Obitalk on March 16, 2011, 06:04:32 AMHardwareVersion 2.8 
SoftwareVersion 1.1.0 (Build: 1892) 
SystemTime 05:47:15 01/-40176/2010, Monday 
UpTime 0 Days 0:17:15 (6)
The Reboot Reason Code is suspicious looking, especially if this is a reproducible scenario:

6: New Profile Invoked AND Profile URL Changed

I believe that Reboot Reason Code would normally mean the OBi rebooted because it just received new provisioning info (but it could also be meaningless if the OBi rebooted because of an unexpected software malfunction).

I would suggest trying several more calls and observing whether each of them show the same Reboot Reason Code.  Then I would disable Auto Provisioning and try several more calls to see if the results change.

It's possible your calls through the Auto Attendant aren't happening because they're crashing the OBi for some reason.  You need to collect more data and symptoms in order to narrow down what's really occurring.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: MichiganTelephone on March 16, 2011, 10:40:11 AM
Quote from: RonR on March 16, 2011, 10:23:49 AMIt's possible your calls through the Auto Attendant aren't happening because they're crashing the OBi for some reason.  You need to collect more data and symptoms in order to narrow down what's really occurring.

Or, you know, he could contact Obihai support and let them work their magic, instead of taking orders from you.  ::)  They have diagnostic tools not available to the rest of us.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 16, 2011, 11:19:04 AM
Hi RonR and MichiganTelehone,

Thanks for all of your input.

Sometime you don't realize the little things like

1.) The Obi rebooting after the PSTN call failing
2.) ObiTalk network shows the status as backing off 50% of the time etc

Did I mention that I had a tough time factory reseting the unit. I did it via the IVR and then couldn't get it to succed even after the reboot of the unit. Then requested someone at the other end use a paper clip to reset the unit. After 5-10 try I was able to get the unit te reset.

Anyways every little bit helps and thank you for your continued support.

I did already provide both the Obi numbers to support@obihai.com. I hope they get back to me sometime.

Thanks
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 16, 2011, 11:32:49 AM
Quote from: Obitalk on March 16, 2011, 11:19:04 AM2.) ObiTalk network shows the status as backing off 50% of the time etc
I didn't mention it in my previous post, but there does appear to be something not quite right in the networking area.  The OBi's Real Time Clock is not getting set properly:

SystemTime 05:47:15 01/-40176/2010, Monday

Quote from: Obitalk on March 16, 2011, 11:19:04 AMDid I mention that I had a tough time factory reseting the unit. I did it via the IVR and then couldn't get it to succed even after the reboot of the unit. Then requested someone at the other end use a paper clip to reset the unit. After 5-10 try I was able to get the unit te reset.
I don't recall you mentioning it.  There is a known bug in the OBi that after a reset to factory defaults from the IVR (option eight), the OBi fails to reboot itself and is left in an indeterminate state until it's manually rebooted.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 16, 2011, 01:48:50 PM
I agree with you that there might be some network issue indicated by the incorrect time as well as the Obitalk service that showd the status of backing off. To make matters complicated, I'm able to call the Google Line on SP1 without any issues anytime. So I'm not sure whether its entirely a network issue and not an issue with the ObiTalk service.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: RonR on March 16, 2011, 03:20:38 PM
Others have reported unrelated issues with time synchronization, so it may not mean anything to your current problem.
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 17, 2011, 07:03:58 AM
Hi Obi support, Any luck on finding out what my issue with the device might be ?  Thanks
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: yhfung on March 17, 2011, 08:21:09 AM
Most of second-stage diallings in SPA3000 or SPA3102 have the same and well-known problems as you described.

You may consider by adjusting the gains (receive or transmit in either or both OBi devices) such that the analogue DTMF signals at the callee end are GOOD enough for the DTMF digit detection.


Hope this give you some direction to go.


YH

Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: obi-support2 on March 17, 2011, 03:59:31 PM
Obitalk,
Our support staff is checking your OBi configuration right now. They will continue to communicate with you directly over email. We may need to run some further diagnostics with your remote OBi in order to trouble shoot the root cause. Thanks for your patience.
Please do not hesitate to email support for status update or to provide further information.

-------

I also would like to make a quick note about the extra rule ([1-9]x?*(Mpli) in digit map
and {([1-9]x?*(Mpli)):pp} in call route. These are added to support a new feature in release 1.2, known as ad hoc 1-stage gateway dialing. Basically you can have a gateway's obi number configured in one of the 99 speed dial slots (1-99). Suppose this gateway obi does not require userid/password authentication for inbound 1-stage call (i.e., only based based on circle-of-trust), then one can dial
<speed-dial> * <target-number> to make a 1-stage call to the target number via the gateway (whose obi number is configured in the given <speed-dial>. For example, speed dial 8 = pp(ob200123456)).

About the missing **8 rule in OutboundCallRoute on some OBi. This was caused by an earlier bug in the OBiTALK portal that accidentally removed the rule from some obi units that are managed by the portal. This issue has been fixed and you will get back the correct OutboundCallRoute after resync'ing with the portal. We apologize for your inconvenience.


Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: OBiSupport on March 17, 2011, 04:14:33 PM
Obitalk,

You mentioned earlier that you ask someone at the remote location to press
**8<phonenum>>. You said that it is working at that place, that's good.
Can you also ask that person to press **0 (which AA will respond)
and then option 2, proceed to **8<phonenum> ?

This way, the person at the remote location is trying the same exact way
as what you do when you call in to AA.

This will need to be handled by the support team,
can you please email support@obihai.com with the answer to above.

Thanks
-Obihai Support Team
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 18, 2011, 08:17:11 AM
I requested the person at the remote end to dial

**8 (phone number) and it was successful. Both parties were able the hear each other

**0 Pressed 2 and then **8 (phone number) was also successful. Both parties were able to hear each other.

I'm emailing the same information to the support team.

Thanks
Title: Re: Unable to dial out of PSTN line from a remote Obi throuh automated attendent
Post by: Obitalk on March 22, 2011, 08:20:10 AM
Hello Obi Support,

I emailed support with some questions on the status and haven't heard back. Do you have any progress on finding the root cause of my issue ?

Thanks
Title: Re: RESOLVED ! Unable to dial out of PSTN line from a remote Obi throuh AA
Post by: Obitalk on April 20, 2011, 11:51:52 AM
This issue has been resolved thanks to suggestions made by Obi Support.

The root cause was a bad inline DSL filter on the LINE port. Once I was able to replace the inline filter, I'm able to place calls dialling the remote OBI --> using AA and then dialling out of the PSTN port.

Thank eveyone for suggestions in finding a resolution.