MXe Server for ISS - Deployment Information Desired

[phoneman429]

Has anybody deployed one yet? We've sold our first one, I've been through all the testing, but can't figure out how to manage any PBX features/functionality, we won't have the server itself until around the 18th of January, I'm trying to see how to integrate the 3300's with the server so I don't have to open a ticket with support as to what to do next after I install the MSL & blade(s). Thank you for any help/enlightenment in advance, -Mike

 

[Mitelmatt]

Hi

Have you downloaded all the documentation on Installing on ISS?

 

[phoneman429]

I've taken evry test I can find, our AE has pointed me to all the docs, none get beyond installing the MSL & the blade.

 

[Mitel100]

Once you have installed the ISS software, you will need to install the Mitel Communications Director Blade, which is downloaded from MOL. License your ISS by entering your ARID (Application Record ID).

After this you will need configure the System IP address for the MCD for ISS blade. I am sure you are aware that the IP address should be in the /30 subnet.

After this has been done just browse to that IP address like any other 3300.

Hope this helps



__________________________

There is no 'I' in 'Team'
__________________________

 

[phoneman429]

Not really, all the documentation states this puppy is IP only, it states what forms aren't available as a result, I have (9) controllers that will be added, (2) as trunking gateways and (7) as survivable branches. Do I administer these like OPS and they're just (9)stand alone PBX's to manage? Do I just setup IP trunking/networking between the server and the ICP's and that's it?

 

[Mitel100]

when it says that it is IP only, it will not support the following:

- AMB and AOB
- T1/E1 modules,
- Quad CIM modules,
- Quad FIMs --therefore, NSUs, DSUs, and Peripheral Nodes.
- Embedded voice mail
- 3300 Internal DHCP server

So you trunking gateways could not be migrated unless they are using SIP. All 3300 would have to have IP Trunking.

If you have an Opsman, you just use it in the same way.

__________________________

There is no 'I' in 'Team'
__________________________

 

[phoneman429]

No SIP trunks here, were deploying 2 MXe's with 4 PRI's each, and 7 CXi's with POTS lines for survivabilty and resilience of 2000 users across all 9, no OPS and this has been engineered with/by Mitel. The same engineer said the server-manager will give me an interface to manage everything, but to-date I haven't seen it and was wondering what it was like or what kind of a chore will it be.

 

[SXWizard]

It looks like you're installing 9 3300 controllers, not ISS (Industry Standard Server). So forget about ISS and just install MCD 4.0 on the 9 controllers and go from there. ISS is MCD deployed on a server (not 3300 controller) and is IP only relying on 3300 controllers for TDM gateways (non SIP trunks, analog, etc).

 

[phoneman429]

Guys, I certainly appreciate the input, but the ISS is being deployed with the 9 controllers for trunking gateways, resiliency, etc. This job was engineered by Mitel, the MCD for MXe Servers Rel. 4.0 I&M Update shows the same with the now discontinued MXe Server (on page 4), which is being replaced by the ISS. I just didn't want the deer in the headlights look when we have to deploy this with their IT staff "over-seeing" this. My supervisor is trying to get a webinar/collaboration set up with their engineers for an overview next week, I was hoping there was a tech who'd already put one in and could chat a few minutes on the phone, somebody with real world experience, not engineered perfection. I guess I'll either get schooled next week or in front of the customer. Thanks to all and have a Happy New Year!

 

[tlpeter]

If i am right it is a Sun server with virtual 3300's running on it.




ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Mitel100]

If it was designed by mitel asked for the TAD. This sould be available, I would only be concerned about the Trunking Gateways. The TAD would detail how this design is going to the implemented.

Currently we are all guessing about how this is going to be set-up. But I would agree, tlpeter it would be a Sun Server, or they would be implementing MICD on one or two Industry Standard Servers.

__________________________

There is no 'I' in 'Team'
__________________________

 

[Mitelmatt]

no it's not on a sun server. As of MCD 4 the ISS version can run on HP, IBM or Sun, just need to check the MSL Server guide.

Ok, so at a guess you have a central MCDfor on ISS for all IP users then the MXE and cx's are for remote survivability and analog plus gateway to PSTN

The ISS server would connect to the gateways via Minet Ip trunking and clustered using the new SDS method rather than ops. You then create an Admin Group which allows Reach through to all controllers. This way you only need to log into 1 controller and can view forms on any of he other controllers via a drop down list.

This is all covered in MCD 4 training.

You've got to get out of your hea that because the software runs on a server that it's any different because its not. You just haven;t got any TDM intefaces that's all.

 

[IrwinMFletcher]

The MCD-ISS is the software only version of the MXe-Server that runs on HP, IBM, or Sun. There is no functionality difference between the two.

Note though that the MiCD is different, that too runs on a server but it allows multiple software instances of the MCD software.