Mitel & Nortel BCM Integration - QSIG - CLID

[tcanact]

Hi All,

We have just purchased 2x Mitel 3300 systems, a CXe and MXe. Currently this has been configured to integrate with our existing Nortel BCM 400 via QSIG. The MX is handling all incoming calls and passing them over to the Nortel where necessary.

Although there are a few issues when it comes to the integration, the one at the top of the list is regarding CLID between the systems.

If I call a phone on the Mitel system from the Nortel the name of the Nortel phone is displayed all ok, whcih is great, however if I do the same from a Mitel phone to the Nortel only the DN of the phone is shown, Ideally I would like the Name to be shown rather than just the extension.

The second issue, which is still related to CLI is we have found that if a call is answered by the Mitel and then the call is transferred to a Nortel extension the original CLID is lost and it looks like the caller is one of the phones on the reception desk, and users are unsure how to answer calls. However this isn't the case with calls to DDI's which are routed to the Nortel by the Mitel via System Speed Calls.

Could you please let me know if anyone has managed to get the CLI of the Mitel phones to display on Nortel BCM systems ok in the pas and also is it possible to forward on the original CLI of the inbound caller?

Thanks

Tom

 

[ianporter]

Has anyone found a solution to this as I'm having the exact same problem and the BCM guys tell me I'm sending data they can't decode.

cheers

Ian

 

[tcanact]

Hi Ian,

We are currently in talks with both Nortel and Mitel regarding this issue. We haven't had much luck as yet but are hoping to get this resolved shortly.

Nortel have identified the problem as being QSIG ASN.1 encoding related, the Mitel switch is sending a tag BCM doesn't support.

After running a trace on the Nortel the following was found: -

07 00
91 = ROSE
AA = NET_FAC_EXT_COMPONENT
23 00
06 80 01 00 82 01 00
8B = INTERPRETATION_COMPONENT
01 00
A1 = INVOKE_COMPONENT
17
02
02 05 43
06 = OBJECT_ID_OPERATION_VALUE_TAG
04 2B 0C 09
00 = CALLING NAME
30 0B = extra bytes that make the decode fail (PARAMETER_TAG ?)
80 = LINKED_ID_TAG
09 52 2E 48 61 72 74 6C 65 79 = "R.Hartley"

Some examples of the supported tags:
LINKED_ID_TAG = 0x80
NO_NAME_ID_TAG = 0x84
PRIVATE_NAME_ID_TAG = 0x87

The BCM doesn't support the 0x30 tag it's receiving, I'm informed that this is by design intent.

I have been told by Nortel that if we want this to be supported, we would have to put in an enhancement request.

If you manage to resolve this issue please would you post an update on here? I will do the same if I have any news.

Regards,

Tom

 

[tcanact]

Hi Ian,

How exactly are you interfacing the two systems together, are you using QSIG or DPNSS?

We are using QSIG, where one port of the Mitel T1/E module is connected to the Digital Trunk Media Bay Module on the BCM.

Thanks

Tom

 

[ianporter]

Actually Tom,

it appears we're talking about the same site )

never mind, I think there's talk of trying DPNSS now

Ian