Incoming Calls Problem

[risktaker91]

Hi there,

I recently set up freephoneline with the Obi100 that I bought. My number ported through today. I also changed the SIP settings with the unlock key credentials I was mailed (username, password, server). I can make calls and it seems to be working fine, but sometimes I just stop receiving incoming calls. When I call the number it says "the person you are trying to reach is unavailable, please leave a message". This is kind of frustrating because people keep trying to call and are not sure what's wrong. We can still send calls, but the incoming calls seems to be the issue. I'm not sure if I need to change some settings around, but I was hoping someone could help me out here.

Thanks!

[bridonca]

It looks like the default incoming RTP port for the Obi device is 10000. If that is so, allow the router to forward port 10000 to the Obi device. Save settings, power down the router, modem and ATA, and see what happens.

[Fongo Support]

Hi there,

I recently set up freephoneline with the Obi100 that I bought. My number ported through today. I also changed the SIP settings with the unlock key credentials I was mailed (username, password, server). I can make calls and it seems to be working fine, but sometimes I just stop receiving incoming calls. When I call the number it says "the person you are trying to reach is unavailable, please leave a message". This is kind of frustrating because people keep trying to call and are not sure what's wrong. We can still send calls, but the incoming calls seems to be the issue. I'm not sure if I need to change some settings around, but I was hoping someone could help me out here.

Thanks!

Hi there,

In addition with what Bridonca suggested, please try this as well:

http://forum.fongo.com/viewtopic.php?f=8&t=15968#p63486

Let us know.

Thanks,

[risktaker91]

I have port forwarded for 10000 like you suggested. I also changed those settings for "keepalive". And I still can't receive incoming calls. Any other solutions?

[Fongo Support]

I have port forwarded for 10000 like you suggested. I also changed those settings for "keepalive". And I still can't receive incoming calls. Any other solutions?

Hi there,

If all your incoming calls are going straight to VM, you may need to check your Follow me settings and also it might be a possibility that DND (do not disturb) or CFW all (call forward all) are enabled on your ATA.

Please dial *73 and hang up to disable CFW and *79 and hang up to disable DND. reference from below:

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

Let me know.

Thanks,

[risktaker91]

Hey,

I did both of those things. After I restarted my modem, router and ATA everything was working for a couple hours. But now it's back to not receiving incoming calls.

[bridonca]

I can think of 2 problems. The modem and the router. What do you have for a modem? If you can get the modem in bridge mode to let the router do it's work, that would make think less complicated. You do not want 2 routers, trust me. Most router/modem combinations are pretty awful.

I see another big issue. The Linksys EA3500 has SIP ALG enabled by default. Disable it.

In any case, your router(s) are not allowing incoming port 10000 to get to the ATA after a period, so that port is not getting forwarded properly.

[Fongo Support]

I can think of 2 problems. The modem and the router. What do you have for a modem? If you can get the modem in bridge mode to let the router do it's work, that would make think less complicated. You do not want 2 routers, trust me. Most router/modem combinations are pretty awful.

I see another big issue. The Linksys EA3500 has SIP ALG enabled by default. Disable it.

In any case, your router(s) are not allowing incoming port 10000 to get to the ATA after a period, so that port is not getting forwarded properly.

+1

I just want to also suggest to ensure that keep alive is enabled on the Obi with an interval of 20 (Not 15)

.http://support.freephoneline.ca/entries ... redentials

I have seen Obi devices not getting calls after a while if keep alive is not enabled.

Thanks,

[risktaker91]

I have a Thomson broadband cable modem (purchased from Teksavvy). I don't think it's a 2 in 1 thing (had that before with Rogers). I also went into my router to see if SIP was enabled, but it was already unchecked. After another modem/router/ata reset, it's working again. But I didn't really change anything so I'm pretty sure it's temporary.

Here are some screenshots I took.

[risktaker91]

I took some more screenshots of my ATA so maybe you guys can verify my settings are correctly configured.

[bridonca]

Your Obi ATA appears to be configured to accept RTP ports 16600 to 16798. If that is the case, get your router to forward those ports to the ATA

[risktaker91]

Your Obi ATA appears to be configured to accept RTP ports 16600 to 16798. If that is the case, get your router to forward those ports to the ATA

I forwarded these ports, but the issue still persists. I feel like I have tried everything. Any other suggestions?

[Fongo Support]

Your Obi ATA appears to be configured to accept RTP ports 16600 to 16798. If that is the case, get your router to forward those ports to the ATA

I forwarded these ports, but the issue still persists. I feel like I have tried everything. Any other suggestions?

Hi there,

I have 2 suggestions:

1. try with a different ATA or with xlite client
2. work with the support engineer on the ticket.

Please try and let me know.

Thanks,

[risktaker91]

Can you explain what the xlite client is? Getting another ATA is not really a viable option since they are pretty expensive. I bought my Obi100 from Amazon for nearly $70. Also the ATA seems to be working fine, and the error seems to be within the networking. Every time I reset the ATA and router/modem, it works fine for a brief period. That's what makes this so perplexing and frustrating.

I have also been working with Fongo Support via a ticket through e-mail. A lot of what they suggested is the same as what you guys have suggested. I also did a factory reset on the Obi device and configured the settings again with no luck. It's been almost a week since I ported my number from Rogers to freephoneline, and I still have this problem. We have family abroad in Europe and so we rely pretty heavily on home phone. They have grown frustrated as well because they can't reach us.

I almost have no idea what to do but maybe go back to Rogers home phone. It's frustrating because I spent a lot of money on the Obi device and for the voip unlock key and number porting.

I really appreciate you guys trying to help me though and I know you guys are doing your best. I really hope we can keep trying to fix this though.

[Fongo Support]

Can you explain what the xlite client is? Getting another ATA is not really a viable option since they are pretty expensive. I bought my Obi100 from Amazon for nearly $70. Also the ATA seems to be working fine, and the error seems to be within the networking. Every time I reset the ATA and router/modem, it works fine for a brief period. That's what makes this so perplexing and frustrating.

I have also been working with Fongo Support via a ticket through e-mail. A lot of what they suggested is the same as what you guys have suggested. I also did a factory reset on the Obi device and configured the settings again with no luck. It's been almost a week since I ported my number from Rogers to freephoneline, and I still have this problem. We have family abroad in Europe and so we rely pretty heavily on home phone. They have grown frustrated as well because they can't reach us.

I almost have no idea what to do but maybe go back to Rogers home phone. It's frustrating because I spent a lot of money on the Obi device and for the voip unlock key and number porting.

I really appreciate you guys trying to help me though and I know you guys are doing your best. I really hope we can keep trying to fix this though.

Hi there,

Obi is a good device and it should work with no issues if it's configured properly.

Xlite is a soft phone and can be used for testing accounts.

In your case, I think that you are trying too many settings and you are getting too many "advices"

I think you should work either on this Forum via PM with either myself or Bridonca, either with the Engineer on the ticket.

Thanks,

[risktaker91]

I have pm'ed bridonca to hopefully get some more help.

[Fongo Support]

I have pm'ed bridonca to hopefully get some more help.

Hi there,

Sorry, I have not looked carefully at the screenshots you have provided earlier. The issue is related to your registration timers.

Under ITSP profile A, your registration is setup to 60 seconds and required FPL is 3600 seconds. As a result, your OBi is sending to many register requests and it will loose registration.

You need to edit that field(RegistrationPeriod) and change from 60 to 3600 and reboot device.

Once you made that change, power off OBI for 10 minutes and power back on after 10 minutes.

This has been explained in the Forums many times.

http://forum.fongo.com/viewtopic.php?f= ... c68#p50432

As long as your OBI is configured as per FPL gudelines, it should be no issue.

To review the FPL guidelines:

http://support.freephoneline.ca/entries ... redentials

Thanks,

[risktaker91]

I have pm'ed bridonca to hopefully get some more help.

Hi there,

Sorry, I have not looked carefully at the screenshots you have provided earlier. The issue is related to your registration timers.

Under ITSP profile A, your registration is setup to 60 seconds and required FPL is 3600 seconds. As a result, your OBi is sending to many register requests and it will loose registration.

You need to edit that field(RegistrationPeriod) and change from 60 to 3600 and reboot device.

Once you made that change, power off OBI for 10 minutes and power back on after 10 minutes.

This has been explained in the Forums many times.

http://forum.fongo.com/viewtopic.php?f= ... c68#p50432

As long as your OBI is configured as per FPL gudelines, it should be no issue.

To review the FPL guidelines:

http://support.freephoneline.ca/entries ... redentials

Thanks,

Sorry for the late response, but I did this change around 1 pm today. It's midnight right now, and it's still working! I think that fixed it and I'm so happy! Thank you guys for all your help, really appreciate it. I'm gonna see if it's still working tomorrow morning before I fully celebrate, but it's looking good. I'll post again in the morning to let you guys know.

Thanks again. For a free service, I didn't expect to get this much tech support, but you guys have been awesome.

[risktaker91]

Everything's working great guys. Thanks again for the support.