Who got caldav and carddav push running successful on lion server?

It is already enabled. It was never disabled.

Ok, so next step is to see if calendar server is correctly advertising to the clients that APNS is supported. Point your web browser directly at your calendar server's port, which is either 8008 if SSL is off or 8443 if SSL is on. Append /calendars/users/pandine/ to the URL (replacing "pandine" with an actual username of course) to view the web page corresponding to that user's "calendar home". Search for "push" within the page and you should see something like:

{http://calendarserver.org/ns/}push-transports

<?xml version='1.0' encoding='UTF-8'?>

<push-transports xmlns='http://calendarserver.org/ns/'>

<transport type='APSD'>

<subscription-url>

<href xmlns='DAV:'>http://example.com:8080/subscription</href>

</subscription-url>

<apsbundleid>com.apple.calendar.XServer.def5188c-3ee4-2c91-1015-b0a034d33778</a psbundleid> </transport>

<transport type='XMPP'>

<xmpp-server>example.com:5218</xmpp-server>

<xmpp-uri>xmpp:pubsub.example.com?pubsub;node=/CalDAV/example.com/3D6241DC-5981 -4D87-9B71-672203E81ACB/</xmpp-uri>

</transport>

</push-transports>

If you see the transport type='APSD' section, complete with subscription-url and apsbundleid, then APNS would appear to be properly advertised. That information is used by the client to subscribe to APNS notifications.

Yes I see all that. Opening port 8080 on my firewal was the solution. It works! GREAT! My iOS devices still show "Load" and "Manual" only - but it works with push. 🙂🙂🙂

Thank you.

Ah, that means the clients had not been able to let the APN bridge know they wanted to subscribe to APNS notifications. Glad we got to the bottom of that.

Yes ... and once again thank you for taking time. 🙂

Once I too opened 8080, I started getting push information to the iOS devices as well, but it still only partially works.. Unless I'm confused about how the service is supposed to work.

If i have the iPad on one side, and the macbook on the other side, both have 2 seperate accounts on them. If i invite one person to a meeting, the other gets the meeting in his calendar, but there is no "Invitation" at the top. There are no popups, just the actual meeting shows up as a gray unaccepted meeting.

Is this right?

Spoke too soon. After removing all Profiles from all devices, then rebooting them and the server, un-checkeing the APNS and re-checking it back in, then re-adding all services, everything started to work perfectly!

Thanks for your help morgen, even if it wasn't for me 😝

So Draekz, the firewall blocking 8080 was your issue as well? On my server under System Preferences > Security & Privacy > Firewall > Advanced... I have "Automatically allowed signed software to receive incoming connections" checked. Are you using "Block all incoming connections"? Just trying to figure out what the difference is here...

I was referring to my hardware firewall not OS firewall.

With iOS5.1 Beta 2 the sync settings for calendars offer 'Push' now. For contacts there are still the options 'Load' and 'Manual' only.

Regards,

Thomas

My push-transports and pushkey both show (no-value). Any ideas?

Well, let's start with whether calendar server has been instructed to enable push. Run this command in Terminal:

sudo serveradmin settings calendar:Notifications:Services:XMPPNotifier:Enabled

You should see:

calendar:Notifications:Services:XMPPNotifier:Enabled = yes

Next, let's see if the XMPP (Jabber) notification daemon is up by running this command in Terminal:

ps aux | grep jabberd_notification

You should see things like:

_jabber 147 0.0 0.1 2449564 6032 ?? S Tue08PM 0:04.01 /usr/libexec/jabberd/s2s -c /etc/jabberd_notification/s2s.xml

_jabber 146 0.0 0.1 2449536 6036 ?? S Tue08PM 0:04.87 /usr/libexec/jabberd/c2s -c /etc/jabberd_notification/c2s.xml

_jabber 144 0.0 0.1 2437464 5308 ?? S Tue08PM 0:03.30 /usr/libexec/jabberd/router -c /etc/jabberd_notification/router.xml

_jabber 143 0.0 0.2 2450116 6316 ?? S Tue08PM 0:03.48 /usr/libexec/jabberd/sm -c /etc/jabberd_notification/sm.xml

_jabber 67 0.0 0.1 2438536 4376 ?? Ss Tue08PM 0:00.07 perl -w -x /usr/libexec/jabberd/jabberd -c /etc/jabberd_notification/jabberd.cfg

root 25427 0.0 0.0 2425480 184 s002 R+ 9:23AM 0:00.00 egrep jabberd_notification

Ok, I get:

calendar:Notifications:Services:XMPPNotifier:Enabled = yes

and:

Looks pretty much like yours...

Ok, now do calendar server and notification server agree on the XMPP port #...

sudo serveradmin settings calendar:Notifications:Services:XMPPNotifier:Port

...should give you something like 5218

Now see if jabberd_notification is listening on that port and whether there is an established connect between calendar and notification, e.g.

sudo lsof -Pi | grep 5218

c2s 146 _jabber 7u IPv6 0xffffff800becf440 0t0 TCP *:5218 (LISTEN)

c2s 146 _jabber 8u IPv6 0xffffff800e52fe80 0t0 TCP example.com:5218->example.com:49188 (ESTABLISHED)

Python 267 _calendar 7u IPv4 0xffffff800f874500 0t0 TCP example.com:49188->example.com:5218 (ESTABLISHED)

Also, check /var/log/caldavd/error.log for any notification error messages.