It could fail for maximum 10 minutes if there was no network for a while. Make sure you do not use keep alive on the server or zoiper could get killed. A firewall is blocking the incoming connections.Zoiper will send a register to the server to let the server know w If you are experiencing this, please reduce the re-registration time (registration expiry) to a lower value to minimize the time you could be without incoming calls when such an event happens. This situation will correct itself when the re-registration time is due. Please note that if your public ip address changes but you are using an internal ip address behind a NAT, then zoiper will not be notified about a network change and will not re-register automatically. If that does not work and you can only use UDP, please ensure sip keep alive is enabled and is set to 30s. Go to settings -> accounts -> your SIP account -> advanced -> Network related. Keep in mind that an excessive reason of re-registrations might lead to temporary blocking by your voip provider, in this case you can try using the sip keep alive option in Zoiper instead. (Keep in mind that this will have a significant impact on battery life when using cellular 3g/4g, the impact on WiFi is not as signficant). If your voip provider or PBX does not support TCP, try lowering the re-registration time in zoiper to 30 or 1 minute. Try switching to TCP or TLS instead of UDP (if your provider or PBX supports it). When using TCP most routers will keep the connection for many hours (unless they run out of memory and start recycling port mappings). This means zoiper would have to re-register every minute to keep the mapping alive. When using UDP, most routers will drop the port mapping after a few minutes. The most likely culprit here is the short NAT port mapping on your home or office router.
Macbook internet only works for a few seconds registration#
You can verifiy if this is the case if Zoiper receives incoming calls immediately after a registration to the server, but after a few minutes incoming calls stop working. The only thing to be done is to implement Push on your/VoIP provider's server. This means if you started any application after opening zoiper, then the incoming calls will no longer work. To enable it, go to Zoiper -> Settings -> Incoming callsĪs Microsoft does not allow applications to run in background, Zoiper will not be able to run in background, only under the lock screen. If you cannot use TCP or TLS because your provider or PBX does not support it, you can still try use UDP although it often causes side effects such as increased battery usage and sometimes problems with audio on other applications. The default registration expiry values are: Zoiper will keep retrying approximately every 10 minutes and if there is network it will re-register. (This will cause the TCP voip socket to get closed and iOS will force Zoiper to hibernate). Keep in mind that due to iOS limitations, it is possible for incoming calls not to work when your internet connectivity stops (out of reach for WiFi and cellular at the same time) and this continues for over 30 seconds. If you cannot, your provider does not support TCP or TLS and this setting will not work. You can do so in Zoiper -> Settings -> Accounts -> (Your account) -> Network SettingsĬhange the transport to be TCP or TLS.Try if you can still register. (When "Qualify" is enabled in Asterisk servers, the default timeout will be 2 seconds) Note, when using TCP if the server sends too much wake-up packets (more than 15 for 300 seconds), iOS will kill the application. Then try to use TCP or TLS for your SIP account. Scroll down to the "Use Cellular Data For" and make sure the option is enabled for Zoiper. To do so, to to the ios settings -> Cellular First make sure that Zoiper is allowed to use the cellular network.