Messages

1

Mitel MiVoice Business/MCD/3300 / Mitel 6.0 and Cisco CUCM 8.6 migration question

« on: March 29, 2014, 03:15:40 PM »

Hi all, we have a customer who has expressed interest to gradually migrate from their existing Mitel solution to a Cisco communications manager solution. They plan to have both environments live with a SIP trunk for communication between the systems. As the mitel phones go bad (or budget comes available) they will buy cisco phones and move the extensions over, until everything is on cisco. We currently have the SIP trunk setup and working between the Mitel and Cisco for our proof of concept.

The extensions on the Mitel systems are a jumbled mess, meaning every time we move a single phone we need to create a new ARS Digits Dialed route pattern as an exact match (as apposed to a block of extensions) to point it to the new cisco system. This customer has about 1000 endpoints spread accross two Mitel servers (their version is below). Are there any limitations on the Mitel side that would prevent us from doing this process?

Mitel Communications Director

Release level: 6.0 SP1
Active software load: 12.0.1.24
Inactive software load: 11.0.2.66
System relink: No relink has been applied.
Call Control relink: no relink has been applied.
Platform: MXe, 512MB or RAM

Thanks

2

Mitel MiVoice Business/MCD/3300 / Re: SIP trunk between cucm 7.1 and Mitel 3300

« on: March 29, 2014, 03:06:27 PM »

Just for anyone else reading along now, or in the future, the document that was being referenced is quite old on the Mitel side (release 9 I think), and will only get you part of the way to having things working.

After a few dozen e-mails jf1221 is now all good and able to make calls both ways! 

There are a lot of options in the SIP peer profile that need to be changed in order for things to work.
Things like disabling mitel proprietary SDP, and preventing the use of 0.0.0.0, and making sure that early offer is used, are the main ones that will get things going that aren't covered in the referenced document.
You also need to make sure that in the trunk attributes you MUST have a 0 in the DID digits absorb, as without it you get a 503 service unavailable error when you try to make a call from CUCM to the Mitel.

If I get a chance I might try and create a new document as a reference.

Thanks for this info Martyn, we have a customer doing a similar integration between CUCM and Mitel, and ran into this exact issue. This was the silver bullet that corrected it.