Quote:
Originally Posted by boatman
Today I tested the five proxies for Contact Address. Here are the results.
proxy01.us1.voxalot.com - ok
proxy02.us1.voxalot.com - User's public IP address given for RTP connection.
proxy01.eu1.voxalot.com - ok
proxy02.eu1.voxalot.com - ok
proxy01.au1.voxalot.com - ok
Some of you may think you are behind symmetric NAT but in fact are not, maybe you just never correctly set your ATA's NAT settings. If you are not really behind symmetric NAT then you can avoid this problem by correcting the NAT settings in your ATA or SIP phone. If you really are behind symmetric NAT try this workaround:
Instead of us.voxalot.com use proxy01.us1.voxalot.com (when you do this set 'Use DNS SRV:' = no).
----------
About the FUP problem; only one or two of the five proxies are affected.
Instead of eu.voxalot.com use proxy01.eu1.voxalot.com (when you do this set 'Use DNS SRV:' = no).
I am not sure if one or both of the US proxies are on Betamax's whitelist. In case of FUP problem with US proxy don't use us.voxalot.com, instead try both proxy01.us1.voxalot.com and proxy02.us1.voxalot.com.
|
Martin,
Have you had the chance to restart the servers?
The problem is still happening, driving my and my called parties quite confused.
Can you confirm whether "proxy01.us1.voxalot.com" will not change in the future and this workaround can be used?
Thanks,
The Doc