Thanks Derek,
I was looking at code in the
ClientInviteSession::dispatch that has a case for a 100 response in the INITIAL
state - right now it only calls onNewSession. - But I just
noticed that DialogUsageManager::processResponse just ignores 100 responses -
so that code is never actually run.
I think providing some kind of application
notification is useful. I like onTrying ... or just sticking with the
onProvisional callback makes sense too.
Scott
From: Derek MacDonald
[mailto:Derek@xxxxxxxx]
Sent: Wednesday, July 14, 2004
3:36 PM
To: 'Scott Godin';
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate] DUM and
Provisional Responses...
Well, you don't have a Dialog yet, so you
can't make a ClientInviteSession. Jason and I talked about adding a
handler for 100's that would return the appdialogSet as a parameter.
virtual void onTrying(AppDialogSetHandle,
const SipMessage&)=0;
I suppose this could be put in
InviteSessionHandler, although there isn't a session yet. The code that
calls this would be in DialogSet::dispatch.
-----Original Message-----
From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of Scott Godin
Sent: Wednesday, July 14, 2004
12:22 PM
To:
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] DUM and
Provisional Responses...
I would like to change the DUM functionality about a little
(ClientInviteSession) so that the onProvisional handler is called even when a
100 response is received from the far end. Currently it only calls onProvisional
if the response is greater than 100 and less than 200.
Are there any issues with this?
Scott
Godin
Research
and Development
Computer
Talk Technology
slgodin@xxxxxxxxxxxx
905-882-5000
and 'Say my name' or x127