[SOLVED] Can't Call OBiTALK Test Number

<< < (2/4) > >>

RonR:
Quote from: longcliff on October 22, 2011, 11:04:05 am

I logged onto the OBi and checked the OBiTALK Service Status.  It says "Normal (User Mode)".


Then you should be able to call : **9 222 222 222

Check to make sure the following settings are at Default in the OBi:

Physical Interfaces -> PHONE Port -> DigitMap
Physical Interfaces -> PHONE Port -> OutboundCallRoute
Voice Services -> OBiTALK Service -> DigitMap

OBiSupport:
Please try to disable the firewall in your westell router.
check "No Security (None)"

This is also described in our FAQ:
http://www.obihai.com/docs/OBiFAQ.html#09

-Obihai Support Team

Gabi:
Quote from: RonR on October 22, 2011, 11:11:26 am

Quote from: longcliff on October 22, 2011, 11:04:05 am

I logged onto the OBi and checked the OBiTALK Service Status.  It says "Normal (User Mode)".


Then you should be able to call : **9 222 222 222

Check to make sure the following settings are at Default in the OBi:

Physical Interfaces -> PHONE Port -> DigitMap
Physical Interfaces -> PHONE Port -> OutboundCallRoute
Voice Services -> OBiTALK Service -> DigitMap



Making those changes worked it for me.
Thank you Ron.

RonR:
Quote from: longcliff on October 22, 2011, 11:04:05 am

I logged onto the OBi and checked the OBiTALK Service Status.  It says "Normal (User Mode)".

I'm going to try going with a static IP and setting up 'port forwarding' in my century link DSL modem (westell 7500).  I really don't know what I'm doing here, but that's what was required to get my xbox live to work through the westell 7500.


The fact that you're successfully connected to the OBiTALK voice server and can make/receive Google Voice calls pretty much says you don't have an IP address, Internet connectivity, port forwarding, or firewall problem.

Once you're showing connected to a particular service, "There is no call route available to complete your call" errors are almost always DigitMap/OutboundCallRoute configuration problems.

longcliff:
Quote from: RonR on October 22, 2011, 11:11:26 am

Quote from: longcliff on October 22, 2011, 11:04:05 am

I logged onto the OBi and checked the OBiTALK Service Status.  It says "Normal (User Mode)".


Then you should be able to call : **9 222 222 222

Check to make sure the following settings are at Default in the OBi:

Physical Interfaces -> PHONE Port -> DigitMap
Physical Interfaces -> PHONE Port -> OutboundCallRoute
Voice Services -> OBiTALK Service -> DigitMap



Ok, I'm getting closer.  Under Physical Interfaces -> PHONE Port -> Outbound Call Route, I did not have the default setting.  This is what I have:

{911:sp1},{([1-9]x?*(Mpli)):pp},{(&lt;#:&gt;|911):li},{**0:aa},{***:aa2},{(&lt;**1:&gt;(Msp1)):sp1},{(&lt;**2:&gt;(Msp2)):sp2},{(&lt;**8:&gt;(Mli)):li},{(&lt;**9:&gt;(Mpp)):pp},{(Mpli):pli}

If I change it to default (by marking the checkbox), submitting changes, and rebooting the system, I can call **9 222 222 222 and it works.  But, then the system reboots again (without being told to) and changes the Outbound Call Route back to the non-default setting above.  Then **9 222 222 222 stops working.

The other non-default setting I have is Physical Interfaces -> PHONE Port -> PrimaryLine, which is set to 'SP1 service'.

Does anybody know why my default setting for OutboundCallRoute is being changed?

Navigation

[0] Message Index

[#] Next page

[*] Previous page