XMPP is no longer supported by Calendar Server as a push notification transport. The supported options are APNS (uses Apple’s push cloud, requires APNS certificates generated by Apple to be installed on the server, only works for Apple clients, does not require an Apple-branded server) and AMP. The AMP transport is simple enough to allow interested integrators to write their own endpoints that act on push notifications (e.g. web app / groupware / middleware), but is generally not intended for wide-spread *client side* use given the requirement of maintaining a tcp connection to receive pushes. (of course this requirement also exists for APNS, however the cost is fixed since a single connection is used for all APNS pushes to all apps on the client).

On Jan 1, 2015, at 1:17 AM, Gaurav Jain <monkeyfdude@gmail.com> wrote:

I am trying to get push notifications working. I looked at the following but could not understand how to use these

Is there a documentation to get started or understand the above settings?

    <key>Notifications</key>
    <dict>
      
      <key>CoalesceSeconds</key>
      <integer>3</integer>

      <key>Services</key>
      <dict>
        <key>XMPPNotifier</key>
        <dict>
          
          <key>Service</key>
          <string>twistedcaldav.notify.XMPPNotifierService</string>
          <key>Enabled</key>
          <false/>

          
          <key>Host</key>
          <string>xmpp.host.name</string>
          <key>Port</key>
          <integer>5222</integer>

          
          <key>JID</key>
          <string>jid@xmpp.host.name/resource</string>
          <key>Password</key>
          <string>password_goes_here</string>

          
          <key>ServiceAddress</key>
          <string>pubsub.xmpp.host.name</string>
        </dict>
      </dict>
    </dict>

Regards,
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/calendarserver-users