News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Obi110 can call out, but the phone doesn't ring.

Started by buhuo, October 18, 2011, 11:35:30 PM

Previous topic - Next topic

Stewart

If you have a modem/router with an incompatible SIP ALG that can't be disabled, you can often work around the problem by setting X_UserAgentPort to a non-standard value (e.g. 5070 and 5071 instead of 5060 and 5061), and/or connecting to a non-standard port at the provider (if implemented on their server).

In some cases, forwarding the SIP local UDP ports (whatever values are used for X_UserAgentPort) is required, possibly in addition to the above.  There should be no problem forwarding two ports, if you have two providers on the OBi, or forwarding many ports (two for each OBi), if you have several OBi devices.

Occasionally, none of the above will help.  In such cases, it's usually possible to set the modem/router to be a simple bridge and use it with an external router.  In very rare situations, that won't work, either, but it would usually be possible to use a commodity modem in place of the one supplied by the ISP.

onecanobi

Quote from: RonR on November 02, 2011, 02:00:46 PM
Quote from: onecanobi on November 02, 2011, 01:48:03 PM
My issue is with a TPLink WR340G router -- and the fact that I'd eventually like to have more than one SIP provider. Doing permanent port forwards ruin that option.

Why does doing permanent port forwards prevent you from having more than one SIP provider?


because most providers expect publicip:5060 to be forwarded to sip device, and i plan on having more than one physical device.

onecanobi

Quote from: Stewart on November 02, 2011, 02:34:11 PM
If you have a modem/router with an incompatible SIP ALG that can't be disabled, you can often work around the problem by setting X_UserAgentPort to a non-standard value (e.g. 5070 and 5071 instead of 5060 and 5061), and/or connecting to a non-standard port at the provider (if implemented on their server).

In some cases, forwarding the SIP local UDP ports (whatever values are used for X_UserAgentPort) is required, possibly in addition to the above.  There should be no problem forwarding two ports, if you have two providers on the OBi, or forwarding many ports (two for each OBi), if you have several OBi devices.

Occasionally, none of the above will help.  In such cases, it's usually possible to set the modem/router to be a simple bridge and use it with an external router.  In very rare situations, that won't work, either, but it would usually be possible to use a commodity modem in place of the one supplied by the ISP.


Thank you for this, I will try this out and report back.

RonR

Quote from: onecanobi on November 02, 2011, 04:36:57 PM
because most providers expect publicip:5060 to be forwarded to sip device, and i plan on having more than one physical device.

Most providers support an array of SIP ports (5060, 5061, 5062, 5063, etc.).  I currently use an OBi and PAP2 on the same LAN with ports 5060/5061 forwarded to the OBi and 5062/5063 forwarded to the PAP2.

Stewart

Quote from: onecanobi on November 02, 2011, 04:36:57 PM
... because most providers expect publicip:5060 to be forwarded to sip device, and i plan on having more than one physical device.
IMO, that is not true.  All SIP UDP packets have both a source and a destination port number.  Can you name even one provider that requires port 5060 (or any specific port) on the user's end?  I know that one can use any local port with all I have tried, including Callcentric, Anveo, VoIP.ms, Localphone, Phonepower, VOIPo, sipgate, Future-Nine, Vitelity, Voxbeam, VoxOx, and ippi.

In contrast, many providers accept registrations on server port 5060 only.  Because that port is often blocked or specially (and incorrectly) treated, it's common for servers to also support at least one non-standard port.  The specific values are provider dependent but do not relate to port forwarding.

As RonR pointed out, you can have e.g. device #1 with local ports A and B, and device #2 with local ports C and D.  You forward ports A and B to the private IP address of device #1; ports C and D to device #2.  This should work for any values of A, B, C, and D that are not in conflict with other devices or functions on your network.

onecanobi

Quote from: Stewart on November 02, 2011, 05:11:18 PM
Quote from: onecanobi on November 02, 2011, 04:36:57 PM
... because most providers expect publicip:5060 to be forwarded to sip device, and i plan on having more than one physical device.
IMO, that is not true.  All SIP UDP packets have both a source and a destination port number.  Can you name even one provider that requires port 5060 (or any specific port) on the user's end?  I know that one can use any local port with all I have tried, including Callcentric, Anveo, VoIP.ms, Localphone, Phonepower, VOIPo, sipgate, Future-Nine, Vitelity, Voxbeam, VoxOx, and ippi.

In contrast, many providers accept registrations on server port 5060 only.  Because that port is often blocked or specially (and incorrectly) treated, it's common for servers to also support at least one non-standard port.  The specific values are provider dependent but do not relate to port forwarding.

As RonR pointed out, you can have e.g. device #1 with local ports A and B, and device #2 with local ports C and D.  You forward ports A and B to the private IP address of device #1; ports C and D to device #2.  This should work for any values of A, B, C, and D that are not in conflict with other devices or functions on your network.

The issue rises when you have older ATA hardware that isn't as flexible to co-exist with the OBI. :)
When I tried this method with a PAP2 and a Cisco 7940 in the past, it didnt work too well.

Anyway, thanks to your help above, i ended up doing a few things:


1) enable STUNEnable and set STUNServer to stun.softjoys.com port 3478
2) enable X_SymmetricRTPEnable [ seemed like a good thing to enable, not sure if it did anything ]
3) login to FreePhoneLine's webpage, and change a) Voicemail settings to ring 5 times prior to going to VM [ from a setting of 1 ] and b) ensure Follow Me Settings are disabled.
4) add X_UserAgentPort for port 6060 on the Obi for SP2
5) add a virtual server for port 6060 udp/tcp on the tplink router mapping to the OBI's internal IP.

After all of this, I am now able to receive incoming calls.
Without 4 and 5 completed, I would get a busy tone when dialing the number, and no ringing would happen.

I will in the very near future switch the cisco deskphone on to the same internal network and see if it can co-exist with a second FPL line and a different port forward.

buhuo

Quote from: onecanobi on November 02, 2011, 07:59:21 PM
Quote from: Stewart on November 02, 2011, 05:11:18 PM
Quote from: onecanobi on November 02, 2011, 04:36:57 PM
... because most providers expect publicip:5060 to be forwarded to sip device, and i plan on having more than one physical device.
IMO, that is not true.  All SIP UDP packets have both a source and a destination port number.  Can you name even one provider that requires port 5060 (or any specific port) on the user's end?  I know that one can use any local port with all I have tried, including Callcentric, Anveo, VoIP.ms, Localphone, Phonepower, VOIPo, sipgate, Future-Nine, Vitelity, Voxbeam, VoxOx, and ippi.

In contrast, many providers accept registrations on server port 5060 only.  Because that port is often blocked or specially (and incorrectly) treated, it's common for servers to also support at least one non-standard port.  The specific values are provider dependent but do not relate to port forwarding.

As RonR pointed out, you can have e.g. device #1 with local ports A and B, and device #2 with local ports C and D.  You forward ports A and B to the private IP address of device #1; ports C and D to device #2.  This should work for any values of A, B, C, and D that are not in conflict with other devices or functions on your network.

The issue rises when you have older ATA hardware that isn't as flexible to co-exist with the OBI. :)
When I tried this method with a PAP2 and a Cisco 7940 in the past, it didnt work too well.

Anyway, thanks to your help above, i ended up doing a few things:


1) enable STUNEnable and set STUNServer to stun.softjoys.com port 3478
2) enable X_SymmetricRTPEnable [ seemed like a good thing to enable, not sure if it did anything ]
3) login to FreePhoneLine's webpage, and change a) Voicemail settings to ring 5 times prior to going to VM [ from a setting of 1 ] and b) ensure Follow Me Settings are disabled.
4) add X_UserAgentPort for port 6060 on the Obi for SP2
5) add a virtual server for port 6060 udp/tcp on the tplink router mapping to the OBI's internal IP.

After all of this, I am now able to receive incoming calls.
Without 4 and 5 completed, I would get a busy tone when dialing the number, and no ringing would happen.

I will in the very near future switch the cisco deskphone on to the same internal network and see if it can co-exist with a second FPL line and a different port forward.

My router is Dlink DVA-G3810BN/TL. I have been following this instruction, but it doesn't work now.

onecanobi

were you able to setup the virtual server, or port forward?
you could try maybe 5061 or 6061 instead of 6060 that I tried.

but I think the key is the 5 rings prior to vm setting in FPL's configuration page, along with proper port forwarding/mapping.

is your obitalk on dhcp or static ip?

Veronica

SAME PROBLEM HERE  :(
Hello yesterday i purchased a configuration file and today i have been trying all day to set it up in my OBIHAI 110 ATA, i have already read freephoneline forums as well as OBITALK forums but i cant make it ring when someone calls.

Router: linksys wireless-N home router WRT120N (No SIP ALG i have looked so many times and havent found it)
ATA: ObiHai 110 with firmware up to date

I have test the outbound call and it works fine, quality is good too only problem is the inbound calls ringing that doesn't ring at all. PLEASE HELP!

RonR

Quote from: Veronica on December 16, 2011, 06:01:09 PM
Router: linksys wireless-N home router WRT120N

Veronica,

Try temporarily connecting the OBi directly to your modem, eliminating the WRT120N.  Power-cycle the modem and the OBi after making the connection.  It's important to determine if your router is part of the problem and the best way to do that is to take it out of the picture.

Veronica

Quote from: RonR on December 16, 2011, 06:06:42 PM
Quote from: Veronica on December 16, 2011, 06:01:09 PM
Router: linksys wireless-N home router WRT120N

Veronica,

Try temporarily connecting the OBi directly to your modem, eliminating the WRT120N.  Power-cycle the modem and the OBi after making the connection.  It's important to determine if your router is part of the problem and the best way to do that is to take it out of the picture.


thank you for reply, i will try that but what you mean with Power-cycle? could you explain?. thanks

RonR

Disconnect and reconnect the power from both the modem and the OBi after making the direct connection.

Veronica

thank you will try that then and report back , but can you help me with something else how do i disable provisioning on device?

RonR

Log into the OBi at the IP address returned by dialing ***1 and set:

System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled

The default username/password is admin/admin.

Veronica

Quote from: RonR on December 16, 2011, 06:18:53 PM
Disconnect and reconnect the power from both the modem and the OBi after making the direct connection.

OK so i connected the obi to the modem directly, then while both connected i disconnected the router and the obi from power waited few minutes and made a test my boyfriend called to my frephoneline number and it RANG! yeiii BUT then i connected the router back to the modem and the obi to the router waited few minutes, made a test DID NOT RING! :'(, im frustated now what else can i do? PLEASE HELP!

RonR

Make a port forwarding entry in your router, forwarding ports 5060-5061 to the IP address of the OBi.

Veronica

Quote from: RonR on December 16, 2011, 10:47:22 PM
Make a port forwarding entry in your router, forwarding ports 5060-5061 to the IP address of the OBi.

i did that i even changed X_UserAgentPort for port 5070 , in freephoneline i have voicemail to wait 5 rings to get in and follow me is disaled aswell. im going to try with port 6060 as a user said and report back.

Also i have port fordward the RTP ports to OBI.

RonR

My suggestion to forward ports 5060-5061 would only possibly help if you haven't changed the OBi or Freephoneline from the default of 5060.

Veronica

Quote from: RonR on December 16, 2011, 11:02:07 PM
My suggestion to forward ports 5060-5061 would only possibly help if you haven't changed the OBi or Freephoneline from the default of 5060.

i havent change the default 5060 just changed the X_UserAgentPort to 5070 which didnt work too

Veronica

alright i changed X_UserAgentPort to 6060 i made a port forwarding to 6060 aswell (apart of the port 5060 that i port forwarded too), made test and did not ring, so went back went to Aplications & Games>>QoS and enabled priority to ports: 5060 to 5061 and 6060 to 6061 in Medium(recommended) priority, then just like that decided to clean my temp files, cache and more in my computer with Ccleaner made a test again and VOILA IT RANG :o just to be sure i made another test and it rang again ;D ;D ;D so problem solved for now, i'll play with the codects tomorrow tho what you would recommend to stay in G729 as first priority or change to G711U in Canada.
Thanks for the support i will report back if i have any problems thanks @RonR.