Re: [reSIProcate-users] Implementing DUM UAS for Session RecordingProtocol RFC 7866 with resiprocate - UPDATE method

[Scott Godin <slgodin@xxxxxxxxx>]

Hi Andriy,

InviteSession::provideAnswer takes a generic Contents, not an SdpContents so you should be able to pass any body type.  

virtual void provideAnswer(const Contents& answer);

Scott

On Fri, Jul 6, 2018 at 4:27 AM Andrew B <andrebroz@xxxxxxxxx> wrote:

Hello Scott,

Thank you very much for your reply!

I use the switch and receive the correct contents in onOffer. The problem is with sending 200 OK back without sending SDP. I tried using provideAnswer, but it requires supplying SDP.

I wish you a pleasant traveling!

Thank you very much for your help!

Andriy

---

From: slgodin@xxxxxxxxx
Sent: ‎06/‎07/‎2018 00:52
To: Andriy Brozgol
Cc: resiprocate-users@xxxxxxxxxxxxxxx
Subject: Re: [reSIProcate-users] Implementing DUM UAS for Session RecordingProtocol RFC 7866 with resiprocate - UPDATE method

Hi Andriy,

I’m traveling right now, so I can’t look up the specific answer, but there is a switch somewhere in the InviteSessionHandler to tell the callbacks to pass a generic contents to you instead of SDP.

Scott

Sent from my iPhone

> On Jul 5, 2018, at 7:08 PM, Andriy Brozgol <andrebroz@xxxxxxxxx> wrote:
>
> Hello All,
>
> I am using resiprocate DUM for implementing UAS of recording server.
>
> I ran into difficulties when implementing UPDATE support. Session Recording Client (SRC) can send UPDATE with recording session metadata contents to Session Recording Server (SRS). The UPDATE request does not contain SDP, just recording session metadata. I receive the contents in onOffer but I do not understand how can I send 200 OK without sending SDP back. I tried to use provideAnswer, but it sends SDP.
>
> Thank you very much in advance,
>
> Andriy
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/