obi202 won't dial last digit of phone number, won't ring inbound.
AngryOldman:
Hi Everyone,
I've just finished setting up an Obi202 according to this guide: http://www.googlevoiceforcanadians.com/wp-content/uploads/2014/09/Updated-OBi100-Guide-1.pdf
It seems to be ok, contacts my SIP provider (freephoneline.ca) just fine. However, it only sends 9 digits instead of 10, because the message comes back from it saying, "The number you dialed, 613 xxx xxx has not received a response from the service provider." I used 613 since I'm in Ottawa, and the x's could be any digits. It only reads back the first nine, and not the tenth... even if I press the last digit many times in frustration, which I've tried.
Digit map is (911|[2 -‐ 9]xx xxx xxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|*98|[6 -‐ 7]x*xxxxxxxxxxx.) which should be fine from what I can tell. I even added a "." in after the second rule to see if that was what was limiting it, like this: (911|[2 -‐ 9]xx xxx xxxx.|1xxxxxxxxxx|011xxxxxxxxxxxx.|*98|[6 -‐ 7]x*xxxxxxxxxxx.)
Didn't make any difference. On inbound calls, it goes straight to VM. Incidentally, FPL's softphone makes outbound calls fine, but also goes straight to VM (after making some clicking noises that sounds like the old digipulse noise you used to hear when you picked up an extension or a party line and someone else was already dialing)
Searched the forums, used Google, but to no avail. Any help would be much appreciated.
Cheers,
A. Oldman
azrobert:
Try this:
(911|[2-9]xx xxx xxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|*98|[6-7]x*xxxxxxxxxxx.)
AngryOldman:
Thanks Azrobert! That solved the problem of the last digit being dropped. Looks like my copy/paste from the PDF was at fault (along with my not proof-reading). However, it now just lists the full number and then says the same thing, "The number you dialed 613xxxxxxx has not received a response from the service provider." So, basically the same behaviour and the missing digit wasn't the main problem I guess :( Inbound calls still go straight to VM.
Inbound and outbound calls to the softphone work properly now, at least.
Oh, and as an aside... a SIP scanner was able to find me and ring the obi last night (right after I went to bed ::)
I haven't fiddled with the security setup because I want to get the thing running first then foil the scanners with oleg's method.
So... I still can't get the freephoneline to work with the obi, but the softphone works fine.
Brisk:
Quote from: AngryOldman on January 20, 2016, 08:52:20 am
Looks like my copy/paste from the PDF was at fault (along with my not proof-reading).
The official setup guides are found here:
1) http://forum.fongo.com/viewtopic.php?f=15&t=16090
2) Use http://forum.fongo.com/viewtopic.php?f=15&t=16196 if you're forced to use a modem/router combo, issued by your ISP, that doesn't allow you to disable SIP ALG.
The official Freephoneline forum is over here: http://forum.fongo.com/viewforum.php?f=8.
011xxxxxxxxxxxx. is wrong. It should be 011xx.
[6-7]x*xxxxxxxxxxx. should just be deleted since it makes no sense at all and can't logically apply to anything.
I would switch to
(911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xx.|*98)
Quote
"The number you dialed 613xxxxxxx has not received a response from the service provider."
Was there also a 3 digit SIP error code given?
https://en.wikipedia.org/wiki/List_of_SIP_response_codes
Is your ATA actually registered with the provider? Login at https://www.freephoneline.ca/showSipSettings and check your SIP status.
By the way, unless you pay $70+tax to FPL for its VoIP unlock key, you're not going to be able to make calls using your ATA.
Otherwise, this sounds like a dial plan issue. You should be providing your Phone Port Digitmap and Phone Port Ouboundcalle route when posting: Physical Interfaces-->Phone Port-->DigitMap
a) Ensure you're not running the softphone on your computer when attempting to use the ATA. Multiple device registrations with Freephoneline using the same account is only going to permit the most recent device registration. Also multiple registration attempts within a short period will also result in a temporary IP ban.
Quote
Oh, and as an aside... a SIP scanner was able to find me
Make sure that you are not port forwarding anything or using DMZ in your router.
b) After navigating to Voice Services-->SPFPL Service-->Calling Features
Make sure that the following are blank or not enabled:
CallForwardUnconditionalEnable
CallForwardUnconditionalNumber
CallForwardOnBusyEnable
CallForwardOnBusyNumber
CallForwardOnNoAnswerEnable
CallForwardOnNoAnswerNumber
Actually, considering that you may have been hacked, I would recommend a factory reset:
http://www.obihai.com/faq/Troubleshooting-sec/How-to-Factory-Reset
c) I found a good post at another forum that may help you.
http://forums.redflagdeals.com/merged-freephoneline-ca-free-local-soft-phone-line-lifetime-voip-821229/282/#post22680421
I would establish security first before attempting to configure anything. There's just no point, considering a hacker could break into your ATA and change settings.
d) Then, after resetting your ATA, for inital setup, I suggest using the Obitalk web portal instead to help avoid basic configuration issues: http://forums.redflagdeals.com/solved-almost-bell-port-out-freephoneline-complete-how-change-obihai-setting-1902015/4/#post24868177
This post has pictures: http://forums.redflagdeals.com/solved-almost-bell-port-out-freephoneline-complete-how-change-obihai-setting-1902015/4/#post24877279
There are some posts in that thread that should help you.
azrobert:
Quote
011xxxxxxxxxxxx. is wrong. It should be 011xx.
That rule is only wrong if the international number is less than 11 digits. IMHO it's better than "011xx." and can prevent dialing a wrong number. If you skip a digit and only dial 10 digits instead of 11, the call will fail. Using rule "011xx." the call will be routed to your provider and possibly connect to someone in a different country.
Navigation
[0] Message Index
[#] Next page