| < Previous by Date | Date Index | Next by Date > |
| Thread Index | Next in Thread > |
|
For an new dialog request, a failure in sending a MESSAGE is
handled using virtual void ClientPagerMessageHandler::onFailure
(ClientPagerMessageHandle, const SipMessage &status, std::auto_ptr<
Contents > contents)=0 This method helpfully includes the “contents” so
that important details like the body, mimeType can be found. However, an indialog MESSAGE failure for an InviteSession
does NOT include the body virtual void InviteSessionHandler::onMessageFailure
(InviteSessionHandle, const SipMessage &msg)=0 Is there a normal way that we can find the correct request
that generated this Failure without keeping a list of requests in our application
layer? -Aron --------------------------------------------- Aron Rosenberg Founder and CTO SightSpeed - http://www.sightspeed.com/ 918 Parker St, Suite A14 Berkeley, CA 94710 Email: arosenberg@xxxxxxxxxxxxxx Phone: 510-665-2920 Cell: 510-847-7389 Fax: 510-649-9569 SightSpeed Video Link: http://aron.sightspeed.com |