Messages

1

Mitel MiVoice Business/MCD/3300 / Ring Groups/MD Ring Group

« on: June 06, 2016, 03:51:37 PM »

Setting up a ring group for our internal helpdesk users.  However many of them have Multi Device ring groups for their cell phones (external hot desk users).  The problem is they don't want the calls for the ring group to go to their cells.  Is there a way to make the ring group only ring the desk phones, yet still allow other direct calls to ring the cells? 

Thanks!

2

Mitel Software Applications / Re: MiCollab Client Mobile deployment

« on: May 18, 2016, 10:49:20 AM »

We ended up getting a UC Cert to install on MiCollab, and the 2 MGB's.  A UC Cert from Godaddy will cover 5 hostnames.  Once we installed that cert on the MGB's everything worked fine.  Only thing we changed in our deployment profile is defined a specific MGB for teleworker, as the MGB also acts as the proxy to MiCollab.  Once I got all those certs installed, and settings verified it worked great. 

One thing to look at is the Diagnostics tab within the client deployment.  Run that before deploying a client, once I got this test to pass everything worked great. 

3

Mitel Software Applications / Re: AWC/Remote Proxy

« on: May 18, 2016, 10:44:48 AM »

I think it's and ISP problem with the address I selected.  I changed the second IP to the next available in my subnet and it works fine now. 

4

Mitel Software Applications / Re: Trunks and TW users?

« on: May 13, 2016, 07:23:32 PM »

We just had a new system installed and our installer and their engineers said the same thing.  I told them if that is the case then they owe me 2 more MGB's.  So now I have 2 MGB's at the main office, one for for SIP TRUNKS, the other for Teleworker and acting as the web proxy.  Then 2 in the backup office with the same configuration.  Only thing they ran into is issues with the trunks on the 2 MGB's in the same cluster.  Once they were separated all worked fine. 

5

Mitel Software Applications / Re: AWC/Remote Proxy

« on: May 13, 2016, 06:58:46 PM »

Perfect, I thought that was the case but wanted to verify first.  After adding the second IP address to the MGB it now let me add the proxy for the AWC.  I also setup the 2 DNS records on the public side pointing to these 2 IP's on the WAN interface. 

Only thing I seem to have an issue with is I am not able to ping that second IP address from outside its network.  IE, from a device on the same layer 2 network I can, but from another subnet I can't.  But I can ping the first IP of the WAN interface.  I would assume that the second IP would use the same gateway?  Not sure if there is something that has to be defined for ARP proxy??

So internally micollab.abc.com and micollab2.abc.com point to the same LAN address, where on the external DNS micollab.abc.com points to WANIP1 and micollab2.abc.com goes to WANIP2

6

Mitel Software Applications / Re: AWC/Remote Proxy

« on: May 13, 2016, 05:37:04 PM »

Does this effect anything with the way the MGB is currently licensed?  Would I need to get a license or record modified?

7

Mitel Software Applications / AWC/Remote Proxy

« on: May 13, 2016, 05:03:13 PM »

Attempting to setup my MBG's to act as a proxy to the Micollab/AWC server.  The MBG is configured on the network edge. 

Proxy works great for Micollab and the client, however when attempting to set the proxy up for AWC I get notified , MSL must have a second WAN interface configured in this mode for AWC to function.

The AWC server does have 2 IP addresses, and 2 fqdn's. 

Is this stating that the MGB needs 2 WAN interfaces?  If this is the case are the 2 WAN interfaces bridged, or separate IP addresses?


Thanks,
Dave