Trunks and TW users?

[dilkie]

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.

Don't know what to say. Unless you have very unique/odd setup, you can run trunks and TW sets and do call recording and web proxy all on the same MBG. And clustering is supported for all this. For sip trunks, you need to obviously configure the mcd and the sip trunking provider to support resiliency via the backup MBG's.. but it works fine.

[dilkie]

go read it for yourself

http://edocs.mitel.com/UG/Apps-Solutions/MiCollab%207.0/MBG/MBG_9.1_IM.pdf

page 7, overview...

[Navarre]

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.

What issues did they run into? The only reason to spread out these services is redundancy and load balancing.

How many TW users do you have? How many channel licenses for the trunks? If they're low traffic then you can absolutely put them on the same box. A cluster of 2 will at least provide some high availability though.