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
I agree (Answer B).
You need to create a SIP trunk and a SIP route pattern between Mediation server and CUCM.
sorry, I said A.
Agree
SIP UIR
Lync Error When Using E.164 Numbers
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/lync_integration/9_0_1/CUP0_BK_CE1362F3_00_lync-integration-guide-90/CUP0_BK_CE1362F3_00_lync-integration-guide-90_chapter_01010.html
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.
Why? The error can be avoided
SIP URI !!!!