AWC on MiCollab

[Joe King]

Hi
Can someone please help. I have MiCollab 7.0 and a standalone MBG which is clustered with the MBG on MiCollab for MiCollab Clients.
I need to setup AWC, I have assigned a 2nd external IP address to a 2nd NIC on the Standalone MBG and congfigured web proxy for this 2nd NIC.
DNS is correct as my first IP points to micollab.xxxxxxxxx.com for external softphones and my 2nd to conferencing.xxxxxxxxx.com. I can setup a web conference internal my DNS is setup for this but external I get a web proxy error page.
DO i have to forward my external IP on port 443 to the internal LAN address on port 4443 on the firewall. My MBG is in Server/gateway mode and works for teleworker traffic on the first WAN.

Any help please, thanks in advance

 

[jcarmichael1203]

Hey Chris,

You do not need to forward any ports. If the standalone MBG has the remote proxy services configured correctly that is basically it.

To access this externally you need to use on of the valid end user URLS (or admin urls for remote administration).

For the AWC, here are some of the valid end user urls: (you can find these on your standalone MBG, in the remote proxy services section, under Supported Applications tab)
/awv/
/awc/
/awcuser/
/vcs/
/call/
/slides/
/wd/
/wcrs$/
/awcwss/
/axis2-AWC/

Simply using the FQDN should give you a remote proxy services unsupported url error page.

My setup is extremely similar to yours but rather than using the AWC, I have the remote proxy setup for MiCollab.
If I use conference.xxxx.com, I get the remote proxy services unsupported error page. However, if i use conference.xxx.com/portal, I land on the MiCollab end user portal.


JCarmichael

 

[kwbMitel]

Also, the 2nd IP can be active on the same port as the primary IP. It does not need to be dedicated to a NIC

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Joe King]

Thanks for advise-I will try these.

 

[Joe King]

So I don't need to configure a 2nd WAN interface on the MSL console, but I do need a 2nd IP?

I am in S/G mode so how do get the 2nd IP to work, is it just the FQDN conferencing.xxxxxxx.com DNSed to the IP that matters.?

 

[jcarmichael1203]

I dont believe you would even need a second IP. If I am wrong hopefully someone will correct me.

I believe you should be able to have micollab.xxx.com and conference.xxxx.com point to 1 IP.

The remote proxy services will look at the FQDN in the HTTP request and then forward to the appropriate server.


Also just as a heads up, when you go to install the web certificates, you need to get the SSL Cert that lets you specificy SANS, as your MBG (that is gateway) will not work properly unless you have SANs listed for each application that you are forwarding via the web proxy.

 

[kwbMitel]

The second ip is required if you want to use collaboration or Video. It needs to be defined with a separate DNS name in the AWC settings. It needs split DNS to function differently for external connections vs. internal connections.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Joe King]

Thanks for your posts. I have now done away with the 2nd IP although it looks like i need it from the 2nd reply as I want to do external web conf

both micollab.xxxxx.com and conf.xxxxx.com point to the external address and internal which works fine. On the web proxy I have ticked the Conf box for MiCollab.
In AWC settings my server is conf.xxxxx.com

internally it all works fine, externally I can click the link in the email, enter my password, I see the join box enter my name click join then get directed to an invalid url wd/us-hc_main.html

Which address is it that users need to connect to externally, is it micollab.xxxxx.com for conf.xxxxx.com

 

[kwbMitel]

I believe you need a 3rd party Web Certificate but I cant say for sure.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[OldTimingMan]

Hey Chris, I'm setting up AWC also. Waiting on my second domain. Let me know how this goes for you. Might try to pick your brain when you get it set up or vice-verse.

From the manual, regarding AWC Web Conference Name: The additional hostname designated for the Web conferencing server. The hostname must resolve to a public IP address that is externally accessible. The internal DNS must resolve the hostname to the local IP address of MiCollab Audio, Web and Video Conferencing. For more information, refer to "Firewall and DNS Server Configuration" in the MiCollab Engineering Guidelines

From the manual regarding AWC Domain Name: Configured on the MiCollab server, the Domain Name cannot be edited through the MiCollab Audio, Web and Video Conferencing interface. This is the URL or IP address for users to access the Web page of the MiCollab Audio, Web and Video Conferencing interface. The name must be accessible to everyone who will be invited to attend a Web conference, both inside and outside of your local network.

 

[jpruder]

Was talking with Mitel yesterday and if the MBG is in lan mode i.e. DMZ, the firewall should translate the inbound 443 on the second address to 4443 before sending to proxy. I think you also need to add the hostname in the MBG so it know where to pass the info

 

[Joe King]

Thanks for all your posts-its working now.

I needed one WAN interface but in the MSL console you need assign a 2nd IP which has conf.xxxxx.com resolved.
This allows you to add a second LAN proxy just for AWC.