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]

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)

"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.

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]

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.

[Brisk]

011xxxxxxxxxxxx. is wrong. It should be 011xx.

That rule is only wrong if the international number is less than 11 digits.

That was my concern.

OP can choose.

[AngryOldman]

azrobert, Brisk:

Thanks for your help with this, folks. I do really appreciate you taking the time to help me out. I've been under the weather since my last post, but about to get back at this right now and will try everything you've suggested. I have paid for the unlock key already, so that shouldn't be the issue, unless there's been an administrative screw-up at freephoneline. Certainly not out of the realm of possibility, I'm sure.
Thanks again, and I'll post my results tonight or tomorrow.
Cheers,
AO

[Brisk]

I have paid for the unlock key already, so that shouldn't be the issue, unless there's been an administrative screw-up at freephoneline.

If you need to contact them, use https://support.fongo.com/anonymous_requests/new

The source for the following information is found at http://forums.redflagdeals.com/merged-freephoneline-ca-free-local-soft-phone-line-lifetime-voip-821229/335/#post24955445



These instructions do not address "this account is not valid" messages (you would need to contact FPL/Fongo for that problem).
"If you're getting an "invalid account" error messages, or if people trying to call you are hearing "invalid account" or a busy signal, please log in to your account online at https://www.freephoneline.ca/followMeSettings and reset your Follow Me settings. Please ensure your temporary FPL number is not listed as one of the Follow Me numbers."

If you have calls going straight to voicemail, login at https://www.freephoneline.ca/voicemailSettings and ensure "Rings before voicemail" is greater than 1. Also, check in your ATA to ensure you don't have "Do Not Disturb" enabled. This is found after logging into your ATA or at Obitalk.com under Voice Services-->SP(FPL) Service-->Calling Features-->DoNotDisturbEnable. Ensure there is no checkmark under "Value".


Getting one way audio issues with an OBi200/202 and Freephoneline? Are incoming calls not ringing?

Often the problem is due to RTP packets not reaching the ATA. Common causes involve poorly functioning SIP ALGs (especially true with Netgear routers) in routers or NAT firewalls.

Hardware Specific Issues

A. Netgear R7000 routers
If you have a Netgear R7000 router, you may need to install XWRT firmware. Afterwards, turn off the router and the ATA. Turn on the router. Wait for it to be fully up and running (including wi-fi). Then turn on the ATA. Download XWRT-Vortex here: http://xvtx.ru/xwrt/download.htm

B. Nettis 4422 modem from Carry Telecom (click the "Internet" tab)
http://www.carrytel.ca/support.aspx
Q : DSL - My VoIP phone does not work with Netis 4422 modem.
A : Please download the newest Netis firmware at www.carrytel.ca/download/netis1228.zip. Unzip the netis1228.zip file and update the firmware file netis1228.img for your modem. The new firmware has been tested and working with most of Voip phone providers





i. Before beginning the steps below make sure whatever modem/router combo your ISP gave you is in bridge mode if you are using your own router. Call/contact your ISP if you have to.


1. Disable any and all port forwarding and/or DMZ in your router. Port forwarding creates security issues and can open the door to SIP scanners and hackers. If you're having trouble with SIP scanners and/or telemarketers, visit http://forums.redflagdeals.com/newegg-ca-obi200-39-99cad-obi202-59-99cad-4-99-shipping-boxing-week-1882793/#post24563087

2. If you used the Obitalk web portal (www.obitalk.com) to configure your ATA, keep in mind that you must continue using it to configure your ATA. Otherwise whatever settings you change will eventually be overwritten by what you previously entered at obitalk.com anyway. If you wish to disable this behaviour, dial ***1. Enter that IP address into a web browser. Navigate to System Management-->OBiTalk Provisioning-->select Disabled for the method. Save. Reboot ATA. Now obitalk.com won't overwrite whatever changes you make via the device's interface (via IP address).

Pick one method (obitalk.com) or the other (IP address of device) for changing device settings. But do not use both methods. Keep in mind that activating Google Voice requires using the Obitalk.com web portal.

(In Obitalk.com, you will need to enable and enter expert settings to do the following, if you want to use Obitalk.com.)

3. Ensure you're using 3.1.0 (Build: 5110): http://fw.obihai.com/OBi202-3-1-0-5110.fw
Yes, this firmware works on an OBi200/202.

Refer to manual firmware update instructions here: https://www.obitalk.com/forum/index.php?topic=9.0


4. In your Obihai ATA or at Obitalk.com, Navigate to Voice Services-->SP(FPL) Service-->X_UserAgentPort
Pick a random number between 30000 and 60000

(submit/save/reboot)

5. Navigate to Service Providers-->ITSP Profile (FPL)-->SIP

i) ensure X_DiscoverPublicAddress is enabled (it is by default)

ii) enable X_UsePublicAddressInVia (it's not by default)
You will need to uncheck default, device default, and Obitalk settings boxes. Then check the box to enable the feature

(submit/save/reboot ATA)

6. Retest
When I say Retest, retest always includes the following: A. Turn off both router and ATA. B. Turn on router. Wait for router to be fully up and transmitting data. C. Turn on ATA.

Then retest by calling your FPL phone number. If the problem is solved, don't continue.

7. If that doesn't work, you can also try enabling X_DetectALG (Navigate to Service Providers-->ITSP Profile (FPL)-->SIP)

(submit/save/reboot ATA)

8. Retest
When I say Retest, retest always includes the following: A. Turn off both router and ATA. B. Turn on router. Wait for router to be fully up and transmitting data. C. Turn on ATA.

Then retest by calling your FPL phone number. If the problem is solved, don't continue.

9. If that still doesn't work, disable X_DetectALG. And submit/save/reboot ATA.

10. If there are still problems, try disabling the SIP ALG feature in whatever router or modem/router combo it is that you're using:
http://www.obihai.com/faq/sip-alg/calling-out
I'm of the opinion Apple routers don't offer this feature, but you might as well check. If you manage to disable SIP ALG in the router, then retest. If you received a modem/router combo, from your ISP ask your ISP. It is typically better to stick the modem/router combo from your ISP in bridge mode and use an external router.

See here for an example on how to disable SIP ALG in a router: http://www.obihai.com/faq/sip-alg/disable-alg




Save settings.
Turn off both router and ATA. Turn on router. Wait for router to be fully up and transmitting data. Turn on ATA.
Then retest by calling your FPL phone number. If the problem is solved, don't continue.

11. Try Proxyserver voip4.freephoneline.ca:6060
visit http://forum.fongo.com/viewtopic.php?f=15&t=16196 (look at the .pdf)
(I'm of the opinion that step #7 makes this step redundant, but trying this is worth a shot anyway).
Retest. When I say Retest, retest always includes the following: A. Turn off both router and ATA. B. Turn on router. Wait for router to be fully up and transmitting data. C. Turn on ATA.

Then retest by calling your FPL phone number. If the problem is solved, don't continue.

voip4.freephoneline.ca:6060 is a SIP server whose purpose is to help those with SIP ALG issues (can't disable it in the user's router, for example).

So steps #7, #10, and #11 are all related. They are attempts to address a problem created by SIP ALG.


12. Try this at your own risk: use voip3.freephoneline.ca as the proxyserver
voip3.freephoneline.ca is intended for testing purposes only--or for those who receive explicit permission to use it. Using it for an extended period may get your account banned. However, if using voip3.freephoneline.ca does work, you should open up a ticket with support and let them know that you can't get two-way audio any other way: https://support.fongo.com/anonymous_requests/new
If no responds to your support ticket, provide the ticket number in a private message to Fongo Support: http://forum.fongo.com/ucp.php?i=pm&mode=compose&u=7852

FPL configures its SIP servers differently than many other VoIP providers.
voip3.freephoneline.ca conforms more to the norm. But using it without permission can get your account banned.
If you'd like to avoid getting your account banned, use Proxyserver voip.freephoneline.ca, voip2.freephoneline.ca, or voip4.freephoneline.ca:6060 instead and skip to step #14.

13. Retest. When I say Retest, retest always includes the following: A. Turn off both router and ATA. B. Turn on router. Wait for router to be fully up and transmitting data. C. Turn on ATA.

Then retest by calling your FPL phone number.

14. If none of that helps, then, unfortunately, you're pretty much stuck with port forwarding your RTP (UDP) port range 16660-16798 from your router to your ATA. For reference, that range can be found under ITSP Profile (FPL)-->RTP. Then look at LocalPortMin and LocalPortMax. RTP packets need to reach your ATA in order for you get incoming audio. Quite often, when the one way audio issue occurs, this is the problem. RTP packets are not reaching your ATA. Ideally, one should not have to port forward in order to achieve proper two-way audio, since port forwarding does create security issues. Port forwarding should only be done when everything else fails.

Refer to the port forwarding section of your router manual to learn how to port forward to your ATA. If a router was given to you by your ISP, call your ISP.

15. Retest. When I say Retest, retest always includes the following: A. Turn off both router and ATA. B. Turn on router. Wait for router to be fully up and transmitting data. C. Turn on ATA.


Then retest by calling your FPL phone number.

16. If all else fails, try posting at http://forum.fongo.com/viewtopic.php?f=8&t=15120&start=300 and/or open a support ticket at https://support.fongo.com/anonymous_requests/new
If no responds to your support ticket, provide the ticket number in a private message to Fongo Support: http://forum.fongo.com/ucp.php?i=pm&mode=compose&u=7852

When I say Retest, retest always includes the following: A. Turn off both router and ATA. B. Turn on router. Wait for router to be fully up and transmitting data. C. Turn on ATA.

[AngryOldman]

Hey All,
Thanks again for all your help. After much messing about, the problem was the r7000. Installed Vortex, all good now.
Cheers,
A. Oldman