Can't make obi to obi calls anymore using **9 (got busy tone)

(1/4) > >>

tsaisfamily:
I have a OBi110 at home and it has been working fine until recently. I am not sure what got changed but I can't seem to make any **9 calls anymore, all I got is the fast busy tone, including trying the echo number **9 222 222 222. But everything else seems ok. Other people with obitalk can call me via **9 ok. And I can take incoming and make outgoing calls via GV (**1) ok too. The obi web portal shows my device is ok (green). I did upgrade my firmware to 1.3.0 (Build: 2824) recently although not sure if this is related to the problem I am having.
I have tried hard reset to factory default but still no luck. I have also tried to add my device to DMZ of my router and no help either. Any clue is appreciated!

drgeoff:
Log in to the local web interface of your OBi and check some settings:

1.  Under Voice services, OBiTALK service, ensure the Enable box is ticked.

2.  Under Physical Interfaces, Phone Port,  what **9 entries are in the Digit Map and OutboundCallRoute?

tsaisfamily:
Thank you for the help.
1. Yes, the enable box is checked under Voice Service, OBiTALK service.

2. Here is the digit map
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp)|(Mpli))

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

drgeoff:
I don't see anything untoward with those.

I should also have asked about the OBiTALK Digit Map.  I expect you will find it is the default (<ob>xxxxxxxxx|obxxxxxxxxx) in which case I'm at a loss as to why it isn't working.

This isn't the sort of problem for which I would expect your router to be responsible.

tsaisfamily:
Right, every setting should be factory default since I hard reset it. I guess that I will have to ask official support from OBI. Thanks for your help!

Navigation

[0] Message Index

[#] Next page