Re: [reSIProcate] What is status of first InviteSessionHandle ifonNewSession(ClientInviteSessionHandle) fires a second time?

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

In this case we shouldn't be creating a dialog - we should instead be calling DialogSetHandler->onNonDialogCreatingProvisional() as we do when the 180 doesn't contain a Contact header.  I can commit a fix for this later this week.

 

Scott

---

From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx on behalf of Kobi Eshun
Sent: Wed 11/29/2006 1:20 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] What is status of first InviteSessionHandle ifonNewSession(ClientInviteSessionHandle) fires a second time?

Hi,

Please consider the following scenario:

- my reSIP app sends out INVITE, and receives a 18x response that has no To tag

- onNewSession(ClientInviteSessionHandle cis, ...) UAC callback fires

- my app caches CIS, and also caches InviteSessionHandle learned via CIS->getSessionHandle()

- my app receives 200 response with a To tag

- onNewSession() fires again with different  ClientInviteSession and InviteSession handles.

Leaving aside for the moment  the question of whether the far-end behavior is 3261 compliant:

Q1 - what should my app do with the first set of handles - are they simply obsoleted?

Q2 - Is it an error to continue using them?

Q3 - How do they get cleaned up?

Thanks,

--

Kobi Eshun

Senior Architect, SightSpeed, Inc.

918 Parker Street, Suite A14

Berkeley, CA 94710

+1.415.713.8431 (m)

+1.510.649.9569 (f)

kobi@xxxxxxxxxxxxxx