Configuring for Push Notifications
Topic Last Modified: 2012-01-28
Push notifications, in the form of badges, icons, or alerts, can be sent to a mobile device even when the mobile application is inactive. Push notifications notify a user of events such as a new or missed IM invitation, missed calls, and voice mail. The Microsoft Lync Server 2010 Mobility Service sends the notifications to the cloud-based Microsoft Lync Server 2010 Push Notification Service, which then sends the notifications to the Apple Push Notification Service (APNS) or the Microsoft Push Notification Service (MPNS).
Configure your topology to support push notifications by doing the following:
If your environment has a Lync Server 2010 Edge Server, you need to add a new hosting provider, Microsoft Lync Online, and then set up hosting provider federation between your organization and Lync Online.
If your environment has a Office Communications Server 2007 R2 Edge Server, you need to set up direct SIP federation with push.lync.com.
Note
Push.lync.com is a Microsoft Office 365 domain for the Lync Server 2010 Push Notification Service.
To enable push notifications, you need to run the Set-CsPushNotificationConfiguration cmdlet. By default, push notifications are turned off.
Test the federation configuration and push notifications.
To configure for push notifications with Lync Server 2010 Edge Server
Log on to a computer where Lync Server Management Shell and Ocscore are installed as a member of the RtcUniversalServerAdmins group.
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
Add a Lync Server online hosting provider. At the command line, type:
New-CsHostingProvider -Identity <unique identifier for Lync Online hosting provider> -Enabled $True -ProxyFqdn <FQDN for the Access Server used by the hosting provider> -VerificationLevel UseSourceVerification
For example:
New-CsHostingProvider -Identity "LyncOnline" -Enabled $True -ProxyFqdn "sipfed.online.lync.com" -VerificationLevel UseSourceVerification
Note
You cannot have more than one federation relationship with a single hosting provider. That is, if you have already set up a hosting provider that has a federation relationship with sipfed.online.lync.com, do not add another hosting provider for it, even if the identity of the hosting provider is something other than LyncOnline.
Set up hosting provider federation between your organization and the Push Notification Service at Lync Online. At the command line, type:
New-CsAllowedDomain -Identity "push.lync.com"
To configure for push notifications with Office Communications Server 2007 R2 Edge Server
Log on to the Edge Server as a member of the RtcUniversalServerAdmins group.
Click Start, click All Programs, click Administrative Tools, and then click Computer Management.
In the console tree, expand Services and Applications, right-click Microsoft Office Communications Server 2007 R2, and then click Properties.
On the Allow tab, click Add.
In the Add Federated Partner dialog box, do the following:
In Federated partner domain name, type push.lync.com.
In Federated partner Access Edge Server, type sipfed.online.lync.com.
Click OK.
To enable push notifications
Log on to a computer where Lync Server Management Shell and Ocscore are installed as a member of the CsAdministrator role.
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
Enable push notifications. At the command line, type:
Set-CsPushNotificationConfiguration -EnableApplePushNotificationService $True -EnableMicrosoftPushNotificationService $True
Enable federation. At the command line, type:
Set-CsAccessEdgeConfiguration -AllowFederatedUsers $True
To test federation and push notifications
Log on to a computer where Lync Server Management Shell and Ocscore are installed as a member of the CsAdministrator role.
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
-
Note
The Test-CsFederatedPartner synthetic transaction provides a means to test and confirm that the configured federation is working in an expected manner. The following examples show how to execute the Test-CsFederatedPartner for a Lync Server 2010 Edge Server and an Office Communications Server 2007 R2 Edge Server.
Test the federation configuration for Lync Server 2010 Edge Server. At the command line, type:
Test-CsFederatedPartner -TargetFqdn <internal interface FQDN of Edge server used for federated SIP traffic> -Domain <FQDN of federated domain> -ProxyFqdn <FQDN of the Access Edge server used by the federated organization>
For example:
Test-CsFederatedPartner -TargetFqdn internaledge.contoso.com -Domain push.lync.com -ProxyFqdn sipfed.online.lync.com
Test the federation configuration for Office Communications Server 2007 R2 Edge Server. At the command line, type:
Test-CsFederatedPartner -TargetFqdn <internal interface FQDN of Edge server used for federated SIP traffic> -Domain <FQDN of federated domain>
For example:
Test-CsFederatedPartner -TargetFqdn internaledge.contoso.com -Domain push.lync.com
Test push notifications. At the command line, type:
Test-CsMcxPushNotification -AccessEdgeFqdn <Access Edge service FQDN>
For example:
Test-CsMcxPushNotification -AccessEdgeFqdn accessproxy.contoso.com