Posts

Showing posts with the label Dial Plan

Dialplan normalization with extension number if user do not have a DDI

If we only have internal extensions and the URI will look like this: +4989123400;ext123 we have several point we need taking care about: - incoming calls shall be addressed via Exchange Auto Attendant - internal call now need to be normalized including the users extension - in some circumstances, we have assigned multiple DID number including the head number. if so we need the incoming normalization, analog to the internal calling normalization Confused finally? Don't worry, it really looks simple: Say our Head Number is: +4989123400 and we have extension from ;ext=01 until ext=99, the normalization rule will look like: If the Exchange Auto Attendant has also an extension, we need to have an incoming normalization rule on the trunk or gateway: Exchange AA: +4989123400;ext=99 Pattern to match: ^(\+4989123400)$ Translation rule: $1;ext=99 the internal assigned phone number has the said range (01-98), so a users phone number looks like: a) tel:54;phone-context=Si...

Demystify Lync Enterprise Voice Phone Numbers and Extension

Image
Demystify Lync Enterprise Voice Phone Numbers and Extension Download the article as PDF: click here Valid Phone Numbers based on RFC 3966 Lync Server 2013 and his related earlier products (Lync 2010 and OCS) fully depend and follow the given requirements of RFC 3966 With this, we know what the goals are we need to fulfill, in a short sentence, we need to get all numbers translated to an E.164 format. Simply said, E.164 represent an international number format, including the “+” sign at beginning. Example E.164 Phone Numbers: +498912345678 (e.g. Munich, Germany) +6038383123 (e.g. Kuala Lumpur, Malaysia) E.164 number a unique worldwide, therefor they are capable addressing a single connection point. As we understood now, it is important to follow this requirements. Nevertheless, there are non-compliance changes local telephone companies apply. This we need to keep in mind, while we do planning’s for our Lync international connection points (Lync...