SIP trunk between cucm 7.1 and Mitel 3300

[jf1221]

I read the PDF and i have set up the trunk...However, whenever i dial from Mitel phone, I get invalid number. I did configure routes and digits mod...

[martyn]

If you do a sip tcpdump from the Mitel, what does it show? Post here if you want and it should be an easy enough thing to figure out.

Also are you going directly to cucm, or via a cube?

[jf1221]

it's to call manager no cube involved...uploaded two files.

[martyn]

So it looks like you are trying to call extension 3320 and the CUCM is 10.21.66.11 and the Mitel is at 10.21.67.153. Are these correct?

The SDP shows that the CUCM is saying that 3320 is not a valid number on the system. Is there an inbound CSS on the SIP trunk on CUCM, and does that CSS include the partition that 3320 is in?

[jf1221]

yes, those are the correct IPs. On CUCM, the ext 3320 does exist and does work. It does a css and partition. however, according to the PDF that i have attached, it doesn't mention anything about creating additional CSS or partitions, just a route pattern. I have attached the PDF. Did I miss something on the PDF?

[martyn]

What are your significant digits, and CSS under the inbound section set to? Does the CSS include the partition that the phone is in?

[jf1221]

What are your significant digits : all
CSS under the inbound section set to css-sat-device
 Does the CSS include the partition that the phone is in.. It does now.

so I changed the CSS to css-sat-device on everything and i can call from Mitel to cisco phone.... Mitel phone 2210 -----> cisco phone 3320...However, when i pick up on cisco, it goes to fast busy. When i try to dial on the Cisco phone, as soon as i hit the second 22XX, i get dial tone....if I ignore it and dial all the way, i get a fast busy.

[martyn]

Can you do another trace now that the CSS is included, as it sounds like you are able to call now, but my guess is that there is a codec mismatch, but a trace should confirm.

[jf1221]

Absolutely...i was just about to do that and post....standby

[jf1221]

I keep getting an error has occurred when i am trying to post...can i email it to you?

[martyn]

I keep getting an error has occurred when i am trying to post...can i email it to you?

yep sure, i'll pm you my address

[martyn]

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.

[ralph]

Thanks martyn,
A doc for this would be great.
Would you mind exporting the SIP Peer profile and posting it up here?

Ralph

[martyn]

Yep sure, can do.

I am about to rebuild my Cisco CUCM lab so once I do that I'll get a lab Mitel set up and document it all and get a sample SIP peer profile.

[P83097]

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.