Mitel Forums - The Unofficial Source
Mitel Forums => Mitel Software Applications => Topic started by: Mattmayn on April 29, 2016, 03:06:00 PM
-
SE is telling me that a single MBG server cannot have SIP trunks and remote users. Are they really mutually exclusive? I always thought you could run both on the same box.
-
That doesn't sound correct to me. I'm pretty sure I've done that.
Ralph
-
I know for a fact that it can be done. I'm a TW user and there are SIP trunks on the same vMBG.
-
I thought so too. I am positive I have done it before. According to my boss the SE said you need different IPs. My response was that is what ports are for.
-
SE is telling me that a single MBG server cannot have SIP trunks and remote users. Are they really mutually exclusive? I always thought you could run both on the same box.
Sales Engineering is wrong, or misunderstanding, unless there is something special about this site that I am missing and they see, which is possible.
But I have done this LOTS of times... Almost every installation I have of MBG or MiCollab that has SIP trunks has remote users that are both MiNET and SIP devices as well.
Now, I do have a couple installations that have to have 3 network interfaces, one for the SIP trunks (connects to a SIP provider's interface directly), one for remote phones and other services (normal public IP), and the normal internal interface. On all sorts of software releases, including the current one because I just set this up a week ago on a new install. I also have several customers with 20+ trunks and 20+ remote phones on the same MBG with the same public IP and interface..
This is a pretty common scenario actually
-
Is secure recording being done? this may cause an issue because it must be lan only to be supported from what I read.
-
nope, you can do secure recording on a teleworker setup, no restrictions there.
unless you have some very odd config that you didn't explain, your SE is a tad mistaken, lots and lots, thousands, nay, tens of thousands of customers run TW sets and sip trunks over the same MBG.
-
This is from MBG help:
MBG provides a secure recording connector (SRC) service that allows third-party Call Recording Equipment (CRE) to record Mitel-encrypted voice streams. Two call recording configurations are supported: Direct and Indirect. The SRC service is supported only in a LAN configuration with MiVoice Business/3300 ICPs
-
This is from MBG help:
MBG provides a secure recording connector (SRC) service that allows third-party Call Recording Equipment (CRE) to record Mitel-encrypted voice streams. Two call recording configurations are supported: Direct and Indirect. The SRC service is supported only in a LAN configuration with MiVoice Business/3300 ICPs
Interesting... and wrong.. Can you point me to the help location that says that and I 'll get it fixed.
Thanks.
-lee
-
Here is a screenshot of the current help file
-
Thanks, found it.. I'll contact the doc writers and get this corrected.
-
So dilkie are you saying I can run this in server-gateway mode?
-
yes, of course. You can add tap licenses to any MBG and connect your call recorder to it (use the lan side ip address to connect to).
-
SE is telling me that a single MBG server cannot have SIP trunks and remote users. Are they really mutually exclusive? I always thought you could run both on the same box.
Nonsense. They do use separate licenses though.
-
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.
-
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.
-
go read it for yourself
http://edocs.mitel.com/UG/Apps-Solutions/MiCollab%207.0/MBG/MBG_9.1_IM.pdf
page 7, overview...
-
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.