For the MCS to be able to support teleworker SIP extensions (either Phone Manager Desktop Softphones or 69xx phones), it needs to know two pieces of information:
- The internal IP Address of the MBG
- The external IP Address of the MBG
The internal IP address of the MBG needs to be known for two reasons. The first is so that the MCS can identify which 69xx phones it receives requests from are actually Teleworkers. The second is so that it knows how to communicate with the MBG's API for SIP User deployment.
The external IP address of the MBG needs to be known so that it can be passed to Phone Manager Desktop and 69xx phones when they are registering their SIP connections.
Configure the MCS with the MBG's Internal IP Address:
- 'Configuration -> Site Settings -> Phone Systems -> MiVoice Border Gateway', enter the internal IP address of the MBG
Configure the MCS with the MBG's External IP Address for each Node:
- 'Configuration -> Site Settings -> Phone Systems -> [Your PBX Name]', enter the external IP address of the MBG into the NAT IP Address property for each node. If the external registration port for SIP has been changed on the MBG, update the NAT SIP Port as well.
Configure the MCS with the MBG's External IP Address for Remote Client Connections:
- 'Configuration -> Site Settings -> Client Locations -> Remote', enter the external IP address of the MBG into the 'NAT IP Address/Fll Hostname' property. This will be used to provide the remote 69xx phones with the URIs they need to communicate with the MCS server for firmware/softkeys etc.
Once the MCS has the information above, it will be able to identify teleworker 69xx phones and will be able to pass them the information required to connect to the MBG.
The External IP Address entered into the remote section of the
Client Locations will also be used by Phone Manager when connecting to the MCS Server.
