Hello,
I'm hoping someone can help me to find a solution to this issue. I'm new to Shoretel, so if I'm missing anything, please let me know.
We have two separate networks
DATA = 10.20.2.0/24
VOIP = 10.20.50.0/24
The Shoretel server has two NIC's. One NIC is on the VOIP (shoretel) network as 10.20.50.1, the second NIC is on the data network as 10.20.2.34. Whenever managers are installing the shoretel call manager, they enter the shoretel server as 10.20.2.34. They get data, and all is happy. However, we discovered that we're not seeing any of the calls in the queues.
Doing a little snooping, we're seeing the Call Managers attempting to make connections to 10.20.50.1:135, instead of connecting to the 10.20.2.34 address. For testing purposes, I added a route on our firewall to forward traffic with a DST of 10.20.50.1 to 10.20.2.34, and low and behold it all works now.
While this works, this isn't really a solution we're looking for. This is more like a bandaid for the time being. Can anyone please advise of any place to look to find the settings for this? I'd like the call managers to pull all data from 10.20.2.34, and not revert back to try to get data from 10.20.50.1.
Any help or direction would be greatly appreciated.
Thank you.
I'm hoping someone can help me to find a solution to this issue. I'm new to Shoretel, so if I'm missing anything, please let me know.
We have two separate networks
DATA = 10.20.2.0/24
VOIP = 10.20.50.0/24
The Shoretel server has two NIC's. One NIC is on the VOIP (shoretel) network as 10.20.50.1, the second NIC is on the data network as 10.20.2.34. Whenever managers are installing the shoretel call manager, they enter the shoretel server as 10.20.2.34. They get data, and all is happy. However, we discovered that we're not seeing any of the calls in the queues.
Doing a little snooping, we're seeing the Call Managers attempting to make connections to 10.20.50.1:135, instead of connecting to the 10.20.2.34 address. For testing purposes, I added a route on our firewall to forward traffic with a DST of 10.20.50.1 to 10.20.2.34, and low and behold it all works now.
While this works, this isn't really a solution we're looking for. This is more like a bandaid for the time being. Can anyone please advise of any place to look to find the settings for this? I'd like the call managers to pull all data from 10.20.2.34, and not revert back to try to get data from 10.20.50.1.
Any help or direction would be greatly appreciated.
Thank you.
Comment