Betamax webcalldirect - Work in Progress???
Checked WebCallDirect current settings instructions as we also cannot make calls via eu.voxalot.com. Their recommendation is for independent devices to connect via sip.webcalldirect.net and stun.webcalldirect.net. However I have a two separate units working while connected directly via sip.webcalldirect.com. Whilst the .net address resolves to IP 80.92.66.130, the stun and sip entries resolve to private IP 192.168.255.4 - strange!!
Otherwise:
webcalldirect.com IP 194.120.0.250
sip.webcalldirect.com IP 194.120.0.198 changed from 193
stun.webcalldirect.com IP 194.221.62.209 unchanged
Not sure that I understand what is going on/happening any more than all the other wise gurus already on the case. However is the above evidence of unfinished betamax change work in progress?
So, sadly, for the moment we cannot route via voxalot, until the problem is resolved. Is there an explanation for the above oddity?
|