Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel MSL 9.1 with MAS 2.0 in LAN-Mode (Server Only) running AWC 3.7

Status
Not open for further replies.

MitelEngineering

Technical User
Oct 12, 2006
42
GB
I have a site running MSL 9.1.24.0, with MAS 2.0.103.2 and Audio and Web Conferencing (AWC) 3.7.1.4. The Server is sitting on the customer LAN in Server-Only mode, there are no other Mitel applications on the network, so no Mitel Web proxy. The question I have is regarding the specified requirement of 2 x Public IP addresses. Is this still the case in the above setup?? As I really cannot see what the second public IP is used for. In the AWC_Config&Maint manual, It shows the server as having 2 x public addresses mapped, for 80+443 on one and 443 changing to 4443 on the other. If you browse externally to the FDQN on public IP one, you can still get to the AWC portal. So I can't see what the second public address is for. In the MAS_EG_R2.0 manual it makes no mention of this second address? thanks in advance for any help given..
 
That's the same question I have. I haven't been able to figure out where it's even addressed in the AWC.

DryAquaman
 
This is done in order to avoid requiremens to open non-standard ports trough the firewall. The server for the web conferencing component is listening on port 4443, so if you map 4443 to 4443 on the firewall and in awc configuration specify internal and external ports as 4443, you should be fine with just one IP.

The concern is valid for both sides, your server and your clients in the public Internet. As it is common to be able to connect to HTTPS web sites from inside of organizations networks, it could require additional provisionings to enable access to port 4443 for clients. This is why Mitel is suggesting to re-map it on your firewall and make everybodys life easier.
 
From further investigation, I've just found the answer I was looking... The second external IP is used for the Web Collaboration Client communication to Connection point, as both web broswer requests are made on port 443, the second address rule requires the port change to 4443.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top