Registration issue
From VoIP.ms Wiki
Sometimes is possible to have issues when trying to register our device or softphone with our VoIP provider, we will review some recommendations and important things to check, to start trouble shooting with this situation.
Contents |
Reboot your device.
Most common issues related with registration failing, can get solved just by rebboting the device or softphone, another good suggestion is to reboot the router or modem to see if this help to solve the issue.
ATA/Softphone.
- Verify if your device has any field to set the "Register expires", if you find something like this, you usually will see a default of 3600 (seconds), lower this value to 120.
- Use the IP address from the server instead of the domain name, example: Use 67.215.241.250 instead of losangeles.voip.ms.
- If your device has any options similar to "Nat keep alive" or "Nat mapping" please enable them. This will make the connection not go idle
- Check if you have the latest firmware updated on the device, some minor bugs get resolved with the new firmwares, so it is important to have them up to date.
Cant connect to login server.
This error is usually caused by the router that somehow is blocking the registration attempts, try rebooting the router then the ATA device, if that does not work, re-enter the password and userID on the device settings, or try using the IP address of the server instead of the hostname. If you do not have the IP address send a ping to the server or contact the VoIP.ms staff.
Tomato firmware (PAP2TNA).
Some of the default settings with Linksys devices conflict with the default Tomato timeout settings. These are the UDP Timeout settings and if they are left at their defaults, VoIP devices will sometimes fail to register after an IP change. These may be found on the Conntrack/Netfilter page in the Tomato config. Set "unreplied timeout" to 10 seconds.
Asterisk/PBX system.
- Add to your trunk nat=yes and qualify=yes, these 2 values can help with your registration issues.
- Use the IP address from the server instead of the domain name, example: Use 67.215.241.250 instead of losangeles.voip.ms.
Nat=yes
The NAT option determines the type of setting for users trying to connect to an asterisk server. With VoIP.ms is recommend to have the NAT option set on Yes, which is the option that will work better.
Portal settings influencing NAT with Asterisk:
- yes = Always ignore info and assume NAT
- no = Use NAT mode only according to RFC3581 (;rport)
- never = Never attempt NAT mode or RFC3581 support
- route = Assume NAT, don't send rport (work around more UNIDEN bugs)
Qualify=yes
This feature may also be used to keep a UDP session open to a device that is located behind a network address translator (NAT). By sending the OPTIONS request, the UDP port binding in the NAT (on the outside address of the NAT/firewall device) is maintained by sending traffic through it. If the binding were to expire, there would be no way for Asterisk to initiate a call to the SIP device. This can be used in conjunction with the nat=yes setting.
Note that it is the qualify=xxx(in miliseconds) or qualify=yes or qualify=no in sip.conf file that determines the registration with the server. If you have "yes" for qualify it will check the registration with the server every 2 seconds.
