< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
Hi, Data* txt = new Data(sdpString.c_str()); HeaderFieldValue* hfv = new HeaderFieldValue(txt->data(), (unsigned int) txt->size()); Mime type("application", "sdp"); SdpContents sdp((const HeaderFieldValue&) *hfv, (const Mime&) type); I know there is a
MultipartAlternativeContents but I don’t know how to use it, specially what would be the HeaderFieldValue that I would pass in the constructor. Is it possible to build such message using Parts() from two SdpContents? Any help is appreciated.
Thanks, Diego From: Diego Carvalho Domingos
This is exactly what I wanted. Thank you very much. Regards, From:
slgodin@xxxxxxxxx [mailto:slgodin@xxxxxxxxx]
On Behalf Of Scott Godin There is a setting on the InviteSessionHandler constructor that will tell DUM to provide you with the entire body back instead of just Sdp bodies. Check out the following comment in InviteSessionHandler.hxx /** Base class for class InviteSessionHandler. The application must override this class and provide an imlementation of the handlers below. The class must then be set as an invite session handler on dum (DialogUsageManager::setInviteSessionHandler()). If you wish to handle invite session offer/answers using generic contents instead of SDP, then construct this class with a bool argument of true, and be sure to add implementations of all of the handlers below that take a Contents parameter type (ie. onEarlyMedia, onOffer, onAnswer, and onRemoteAnswerChanged). Overriding these methods will cause their SdpContent counterparts to not be called. You can then provide a basic empty body implementation of these SdpContent versions of the callbacks. Example handler for generic (non-sdp only) invite sessions: class MyInviteSessionHandler : public InviteSessionHandler { MyInviteSessionHandler() : InviteSessionHandler(true) {}; ... virtual void onOffer(InviteSessionHandle, const SipMessage& msg, const SdpContents&) {} // No body required virtual void onOffer(InviteSessionHandle, const SipMessage& msg, const Contents&) { // Add handler body here } ... }; */ Scott On Tue, May 17, 2016 at 10:02 AM, Diego Carvalho Domingos <ddomingos@xxxxxxxxxxxxxxx> wrote:
|