Which dial plan type should the engineer recommend?

An engineer is designing a new dial plan for a customer that has offices in several countries on four continents around the world. This client also wants to integrate with a Microsoft Lync backend.
Which dial plan type should the engineer recommend?
A. SIP URI
B. TEHO
C. E.164
D. H.323

cisco-exams

6 thoughts on “Which dial plan type should the engineer recommend?

  1. I agree (Answer B).
    You need to create a SIP trunk and a SIP route pattern between Mediation server and CUCM.

    1. E.164
      Phone Numbers within Lync

      Like your phone numbers within Active Directory, your phone numbers (or LineURI’s) within Lync will also be in E.164 format. The difference is, there is no option to not have them in this format. So your LineURI should be formatted as:

      +;ext=

      One common mistake is organizations will leave the extension field off because they believe they have no non direct inward dial (DID) numbers. Although this format would work:

      +19528310888

      Leaving the ;ext= off of the phone number can cause some unexpected behaviors during your deployment.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.