4 Digit Internal number

We have LYNC 2013 pool. Our users' phone number is in "123-456-7890" format with internal extension "7890". We have normalization rule to match pattern ^(40\d{2})$ and translates to +1123456$1. When user dial 4 digit internal extension from Lync client, the display on deskphone is showing full 10 digits (1234567890) instead of 4 digit extension and user name. 

I have tried Translation rule $1 ( without any digits added), but still displaying 10 digit number.

We want deskphone display shows only 4 digit extension  and calling user name ( as regular desk to desk call).

What is the best way to show user name?

We have Avaya PBX.

Thanks in Adva

July 31st, 2015 4:52pm

What phones are you using?  Is the caller ID shown on the Avaya side or the Lync side? 
Free Windows Admin Tool Kit Click here and download it now
July 31st, 2015 5:02pm

Hi

The Lync client will normalize phone numbers that match rules in the users dial plan on Lync. This is by design.

If the extension numbers are not internal to Lync and are on Avaya PBX, then you could create a normalisation rule at user level that essentially does nothing but allow 4 digit numbers. Then on the trunk configuration to the Avaya PBX add a normalisation rule there on calling number translation rules to explode the extension into full number.

If you are calling Lync to Lync users then you are best using SIP addresses rather than extension dialling.

thanks

July 31st, 2015 5:03pm

We are using Avaya phones. I am talking about the display on Avaya deskphone when we call from Lync client (4 digit extension, not Lync to Lync)

Free Windows Admin Tool Kit Click here and download it now
July 31st, 2015 6:15pm

Are you using an SBC?

You can tell Lync in a trunk translation rule to change the calling (not called) number to 4 digits which should help.  Not much more modification you can do with pure Lync than that.

July 31st, 2015 6:21pm

Hi Tek-Nerd,

 

Agree with Anthony.

You may try configuring Calling Number Translation Rules to change Display Number. You can define the translation rule to manipulate the request URI before you route it to the trunk peer.


 

Best regards,

Eric

 

 

Free Windows Admin Tool Kit Click here and download it now
August 3rd, 2015 3:40am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics