Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

After replacing UTM vs. XGS VoIP calls from other sites have no audio

Hi all,

we recently replaced the SG115 with an XGS116. We have rebuild all the FW rules and NAT exactly the same as it was in the SG115. We have two other sites connected to the XGS which are accessible both ways. Below picture show the firewalls. I can reach the phone server from both remote sites. I also see the phones are registered via UDP 5060. Status of the remote IP phones in the phone system are up and reachable. I can send a ping to 192.168.168.250 from any remote IP phone. Traceroute from both remote sites are going through to the phone server. Also a trace and ping from the server to any IP phone works.

Calls from or to the remote sites are without any audio.

On the SG115 side I can see UDP connections from 192.168.169.107:29100 to 192.168.168.26:5004 and 5005. If I look on the XGS firewall log, I can´t find any matching connections but I see them in capture log. Why?

Logs...

UTM:

XGS:

XGS packet capture:

Any ideas?



This thread was automatically locked due to age.
Parents Reply Children
  • Small update - we have figured out the issues. It was a VLAN that was interferring with the LAG interface. SIP calls from and to remote sites are working again. Last issue is with the IP phones from our home-office workers. We have a DNAT and FW rule that allow SIP registering to the phone system and SIP calls. The phone is ringing but no audio.

    I did a trace and more checks and see the connection from/to the IP phone in our LAN (IP phone address 192.168.168.26) is trying to send UDP packets to the private LAN address of the remote IP Phone (192.168.178.20) which of course will not work.

    I am not sure where to search for the changes to be made. Is this SNAT or DNAT?

  • Hi Martin Nowak,

    thanks for the update, were you able to get this issue resolved, we kinda have same issue going on right with a one way audio.

    regards