if they are enabled try disabling them and vice-versa. You may need to disable or enable STUN and rport in different combinations according to their current state e.g. If you do not know how to configure your routing device / firewall, please ask for assistance your network provider / system administrator.Īltering STUN and rport / rport media options in different combinations could also help.
You should also make sure that ports used by Zoiper are not being blocked or filtered by your firewall / router and are properly forwarded: You need to first disable SIP ALG under your router configuration, if you do not know how to do it, you will need to contact your Network service provider / administrator for assistance. If you need additional, more technical information you can find it on the link below at the "SIP ALG problems" section:
This in most cases is because some routing devices / firewalls have built-in "SIP ALG"(Application-level gateway) functionality which is implemented to resolve NAT(Network Address Translation) issues, however the implementations are wrong and break SIP. For example when you receive a call, Zoiper should reply with an acknowledgement which probably never reached the server for some reason (or the ACK from the other side never reached Zoiper). This issue appears mostly because the session was not actually established and is in most cases network(NAT) related.
0 kommentar(er)
