| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
|
Re-tranmissions are handled by
the stack layer – you won’t have access to that from dum (the stack
can run in it’s own thread). There is a request map in the dialog
class (index by CSeq) and use for auth logic – but is cleared as soon as
the response comes in. I suppose we could delay it’s cleanup until
after the response has been dispatched to the usages, then offer an accessor
for it, but I think it also makes sense to just implement this in the
application layer. From: Aron Rosenberg
[mailto:arosenberg@xxxxxxxxxxxxxx] If we wanted to patch
resiprocate for this functionality is the original outbound message stored
somewhere in the transaction, Dialog or DialogSet layer? My hunch is that it
must be so that retransmissions can be sent. -Aron From: Scott Godin
[mailto:slgodin@xxxxxxxxxxxx] There is currently no way to get
this, you will need to keep a list of requests in the application layer. Scott From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxx]
On Behalf Of Aron Rosenberg For a 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 |