Quote:
Originally Posted by martin
Looking at your log snippets, my guess is the reason the ACK is *not* being sent directly to the Contact URI is because Voxalot NAT handling is kicking in and changing the Contact URI.
If the have "Symmetric NAT Handling" set to yes and your Contact URI is and RFC1918 address as highlighted in your log:
Contact: <sip:246875@192.168.1.3>
Then Voxalot will change this Contact in the 200 OK message before passing it back to the PSTN gateway.
|
My voxalot Symmetric NAT handling is set to NO. The 600 echo test works fine.
As I mentioned in an earlier post, eventually an ACK arrives with the proper REQUEST URI. Up to that point there is two way audio. So with the arrival of a proper ACK the phone is satisfied but incoming audio ceases. Is it possible that voxalot is changing the media address to a private address as well? Private addresses can not be routed through the internet. My outgoing proxy is associated with an rtp proxy/media relay and the SDP contained in the 200 OK specifies a public address.