If a user does not have an extension configured, instead of requiring the user to enter their full phone number, Lync attempts to normalize the entered digits to the full E.164 phone number. The user experience is improved when users can authenticate with a short extension instead of a 10-digit phone number. A warning is displayed for users that do not have an extension configured Users without an extension receive a warning message on the dial-in conferencing page (see Figure 1). Also if you want to authenticate with your PIN on a Lync qualified phone, your extension and PIN numbers are required. If you dial in to a conference and you want to join as an authenticated user, you must provide your extension and PIN. Phone number extensions are used in multiple ways in Lync. Specify a Line URI that contains a DID number. Lync Server also provides the ability to suppress the caller’s ID by replacing it with another number (for more information readĪs a best practice make sure to always provide a caller ID that can be called back when calling outside the enterprise. Use the format where the call back number is specified as a global number and the user’s internal extension is added – for example Usually, this number is the company’s receptionist or auto attendant number. If a user does not have a DID number and can only be reached through an internal extension, configure a DID number as the caller ID so that the callee can return the call. (The next section encourages the use of the second format.) Use one of the formats where the user’s DID is specified as a global number – for example If the user has a DID assigned, it will be presented as the caller ID for all outgoing calls and no additional configuration is necessary. (DDI) – these numbers are globally unique phone numbers that can be called directly from the PSTN. To accomplish this, we have the following options: When the user does not have a public telephone number, we want to display the company’s receptionist or auto attendant caller ID, so that the called party can return the call. When a Lync user makes an outbound call, we want the called party to see a valid number so she can return the call. ), is used in Lync and an employee places outbound calls, the correct caller ID is not displayed. The following sections explain the recommended number format for each Line URI. A phone number is assigned to a Lync user when the Line URI property of the user’s Active Directory account is populated with a string similar to the listed examples. It is not recommended, however, to assign all formats to users. Tel:+12125550100 ext=863 where the extension is not part of the phone number.Īll these formats comply with RFC 3966. Tel:+12125550135 ext=135 where the extension is part of the phone number. The following are valid RFC 3966 TEL URI examples: The combination of the phone number and phone context creates a number unique. Local numbers – those that are not globally unique – must provide the context in which they are unique. E.164 is the standard for PSTN numbers and specifies country codes. Sign followed by digits that represent an E.164 number. Phone numbers can be either local or global. The RFC also defines additional parameters – such as extension, phone context, and so forth – to add to the TEL URI. RFC 3966 prescribes the format of TEL URIs in SIP. Let’s consider each of these objectives in more detail and provide recommendations for assigning phone numbers in different situations. Leverage telephone numbers configured in Active Directory. This enables a callee to quickly return a missed call. To provide the best user experience, allow room for future growth opportunities, such as expansion to other countries or merger and acquisitions (M&A).ĭesign your phone number plan for Lync to take into consideration the following objectives:Ĭompliance with Internet Engineering Task Force (IETF) standards. Defining the correct numbering plan is a crucial factor in the success of your Enterprise Voice deployment. When rolling out Enterprise Voice in your organization, use the following best practice recommendations to define your numbering plan and to assign telephone numbers to Enterprise Voice users. This article describes how to effectively assign phone numbers to Lync Server 2010 Enterprise Voice users. To provide the best user experience and prepare for future growth, it is important to use the correct numbering format when assigning phone numbers to users. First published on TECHNET on Nov 30, 2011
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |