So, I've read many posts on here about audio issues with One-X and still haven't found a solution for our issue. Our phone vendor also can't figure out the problem. Our issue is that we can use the One-X mobile app to connect and make telephone calls on our internal network, although voicemail will not play. When connecting EXTERNALLY the app will connect, the light shows green that VOIP is fully connected, and you can place a call to an internal extension but there is no audio at all. Voicemail still does not work externally. Here is our general config:
One-X Server and Voicemail pro are on the same Server 2012 R2 machine, and has an internal dns entry for an externally resolvable FQDN that points to the internal IP address. The IP Office server also has the same DNS config. At our firewall we have dedicated external IP addresses, one each for One-X and IP Office. External DNS resolves to the same FQDNs for each server and points to their respective public IPs. We have a one-to-one NAT rule at our firewall, and for testing purposes I created a rule that does straight one-to-one mapping with NO port blocking at all. I only turn it on when testing to reduce the attack surface. I created that rule to eliminate the argument that a port isn't open. When that rule is in place, all of the web interfaces for both systems are accessibly externally through their FQDNs, so I know the rule is working and not blocking ports. Also, running a packet trace on traffic passing through the firewall shows that connections are being made on various ports. Curiously UDP traffic is missing from the packet trace. Does anyone have any ideas on what could be going wrong? This has been going on for months. We have a Fortigate firewall, if that helps, or if anyone has come across issues with One-X and Fortigates.
Thanks!
One-X Server and Voicemail pro are on the same Server 2012 R2 machine, and has an internal dns entry for an externally resolvable FQDN that points to the internal IP address. The IP Office server also has the same DNS config. At our firewall we have dedicated external IP addresses, one each for One-X and IP Office. External DNS resolves to the same FQDNs for each server and points to their respective public IPs. We have a one-to-one NAT rule at our firewall, and for testing purposes I created a rule that does straight one-to-one mapping with NO port blocking at all. I only turn it on when testing to reduce the attack surface. I created that rule to eliminate the argument that a port isn't open. When that rule is in place, all of the web interfaces for both systems are accessibly externally through their FQDNs, so I know the rule is working and not blocking ports. Also, running a packet trace on traffic passing through the firewall shows that connections are being made on various ports. Curiously UDP traffic is missing from the packet trace. Does anyone have any ideas on what could be going wrong? This has been going on for months. We have a Fortigate firewall, if that helps, or if anyone has come across issues with One-X and Fortigates.
Thanks!