Native Registration

Another type of integration used by third-party systems is native registration to Lync Front End pools where the third-party system’s video endpoint registers to Lync just like any other endpoint. In many cases, the third-party endpoint supports dual-registration so that it can maintain a connection to its traditional control system, and simultaneously stay registered to Lync, as depicted in Figure 20.3.

Figure 20.3. Native Lync registration.

The process for this is usually much more straightforward and involves minimal server configuration. A user account is created to represent the third-party endpoint, and the endpoint is then configured with those credentials. The process will vary slightly depending on the vendor, but it generally requires a server name, SIP address, username, and password. The endpoint then uses NTLM authentication to authenticate to the Front End pool, and then behaves like another Lync user.

The advantage to this method is that it provides presence for the endpoint so that other Lync users can tell whether it is available or currently in a call. This solves a number of problems, and results in a much more refined user experience. Seeing “Presence Unknown” for every third-party endpoint is confusing to end users because there is no notification that this is expected, so it appears there is an error with Lync. Having the presence reflected even unidirectionally is a big step forward.