Obi110 can call out, but the phone doesn't ring.
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page