MiVB SMBC Controller with Embedded MBG Blade

[danramirez]

Hi Gents,

I am confused with the IP addresses and network set up for the SMBC Controller when using the embedded MBG.

For the ETH1 interface, shall we use a local IP address behind the customer firewall, or shall we assign a public/external IP address from the ISP?

Documentation is confusing:

From document "MiVoice Business Rel 10.0 Core I&M Update Course":

Page 42:

Eth1
- Always used to connect to the ISP.
- One Static External IP Address from the ISP for the MBG WAN Port.
- At initial installation, no IP Address assigned to Eth1.
- The MBG requires two IP Addresses: one is for the WAN connection to the ISP, and one is for the LAN as described above.

Then Page 51 says: The MBG uses a WAN IP Address programmed in MSL. This WAN connection is behind the Customer Firewall and connected directly to the Internet via an ISP Router..

Above is also confusing as it says WAN connection behind a customer firewall and connected directly to the internet.

Is it directly connected or behind thecustomer firewall?

Please let me know what you understand form documentation.

Thank you, Regards,

Daniel

 

[jpruder]

That would be an additional internal address

 

[Billz66]

pretty sure its same as server gateway - public IP has to be applied directly to the interface
- effectively makes it useless for customer site installations as they hate that config

 

[bojo3871]

Let me go on a bit of a rant here:

MiVB docs state "Deployment using all three MBG NIC Interfaces is not available on the SMBC MBG. SIP Trunks and Teleworker Phones must be on the same WAN Interface."
also "once the MBG WAN is configured, the WAN will be used as the Default Gateway for the platform. As a result, all external access will go through this WAN connection."

Local telcos in our region assign a customer WAN IP for SIP trunks. Usually, we assign this to the third interface of an external/off-board MBG. We then use the MBG WAN interface for the public IP facing the internet. But for the SMBC's MBG Blade, we can only assign this customer assigned IP on the WAN interface. Once we enable this, it becomes the default gateway for external connections and breaks the internet connection. Of course, it breaks the connection to AMC/SLS because this WAN IP is just for the SIP Provider WAN.

It's better for us to just deploy an external/off-board MBG provided we have a server to host it. (But it defeats the purpose of proposing the SMBC as a one box solution.)

 

[TCSI17]

@bojo3871 There are a few other reasons that the SMBC is not as ideal as a one box solution that I have come across too. What you stated above is accurate and an issue that I always have to deal with as well. a standalone MBG is the best solution, but again, then you need to virtualize it, or have own hardware for the MBG...again, not ideal.

The other 2 things that are issues is that the SMBC MSL does not have, is the ability to do port forwarding and MSL does not have a builtin DNS server (like standalone MBG does). It's this issue with not having a builtin DNS server that gets me. We cannot setup the MBG Proxy to remotely admin the systems as we don't easily have access to split DNS. We need to rely on clients DNS server for that. If they don't have one (such as small businesses don't), then you can't use MBG for remote access, you need to use another firewall to do that. Sometimes the costs associated with that standalone MBG/server to host it, is prohibitive. This is my experience and your mileage my vary.

 

[Billz66]

seems to be yet another short sighted design from mitel - express also had a heap of limitations and then they gave up on it , wouldnt be surprised to see this go the same way