CLID on MSDN

[jazwinner]

Calls with CLID show-up when traversing the network fine, but if CLID is blocked (or unavailable) the display shows either the trunk-port (not the trunk label) or the cluster element info. Is all display info controlled via COS for the station, or is COS for trunk involved too? Any quick rules to ensure CLID (or trunk label) info is maintained across the MSDN net?

Thanks!

 

[Lundah]

Trunk COS is involved here as well, but I don't have specifics in front of me. Normally it something I'd just keep playing with until it looks right.

 

[kwbMitel]

What I would expect to be displayed if CLID was missing is the Trunk Service Assignment Label. If you use a different Service assignment for each trunk it might appear as if the trunk port is being displayed.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Lundah]

If you have no incoming CLID, and the Trunk Service Assignment label is blank, I think you should see the trunk number in the display on an incoming call.

 

[jazwinner]

We've double checked all the TS labels; time to triple check, might be something simple like extra space somewhere... Running 34.2.0.20, and I'm sure it was fine prior to all the ARS rework. Thanks for the input!

 

[kwbMitel]

Lundah is correct, I forgot about the Trunk Service assignment Label being blank.

Verify that the trunks are using the service assignment you think they are. I got burned once when someone assigned service assignment 101 instead of 1 and it left me scratching my head for hours.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.