- #Zoiper android login failed update#
- #Zoiper android login failed registration#
- #Zoiper android login failed windows#
GS Wave doesn't, in LAN or with Outbound Proxy (though it works with Sipgate ITSP) Yes, as I've said before, Zoiper with Outbound Proxy works.
So an INVITE can reach to 200.168.45.78 now? Now that we discarded GS Wave and with Zoiper we turned on Outbound Proxy, the internal IP addresses don't show up to top And paste "Contact URI (Source IP Address)" field here.
#Zoiper android login failed registration#
Let you find the 900890002's registration record at SIP Server's "Registered Clients" page. I've handled VPNs in a different way, I'm using a very efficient SD-WAN solution. Something is different, just don't know exactly what. Just added a specific rule to handle these tests. Yet BSS recognized NAT: in the REGISTER packets it correctly differentiates when the Zoiper phone is registering through VPN (no NAT) or through 4G (NAT on)ĭial Plan is the same. I used to be able to make calls between UAs on open internet without Outbound Proxy set. Still, now all configurations require Outbound Proxy set to ON: the WiFi (NATted) configuration but also the open 4G internet configuration require it. Could be an interoperability issue?ī) Zoiper is back to work. A Zoiper phone in the same Android phone works without problems. I can make calls to NATted Snom phones and to Zoiper android phones on 4G and WiFi, but it doesn't receive any calls when connected to BSS.
#Zoiper android login failed windows#
Also Windows was updated.Ī) GS Wave has real problems.
#Zoiper android login failed update#
I'm not 100% sure that the software update broke it or if something just changed. If you request a official technical support from our team, please contact to open a support ticket.ĭo you have any settings at "External IP address pattern" or/and "Internal IP address pattern" in Configuration>System page? This is a user community forum not for official technical support. so you must tune the DialPlan to specify the destination. > Wireshark shows the target packets being sent to the private IP (192.168.15.19), not the public IP (200.168.45.78 )Īre you sure that 900890002's REGISTER request was sent from 200.168.45.78? Last edited by Truong on Thu 11:37 pm edited 1 time in totalĭid the issue start happening after you upgraded the SIP Server?Īre you using the same configuration/DialPlan as the before the upgrade? Im sorry if it make bother to you and thank you so much! Now i have problem with connection from smartphone to Voip Brekeke SIP. I post a subject to forum but not received support. Im sorry for this post not relate to your post.īut it very difficult for newbie same me. So it seems to be an issue with Far End NAT traversal. They can be on open internet or behind a WiFi router: in any case they can call the phones in the VPN, but the can't be called UNLESS they are in the same LAN, in which case 2 of them can talk to each other. The Grandstream phones are GS Wave Android softphones. I've done a upgrade/reinstall of the software (saving webapps directory) to correct the Apache vulnerabilityĪny idea what could be wrong? New BSS version issue? To = from NATted devices to devices in the VPN are working. Wireshark shows the target packets being sent to the private IP (192.168.15.19), not the public IP (200.168.45.78 ) Now I'm not able anymore to call the UAs behind NAT from my UA in the VPN. RTP exchanger > RTP relay is set to "Auto" NAT traversal > Keep address/port mapping is set to "On" I used not to have problems with phones behind NAT. UA (phone), gateway or other hardware/software involved: Posted: Thu 11:26 am Post subject: NATted calls not working anymoreīrekeke SIP Server, Version 3.9.5.8, StandardĤ. NATted calls not working anymore Goto page 1, 2 Next Brekeke Forum Index » Brekeke SIP Server Forum
0 kommentar(er)
