Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: mszodiac on April 19, 2016, 11:00:59 AM

Title: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: mszodiac on April 19, 2016, 11:00:59 AM

Hi everyone!

We have a few sites in Australia and New Zealand that were using Nortel Option 11s.  CLID worked on the PRI ISDN.

We recently changed them to a MITEL MiVoice Business, and CLID stopped working on PRI calls.  Incoming calls only showed the trunk label "E1 PRI".

I've done CCS, EDT TSP, and EDT TRACE VDSU traces all of which confirm there is no calling number and calling name sent by the CO.

Telco confirmed they are sending us the CLID.  Apparently, it is only a check mark on their system. 

On the Nortel configuration, there are many ISDN options to set like the country and interface type which are not available on the MITEL.

Some notes online show Australia, New Zealand and other countries in Asia use "Bellcore" protocol variant of CLID.

Has anyone dealt with a similar issue? Any ideas? Thank you.

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: ralph on April 19, 2016, 01:22:03 PM

Look at the COS of both the end user device and the trunks to be sure that CLID is enabled.

Ralph

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: acejavelin on April 19, 2016, 01:38:18 PM

Assuming the system is programmed correctly as Ralph indicated, this is controlled by the Protocol variant (Bellcore, DMS100, 5ESS, etc). You would need to match the 3300 to what the carrier is providing, most current PRI circuits in the USA use Bellcore, but in the past it could be almost anything so if the PRI was existing on the old system you will need to find out the protocol variant used and match it in the 3300, or have the carrier change it to one the Mitel supports.

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: mszodiac on April 19, 2016, 02:08:37 PM

Thanks for your replies!

I've asked our local tech to get the ISDN config from the Telco and I'll match it with the 3300. 

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: sarond on April 19, 2016, 07:38:14 PM

In Australia we use the ETSI protocol. We are E1 not T1.
Protocol will be set as Euro ISDN
Protocol variant set as Euro Standard.

Also attached screenshot of Digital Link Descriptor form of one of our sites.

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: mszodiac on April 25, 2016, 11:20:41 AM

Thanks sarond!

I'll give this a try and will update this forum.

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: mszodiac on April 25, 2016, 11:36:02 AM

On the help files, ETSI variant is only available under QSIG protocol type.

The system is currently set as Euro-ISDN with Euro-Standard ISDN.  I guess I'll need to setup a short outage to make the changes.

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: sarond on April 25, 2016, 07:35:16 PM

No don't.

Leave as  Euro-ISDN with Euro-Standard ISDN.
That is correct.

It is most likely another issue.

Maybe the nortel was using something different?

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: Dutch on April 26, 2016, 04:01:35 AM

I assume the COS options for the Trunk and phones are checked already?

Gr,

Dutch

Title: Re: Calling line ID stopped working after system change from Nortel to MiVoice
Post by: x-man on April 26, 2016, 05:03:23 AM

Have you checked in system options that the caller ID type is set correctly to the system used. It can be set as either BT or ETSI type. Only there if your system type allows it.

UK only - Standard for CLIP; don't know if its there in Australia version.