Voxalot not responding to OPTIONS
Asterisk as other SIP UAs is using OPTIONS as a keep alive and/or link monitoring tool.
Just noticed that 2 Voxalot servers are replying 200 OK for some time and after a few minutes - no reply :( Code:
Retransmitting #4 (no NAT) to 85.17.19.194:5060: |
Is your Asterisk behind a NAT router? Can you change the time interval between OPTIONS? I suspect Voxalot proxy thinks you are sending SIP packets too often, then cuts you off. I know the Gizmo5 proxy will do that, not sure about Voxalot. Maybe stop using OPTIONS, instead register every 299 seconds, or 1 second less than your router's NAT expiration time.
|
Quote:
My router's NAT expiration time is 180 sec which is quite typical value. Setting qualifyfreq=170 (seconds) does not help as well (default is 60 sec). Thanks! |
:confused:
Any chance that somebody from Voxalot team will react? I don't think I'm the only person who have this problem Voxalot due to this situation with the quite common NAT keepalive method. There is no need in receiving a reply in order to have NAT pinhole open, so it is still possible to receive incoming calls from Voxalot. But it is not possible to use the same trunk in Asterisk for placing calls to Voxalot, because Asterisk will mark Voxalot server unreachable. |
Green, is this problem new....as in it started in the last little while...or have you had it before...
I am worndering if the issue is just the new EU proxy? |
Quote:
Quote:
proxy02.eu1.voxalot.com proxy01.eu1.voxalot.com I had 2 registrations to Voxalot and probably one of the peers took the failover way. As a result I've got 2 addresses in my log. |
If other methods (to maintain an open NAT route) don't succeed, you might try registering every 179 seconds. Even though the proxy will record the registration for 600 seconds and return "expires=600", it will accept another registration before the first has expired. A better solution would be to forward some ports in the router, but of course this is not always possible.
Maybe someday there will be a real NAT-keep-alive module written for Asterisk. A proper NAT-keep-alive module would allow a choice of time interval, and allow sending of empty packets which are better for NAT-keep-alive because they don't add load to the proxy by causing it to respond. |
Quote:
Quote:
So for me the logical choice will be switch from voxalot to more predictable service. I already replaced all my voxalot URIs I used with e164.org, also changed my DID forwardings to another URI. Very disappointed. |
Hi green,
Voxalot does not have any limitations or restrictions on the number and / or frequency of OPTIONS messages. As suggested by others in this thread, I suspect the reason you are not seeing the replies after a few minutes is due to the OPTIONS message requests load balancing between EU1 and EU2 and after a short period of time, your router is closing down the keep alives. One suggestion is to reconfigure your setup to point directly to one of the EU proxies i.e. proxy01.eu1.voxalot.com or proxy02.eu1.voxalot.com instead of eu.voxalot.com Let us know if this helps? |
Quote:
|
All times are GMT. The time now is 03:40 PM. |
Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.