List of Dial Plan Regular Expressions

^	match the start	$	match the end
\d	match any digit	\d*	0 or more digits
\d{5}	any 5 digits	[135]	1, 3, or 5
(13)|(17)	13 or 17	[1..5]	1 through 5
(…)	“captures” the enclosed characters for referring to them in the result as $1, $2, $3, etc.

Examples

National dialing:

                 ^([2-9]\d\d[2-9]\d{6})$ → +1$1 (NANP)

                 ^0(\d{10}) → +44$1 (UK)

Include national and international dialing prefixes:

                ^011(\d*) → +$1

Extension range (e.g. 15xx-35xx):

                 ^((1[5-9]|2[0-9]|3[0-5])\d{2})$ → +1206555$1

Avoid expressions that make the first digit optional:

                ^9?([2-9]\d\d[2-9]\d{6})$

Error: "The parameter is incorrect - starttime" error when you run Search-CsClsLogging in Lync Server 2013

When you run the "Search-CsClsLogging cmdlet" from Microsoft Lync Server 2013 Management Shell on a computer, you receive the following error message:

Starting search against 1 computers
Failed on 1 agents
Agent - lync.domain.com, Reason - Error code - 87, Message - The parameter is incorrect -    starttime.

Note: This issue occurs because the date and time format setting on the computer is not set to English (United States).

The work around for this issue is to set the date and time format setting to English (United States):

1. Open Control Panel, and then open Region and Language.
2. In the Formats tab, change the format to English (United States).
3. Restart Lync Server Management Shell, and then run the get-date –format g cmdlet to verify that the change has taken effect.

Windows Store Lync App

Microsoft recently released a version of the Lync client for Windows 8 and Windows tablets such as the new Microsoft Surface.  The new client version is officially called “Windows Store Lync App” (a.k.a. Lync MX, Lync RT, Win 8 Lync App, and Lync Metro). This version is optimized for touchscreen and runs on any flavor of Windows 8.  It does not run on Windows 7. The Windows Store Lync App can connect to Lync Sever 2010, Lync Server 2013, and Lync Online in Office 365

http://blog.insidelync.com/2012/11/basic-tips-for-the-windows-store-lync-app

http://blogs.technet.com/b/nexthop/archive/2012/11/09/understanding-lync-server-autodiscover-to-support-the-lync-windows-store-app.aspx

Lync 2013 Quality of Service (QoS)

Lync Server has been designed to work without any Quality of Service (QoS) framework. It can be deployed with QoS implemented by using Differentiated Services (DiffServ). In Lync Server, DSCP marking can be enabled by using Windows policy-based QoS to specify port ranges for each communication type. By default, policy-based QoS and DSCP marking are disabled.The marked packets can then be recognized by network entities (end systems and routers if enabled to do so) to manage the media traffic according to the QoS priorities. The QoS marking is applied to all media ports and regardless of whether the audio/video/Application Sharing / File Transfer traffic is delivered over Real-Time Protocol (RTP; see IETF RFC 3350) or Secure Real-Time Protocol (SRTP; see IETF RFC 3711). To support the QoS environment, endpoints are configured to mark the IP traffic, thereby conveying the priority of the real-time audio and video IP traffic according to well-established classes of services that are designed to protect the real-time communication traffic from other asynchronous traffic in the IP network, including instant messaging (IM), application sharing data, and file downloads. These markings can be changed to map to different classes of services as an enterprise wants.

Also note that for clients that run on operating systems other than Windows 7 and Windows Vista, policy-based QoS is not supported.

“Failed while updating destination pool”

Error : “Failed while updating destination pool”, when attempting to migrate a user from a Lync Server 2010 pool to Lync Server 2013 pool .

This all too common error has been around since OCS 2007.  The reason why you are unable to move the user is because of the inheritable permissions on the user’s account object.  Open up adsiedit.msc, navigate to the user’s account, open up the properties and review the Advanced Security Settings of the object. Uncheck “Include inheritable permissions from this object” s parent setting for the user account.

Lync 2013 Certificate type: "OAuthTokenIssuer"

When requesting certificates in a Lync 2013 you will notice a new certificate type called “OAuthTokenIssuer”. OAuth stands for “Open Authentication” and is a protocol for server-to-server authentication and authorization. OAuthTokenIssuer certificate is a global certificate. Exchange 2013, SharePoint Server, and Lync Server 2013 support server-to-server authentication.  If you are not running one of these servers then you will not be able to fully implement OAuth authentication. Authentication and authorization is based on the exchange of security tokens; these tokens grant access to a specific set of resources for a specific amount of time. Lync Server 2013 must be able to securely communicate with other applications and server products. You can configure Lync Server 2013 so that contact data is stored in Exchange Server 2013; however, this can only be done if Lync Server and Exchange are able to securely communicate with one another. Although it's possible to use one authentication mechanism for Lync-to-Exchange communication and a separate mechanism for Lync-to-SharePoint communication, a better and more efficient approach is to use a standardized method for all server-to-server authentication and authorization. When you assign this OAuth certificate, it is replicated via the CMS and is assigned to all of the Lync Server 2013 servers that require OAuth. So when requesting the OAuthTokenIssuer certificate in Lync Server 2013, you will only request it once and CMS will replicate it to the other servers

To determine whether or not a server-to-server authentication certificate has already been assigned to Microsoft Lync Server 2013, run the following command from the Lync Server 2013 Management Shell: Get-CsCertificate -Type OAuthTokenIssuer

If no certificate information is returned you must assign a token issuer certificate before you can use server-to-server authentication. Any Lync Server 2013 certificate can be used as your OAuthTokenIssuer certificate: For example, your Lync Server 2013 default certificate can also be used as the OAuthTokenIssuer certificate. The OAUthTokenIssuer certificate can also be any Web server certificate that includes the name of your SIP domain in the Subject field. The primary two requirements for the certificate used for server-to-server authentication are these: 

1. The same certificate must be configured as the OAuthTokenIssuer certificate on all of your Front End Servers
2. The certificate must be at least 2048 bits.

If you do not have a certificate that can be used for server-to-server authentication you can obtain a new certificate, import the new certificate, and then use that certificate for server-to-server authentication.

Ref: http://technet.microsoft.com/en-us/library/jj205253
http://technet.microsoft.com/en-us/library/jj204817%28v=ocs.15%29

ACL Error when Publishing Lync 2013 Topology

When Publishing Lync 2013 Topology you may come across this permission error.
 
Error Description in Log file:

Failed Adding “Access Write” permission for “RTCHS Universal Services” on “share”. Access control list (ACL) might fail on UNIX files shares. Refer to the deployment guide to manually set the ACLs in the file share.

This is due to a permission's error on your LyncShare. The fix is to give Full Control access on the “Share tab”, not the “Security” tab.

1. Right Click your Lync File Share
2. Select Properties
3. Go To Sharing Tab
4. Select Advanced Sharing
5. Select Permissions
6. Add Full/Change/Read permissions to the follow Groups:
7. RTCHS Universal Services
8. RTC Component Universal Services
9. RTC Universal Server Admins
10. RTC Universal Config Replicator
11. Click OK
12. Republish Topology

The New Lync Connectivity Analyzer

Here is the new Microsoft Lync Connectivity Analyzer. This tool will help Lync administrators determine whether the deployment and configuration of their on-premises Lync Server environment meets the requirements to support connections from Lync Windows Store app and Lync mobile apps. Lync Connectivity Analyzer will help you test and troubleshoot connections to your on-premises servers from these apps. You can perform the connection tests over your internal network or over an external network that connects to Lync Server. Lync Connectivity Analyzer provides a report with detailed information about each connection step, with links to online documentation when a test fails.

To obtain the Lync Connectivity Analyzer, visit the Microsoft Download Center:

• Microsoft Lync Connectivity Analyzer (32 Bit)
• Microsoft Lync Connectivity Analyzer (64 Bit)

New set of Visio stencils for Exchange, Lync and SharePoint 2013

The much anticipated release of the new Visio stencils are here. I will also post the link to the downloads on my "Links" page. This download contains more than 300 icons to help you create visual representations of Microsoft Office or Microsoft Office 365 deployments including Microsoft Exchange Server 2013, Microsoft Lync Server 2013, and Microsoft SharePoint Server 2013.

SharePoint, Exchange, Lync and Office 2013 Link to download
Exchange 2013 - Link to download

Lync 2013 call forwarding - Issues with Call Forwarding

Are you in the middle of deploying a new SIP trunk deployment and having troubles with Lync 2013 call forwarding. The common problem is not allowing you to forward any calls to your cellphone, use call forwarding or simring. The first item you want to check is that EnableSipRefer is set to $False cmdlet: CsTrunkConfiguration -EnableReferSupport $False.