Internal Extensions

Many times organizations will not offer DID numbers to users, or might assign DIDs to only some users. In this case, the remaining users only have an internal extension defined. This is a completely acceptable deployment option with Lync Server 2010, but there can be some confusion as to how the telephone URI should be assigned to user accounts.

The most common method is to identify a main office, or an automated-attendant phone number, that external users can dial and be transferred to in order to reach users with an internal extension. This type of attendant does not have to exist, but it usually makes sense to leverage this number in the telephone URI. After this number is identified, it should be used as the telephone URI with a “;ext=xxx” suffix. The number of digits in the extension field can vary depending on the organization or even the site.

For example, let’s say that Company ABC’s San Francisco office does not offer DIDs to users and uses internal extensions only. The main office number is +1 (415) 777-3000 and Alice has extension 234. In this case, Alice’s Line URI field should be tel:+14157773000;ext=234, which uniquely identifies her within the organization. Bob might have extension 567 and his Line URI would be tel:+14157773000;ext=567.

Tip

Using extension-based URIs will prevent an organization from assigning that main line URI to a user because Lync considers the numbers ambiguous. Using the previous example, a receptionist cannot have the URI tel:+14157773000 if Alice has an extension URI based on the same number like tel:+14157773000;ext=234. To work around this issue, use tel:+14157773000;ext=3000 for the main line account, and translate calls to the main line into this number.

This extension-based scenario must also be accounted for within a dial plan. The dial plan within San Francisco must include a normalization rule that takes a three-digit dial into this URI, such as the following rule:

Dial Plan: San Francisco

Name: Three digits to San Francisco

Starting Digits: Blank

Length: Exactly three digits

Digits to Remove: 0

Digits to Add: +14157773000;ext=

Caution

The Normalization Rule Wizard cannot be used to create this type of rule because the ;ext= component is not a valid number. Instead, define the regular expression matching pattern and translation rule manually. In this example, the matching pattern is ^(d{3})$ and the translation rule is +14157773000;ext=$1.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset