Incoming calls not working for Mitel MBG. 1

[Richard_Harrow]

So we have an embedded MBG on a Mitel SMB with MiVB 10.1 along with an EX-Controller that has all the extensions registered on it.

Outgoing is working, but we can't seem to get incoming to work and there aren't any traces showing up on MiVB.

We don't have any routing rules set in the MBG nor do we have any digits being absorbed or inserted in the SIP peer profile. Both of them are blank within the profile.

Could someone help me out on how to go about setting incoming call for the MBG?

 

[The mitel guy]

I dont know the platform but check your router settings something sip related is being blocked

 

[The mitel guy]

Im just guessing.....

 

[Richard_Harrow]

I dont know the platform but check your router settings something sip related is being blocked

Thing is, it's deployed in server-gateway mode with the SIP trunk coming directly from the ISP's device and going into the eth1 port of the SMB controller. There isn't anything in between the SMB controller.

When looking at Wireshark traces from the MBG, it looks like the incoming call is being rejected from by the Mitel controller.

 

[The mitel guy]

Check licensing.. maby a feature needs to be turned on? Tell me about the mitel controller. info specs?

 

[Richard_Harrow]

Check licensing.. maby a feature needs to be turned on? Tell me about the mitel controller. info specs?

Basically, the main controller with all the extension information is an ex-controller that is clustered with an SMB controller that has an MBG blade hosted on it.

The main controller's your regular 16G EX-Controller.

 

[The mitel guy]

It has nowhere to land the call so its rejected? Check incomming call routing

 

[The mitel guy]

I dont know this system i have 24 years pbx and i love them. I can offer advice based upon expierence... but i might be way off base in some cases...

 

[The mitel guy]

Also this might be as simple as a protocol change or even a codec...

 

[Richard_Harrow]

It has nowhere to land the call so its rejected? Check incomming call routing

We already have DIDs assigned to the extensions. When calling from those extensions, the DIDs are showing which means they're mapped so I'd appreciate it if you could further guide me on where the incoming call routing tab might be on MiVB 10.1 since the dial inward tab already has the DIDs in it.

 

[The mitel guy]

I saw a hitachi hcx 5000i get taken out of service because of a 0 in the wrong spot.

 

[The mitel guy]

Let me do some reading i will see what i can come up with..

 

[The mitel guy]

Again guessing Is the call being rejected because of the DID being the wrong amount of digits expected

DID DIGIT LENGTH? GUESSING.....
INCOMMING SMDR.. worth the logs...

 

[jpruder]

You will need a routing rule think a wildcard is uri * going to desired controller

 

[The mitel guy]

You will need a routing rule think a wildcard is uri * going to desired controller

Im in over my head here...

 

[Richard_Harrow]

Also this might be as simple as a protocol change or even a codec...

The ISP's already confirmed that the protocol needs to be UDP.

 

[Richard_Harrow]

You will need a routing rule think a wildcard is uri * going to desired controller

Yeah, I already have a routing rule set for that. It's set to request uri with * and then the desired controller.

 

[Richard_Harrow]

Again guessing Is the call being rejected because of the DID being the wrong amount of digits expected

DID DIGIT LENGTH? GUESSING.....
INCOMMING SMDR.. worth the logs...

It's possible and that's what I'm trying to figure out because this is my first time working with Mitel's MBG. Do I need to set any digits for absorption and insertion in trunk attributes or can I leave them as blank?

 

[jpruder]

Trunk attribute Dial-In Trunks Incoming Digit Modification - Absorb should have a zero and Direct Inward Dialing Service should be on. This is assuming you are getting 10 digits and there are entries in the DID form

 

[Richard_Harrow]

Trunk attribute Dial-In Trunks Incoming Digit Modification - Absorb should have a zero and Direct Inward Dialing Service should be on. This is assuming you are getting 10 digits and there are entries in the DID form

Thing is, the country where this controller is in uses 8 digits. We have 8 digit DIDs defined on each user which I think automatically makes entries within the DID form if I'm not mistaken.