Hi,

I'm trying to modify an INVITE message from a "filter" server application using the managed API (Microsoft.Rtc.Sip)  to automatically add an application context, so the receiver should open the extensibility window pointing to the registry configured app and url.

At the beginning I simply tried to add to the INVITE request content, the session xml string:

<session><application-id>{6989be7c-64f1-4a64-b32f-e700ce0ce5b4}</application-id><additional-properties><entry><name>name</name><value>TEST</value></entry></additional-properties></session>
 

but it was simply ignored, the conversation is started without extension window.

So I performed various other tests changing the ContentType to
"Content-Type: application/ms-session-invite+xml" or playing with other headers but I don't find a working solution.

I've seen the example in the client SDK that initiates a conversation via automation with application context and in that case all is working, but it isn't a solution for me: I cannot have a client application to pilot the Lync client, I would like to intercepit and manipulate the Invite message on the server side.

Could you give me any hint or sample to put this working ? Is it an approach suppported ?

Thanks,

Vincenzo