RE: [reSIProcate] using InviteSessionHandler callbacks with a singleSIP message
Anyone want to take a crack at this question :-)?
Thanks,
-Justin
-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Justin
Matthews
Sent: Friday, January 28, 2005 12:21 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] using InviteSessionHandler callbacks with a singleSIP
message
Hello,
When handling a sequence of DUM InviteSessionHandler callbacks for a
single SIP message, for example see the attached file: INVITE,
onNewSession(), onOffer(), I want to know when the DUM is done handling the
incoming (or outgoing for other scenarios) message. In the attached
scenario the onNewSession() is called and then returns and at that point I
don't know if I should then wait for SDP or not. My first thought was to
just check for SDP contents within the current message to see whether or not
to wait for the SDP, but am unsure this will work because there is other
logic surrounding the call (in the DUM code) to onOffer(). My next thought
was to keep the new session information around after receiving the
onNewSession() call and then wait until process() returns and at that point
go through any sessions that I have and process them. I have only run
through this scenario and am new to the stack so I haven't looked at other
scenarios, but am guessing that there are others cases where a similar issue
will present itself. Would some kind of onMessageProcessEnd() or equivalent
make sense. How is the InviteSessionHandler() intended to be used?
Thanks,
-Justin