Mobile Extension - Passing CLID

[RDECIT]

We've always had this issue with ME and no matter who we deal with we've never been given an answer. MCD 4 lastest build, ME and MSL latest build (downloaded today)

All twinning is setup fine and works. However the caller ID is not passed to the twinned mobile device, its the CLID of the office. Our own installation and a clients are both suffering the same problem and I'm not sure if it's a config problem or we've asked for the wrong service on our lines.

We've had Network Address Extension or 3rd Party Subaddressing as it's known enabled on the line but this has had no effect. I've created a route for the destination mobile device in ARS to by pass our LCR code. Internal and External Caller ID is enabled on ME. Has anyone else got this working, I'm in the UK if that makes a difference.

 

[Saywhat39]

This typically is a carrier issue. Can you manipulate digits with no issue such as pulsing your DID #? If that works just fine I might be able to point you at a couple different areas.

 

[SXWizard]

Under the Options tab in ME do you have External Calling Line ID and Internal Calling Line ID set to On> (This is how ours is set and the CLID works fine) From the Help file:

In the External Calling Line ID list, do one of the following:
- select On to enable caller identification (that is, the original caller's ID (CLID) is presented to the twin device (where available) for external calls)
- select Off to disable caller identification (that is, the Outgoing Line ID is presented to the twin device). Default setting is Off.

In the Internal Calling Line ID list, do one of the following:
- select On to enable internal calls (that is, calls made from the same 3300 ICP or cluster) to use the caller's CLID and normal CPN substitution.
- select Off to allow the Outgoing Line ID to be presented.

 

[kwbMitel]

All the above are true.

Make sure you can send a DID as Saywhat39 suggests.

If the DID test is successful try sending s different number that is not currently associated with your PRI. Often the Telco will not allow this step.

If you can't send a Non-Assoc number then talk to your telco about removing this restriction. They will probably require you to sign 911 liability forms.

If you can send a NON-Assoc number from a deskset, then try forwarding said deskset and calling it from a cell and see what number displays.

If all of the above is successful, then the issue is in the setup of the ME as SXwizard suggests





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

 

[isrm]

Check the replace external CLID is not set in the PRI configuration and also that default CPN sub is not affecting the call.

 

[RDECIT]

Thanks guys, lots to digest here. I'l take these suggestions away and let you all know how I get on.

 

[andy4uk]

I have experienced this problem with a number of my customers, as you can probably see it states within the documentation that this works - however as one of the guys as mentioned just above...... it looks like it could be a carrier problem - he is right, my problem turned out to be B.T.

Aparently B.T will not allow CLI to pass through as it is against their ruling..... or against the law, if you speak with Mitel UK they have it working - however they use a moblie carrier to route back out and this solves the problem.

Not sure how this works in other country's?

Andy

 

[fissure]

some SIP providers allow you to control outbound CLI (so if your telco doesn't/won't) that might be an option (to allow the Mitel to show the external caller's CLI to reach the twinned phone)

 

[RDECIT]

UPDATE:

Yes using associated directory number I can dial my mobile from the deskphone and it's DDI number is displayed.

Yes both options are set to ON - External Calling Line ID and Internal Calling Line ID.

When dialling in my mobile number is displayed on the DDI set, so caller ID is working.

We're using LCR codes, so for dialling my mobile I've inserted a route with a bypass code just for my mobile for testing. This enabled me to see the ddi number on the outbound call. However when I enable the twinning the main number is displayed again.

I've also tried applying the associated directory number to the twinned device, this has no effect the main number is still being displayed.

 

[RDECIT]

CCS Trace:

12:46:20 RI4 DPN 2B ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*233*dIBc#*58*CI*W6a#
12:46:20 RI4 DPN 17 SSRM_C *50*Calling Party Number#Dialled DDI Number
12:46:20 RO4 DPN 26 NAM *1#*50*6301#*166*6#*100*Username*1#
12:46:21 RO6 DPN 2B ISRM_I ;10;*3*1#*50*0Calling Party Number#*100*Calling party Name*1#
12:46:21 RO6 DPN 28 SSRM_I *19*Z#*58*CW*;7F;hpo@@@@AV^JpP#*58*C6*001#
12:46:21 RO6 DPN 2B SSRM_C *58*CL*E*0*7411*A0006717*A#12800797xxxxxxx
12:46:21 RI6 DPN 7 NIM *51*3#
12:46:26 RI6 DPN 13 NAM *4*4#*166*1 2 3 4#
12:46:32 RI4 DPN 17 CRM/CIM ;30;*166*1 2 3 4#*234*D@#
12:46:32 RO6 DPN 2 CRM/CIM ;30;
12:46:32 RI6 DPN 2 CRM/CIM ;30;