I don’t use this often but when I set it up I added two accounts, one for local and one for remote. The port would be the same in both cases probably 4569 unless you changed it but you need to port forward that port in your router to your Allstar computer to allow incoming from the internet. If you have a dynamic IP address to your provider and it changes often you need to setup a domain name using dyndns or etc. Outside of your local lan on the internet you need to use the public IP address or domain name of your router. That would be the .x address or whatever adressing you have setup on your local lan. Quick reply and I am not sure if this is your problem but you need to use the local lan IP address when using your own wifi. You may have better luck with an IAX client. It will be a very painful and futile experience. So unless you have control of your work firewall (or a vpn to your home network from your phone) don’t even try. Even if you manage to get your IP correctly registered the RPT (UDP protocol that carries the voice packets) will still be broken. SIP is a great protocol until you get a NAT firewall in the middle. SIP and NAT without proxy or a NAT aware app is a no starter. Very confused, if anyone can help I would appreciate it. I also took it a step further and installed zoiper on my laptop and connected to the same WiFi and my laptop connects and shows the IP address of my actually cable modem. Also from my phone I show a time out and a 408 error for time out. When I connect using WiFi I’m connecting but when it tries to poke me its using an IP that’s private and behind me firewall. It looks like when I register on LTE it shows my actual IP address and then pokes me and deems me “reachable”. NOTICE: chan_sip.c:16258 sip_poke_noanswer: Peer ‘7252’ is now UNREACHABLE! Last qualify: 0 NOTICE: chan_sip.c:12758 handle_response_peerpoke: Peer ‘7252’ is now Reachable. Registered SIP '7252' at 70.XXX.X.XX port 4446 expires 60 I watched the CLI and I think I see the problem, but don’t quite understand how to fix it and maybe someone can help. At work on the WiFi I can not register, but if I turn off WiFi the SIP account will register on LTE. Those glitches are more common when I'm travelling and staying in countries with weak internet infrastructure, than they are when I'm at home.I can register my SIP zoiper account from my home wifi and LTE. This registration lockout problem only seems to arise when network glitches occur deeper down the line towards my sip server, ofr even in the sip server itself. Zoiper copes and recovers registration OK with local loss of wifi and/or local loss of mobile signal. Zoiper fixes itself, but that doesn't work, at least not after quite a long wait anyhow. I've tried simply waiting and doing nothing for quite a while to see if Force stop Zoiper in Settings -> Applications. Registration turn green, and then go back to my local wifiĢ. Stop my local wifi and temporarily go over to mobile internet, see I've found 3 possible ways of restoring my registration:ġ. In that event I find there's no indication of any incoming call from that voicemail's number on Zoiper. Indicating that someone has left me an incoming voicemail when I thought Zoiper should have had me registered on-line. I can't usually tell how long it's been in that failed state unless I've received an email Registration fail notification when I open it. The problem I have is that when Zoiper has been running in theīackground and I haven't opened it for a while, maybe a couple of daysįor example, it's quite common for me to discover it displaying a red Would be, or explain what exactly it is that initiates an automatic fix operation? Zoiper will fix itself automatically after a while, the issue is because android does not notify us at the proper time when the network is upĬan you be a little more specific about how long that "after a while" Retrying to recover from any registration fail. Zoiper needs a mod so it automatically keeps To 3G mobile for a minute and then go back to wifi. Restarted for it to recover, or I have to temporarily stop wifi and go Mode, but what is not expected is that when the network recovers, Zoiper remains locked out in registration fail. *Registration fail issue * As expected, network glitches between ZoiperĪnd my host sip server cause my Zoiper to go into registration fail
0 Comments
Leave a Reply. |