BYOD Users: Testing Michigan Datacenter

[racerdude]

I believe that post you linked to is outdated, Voipo does proxy audio now on all calls. In the case of sip7 the audio proxy shows as 72.52.231.45 (Liquidweb Michigan) and in the case of sip and sip-central01 it shows 67.228.190.147 (Softlayer Dallas). So this does have an effect in the call quality, at least for me.

[tritch]

I believe that post you linked to is outdated, Voipo does proxy audio now on all calls. In the case of sip7 the audio proxy shows as 72.52.231.45 (Liquidweb Michigan) and in the case of sip and sip-central01 it shows 67.228.190.147 (Softlayer Dallas). So this does have an effect in the call quality, at least for me.

Thanks, I stand corrected. I wasn't aware they made changes and proxy the audio now....good to know.

I suppose they made the change to mitigate firewall issues at the customer's router. In the past, they suggested forwarding a wide range of ports on the router to prevent blocked, one-way audio issues due to the audio coming from a different IP (terminating carrier) than the SIP server...

[GreenLantern]

Thanks, I stand corrected. I wasn't aware they made changes and proxy the audio now....good to know.

I suppose they made the change to mitigate firewall issues at the customer's router. In the past, they suggested forwarding a wide range of ports on the router to prevent blocked, one-way audio issues due to the audio coming from a different IP (terminating carrier) than the SIP server...

at risk of getting off topic... I believe that this change has rendered the "force media proxy" setting in the control panel to be meaningless. can anyone confirm that?

[burris]

Would you guess then that those of us who have major port forwarding enabled for many years now, can disable the port forwarding?.

[racerdude]

Would you guess then that those of us who have major port forwarding enabled for many years now, can disable the port forwarding?.

I used to have dozens of port forwarding rules setup on my router for each of the RTP audio providers, it was a real pain especially when I found a new one (one way audio) and had to go add the port forward rule and redial or have them call me back. I finally just gave up and port forwarded all UDP traffic on my RTP ports to my SPA2102 and haven't had any issues since. I did change the RTP port range from the standard ones to a different range and also the SIP port numbers on my SPA2102 just to avoid any issues with random calls from hackers that I've read about on other message boards.

But to answer your question - if you do require port forwarding on the RTP ports you can try just setting it to the ones I posted above for outgoing calls and for incoming calls I am seeing 174.36.46.53 (verify that these are the same ones for you). This should work until they change to proxies and you get one way audio..... Or just forward everything like I ended up doing and if you get strange calls then change the RTP ports to a different range.

[burris]

Thanks for your reply..

Many years ago Brandon advised me to port fwd 5004-65000-Since then I have never had a problem.
I think this is safer than DMZ and it doesn't affect any of my other devices or network.

Maybe Tim will offer an opinion at some point..

thanks again..