Publishing Presence with Routing Information kills team and delegate list

I want to change the routing/forwarding settings of a user on behalf of a UserEndpoint and publishing presence with routing information like the following:

<routing xmlns="http://schemas.microsoft.com/02/2006/sip/routing" name="rtcdefault" version="2" minSupportedClientVersion="4.0.0.0">
    <preamble>
      <flags name="clientflags" value="enablecf forward_immediate"/>
      <wait name="total" seconds="20"/>
      <list name="forwardto">
        <target uri="sip:user@domain.com"/>
      </list>
    </preamble>
  </routing>

I publish it with the following peace of code and at first view everything looks as it works like expected.

PresenceCategoryWithMetaData pcm = CreatePresenceCategoryInstance("routing", 0, 0, presenceNoteValue);
            PresenceCategoryWithMetaData[] categories = new PresenceCategoryWithMetaData[1];
            categories[0] = pcm;
            endpoint.LocalOwnerPresence.BeginPublishPresence(categories, null, null);

But if I check all "Call Forwarding" settings in the client these things are broken:

• the team group is empty
• the "recieve call"-checkbox of my delgate is unchecked

Can anyone tell me why this happens and has an idea how to fix this? My idea is to first save these configuations and add it to the published routing settings with a team and delegate list. Can anyone tell me, how I can get the team or delegate information for a user?

Thank you for every statement.