Determine message origin in federated networks (FederationEdge sample)

Lync 2013

Learn about the Microsoft Lync Server 2013 SDK FederationEdge sample application.

Last modified: August 16, 2013

Applies to: Lync 2013 | Lync Server 2013

Note Note

By default, the FederationEdge application is copied to the %progfile%\Microsoft Lync Server 2013\SDK\Samples\FederationEdge folder. FederationEdge and related code samples can also be downloaded from the MSDN Code Gallery.

The FederationEdge application that is distributed with the Lync Server 2013 SDK shows how to use a script-only SIP application to determine the origin of a message by using the MessageOrigin enumeration against the Origin property on an incoming message. After displaying the original source of the message in the ApiLogger utility, it routes the message back to the server without any updates.

If necessary, copy the %progfile%\Microsoft Lync Server 2013\SDK\Samples\FederationEdge folder to a Microsoft Lync Server 2013 computer on which the application runs.

To run the application

  1. Log on to the Lync Server 2013 RTC Server Applications local security group account.

  2. Copy the application manifest (.am) and the configuration files to the %progfile%\Microsoft Lync Server 2013\Server\Core folder.

  3. Register the application by running the following commands in a Lync Server Management Shell window.

    Note Note

    <lync.Server.Fdqn> is the placeholder for the fully qualified domain name for the test server. You may have to change the priority value so that it is larger than the UserServices application value.

    new-csServerApplication -uri "" -identity "service:registrar:<lync.Server.Fdqn>/FederationEdge" -critical $false -priority 6 -scriptname -enabled $true

  4. Send IM messages from a SIP client to another user from various user accounts in different networks.