RE: SIP session liveliness
"Donovan, Steven R." <Steven.R.Donovan@wcom.com> Fri, 29 October 1999 00:39 UTC
Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22785 for <sip-archive@odin.ietf.org>; Thu, 28 Oct 1999 20:39:31 -0400 (EDT)
Received: by lists.research.bell-labs.com (Postfix) id 7961F52DD; Thu, 28 Oct 1999 20:37:24 -0400 (EDT)
Delivered-To: sip-outgoing-local@paperless.dnrc.bell-labs.com
Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id EBB4052E7; Thu, 28 Oct 1999 20:37:23 -0400 (EDT)
Delivered-To: sip-local@paperless.dnrc.bell-labs.com
Received: from scummy.research.bell-labs.com (research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id 2060B52DD for <sip@lists.research.bell-labs.com>; Thu, 28 Oct 1999 20:37:07 -0400 (EDT)
Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Thu Oct 28 20:36:28 EDT 1999
Received: from alpha.mcit.com ([199.249.19.243]) by dusty; Thu Oct 28 20:35:32 EDT 1999
Received: from ndcrelay.mcit.com ([166.37.172.49]) by firewall.mcit.com (PMDF V5.2-32 #38416) with ESMTP id <0FKB000ILKH6HK@firewall.mcit.com> for sip@lists.research.bell-labs.com; Thu, 28 Oct 1999 15:32:20 +0000 (GMT)
Received: from omzexch007.mcit.com (OMZEXCH007.mcit.com [166.37.194.38]) by ndcrelay.mcit.com (8.8.7/) with ESMTP id PAA05355; Thu, 28 Oct 1999 15:29:29 +0000 (GMT)
Received: by omzexch007 with Internet Mail Service (5.5.2571.0) id <VQP893WN>; Thu, 28 Oct 1999 15:30:53 +0000
Content-return: allowed
Date: Thu, 28 Oct 1999 15:30:53 +0000
From: "Donovan, Steven R." <Steven.R.Donovan@wcom.com>
Subject: RE: SIP session liveliness
To: 'Paul Defrain' <defrain@nortelnetworks.com>, "'sip@lists.research.bell-labs.com'" <sip@lists.research.bell-labs.com>
Message-id: <75C79E507864D3118AFC00805FEAB7D8018F32@ripexch001.mcit.com>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2571.0)
Content-type: multipart/alternative; boundary="----_=_NextPart_001_01BF2159.6BF22CE4"
Sender: owner-sip@lists.research.bell-labs.com
Precedence: bulk
Paul, Please see the following draft: http://www.ietf.org/internet-drafts/draft-ietf-sip-session-timer-00.txt <http://www.ietf.org/internet-drafts/draft-ietf-sip-session-timer-00.txt> This is another method for achieving your goal. It is more of a keep-alive mechanism than the ping method you propose. Regards, Steve -----Original Message----- From: Paul Defrain [mailto:defrain@nortelnetworks.com] Sent: Thursday, October 28, 1999 12:10 AM To: 'sip@lists.research.bell-labs.com' Subject: SIP session liveliness All, While we're on the topic of SIP INFO message use, it seems reasonable to assume that we will need to develop a way to ascertain whether or not a SIP session is active. Once a SIP session is established there remains no required "connection" that physically ties the involved parties together. If one party leaves the session and cannot (or does not) contact the other then network resources could be lost (depending on the nature of the application involved in the session). We have identified the need to occasionally "ping" a SIP call based on its call-id (the only persistent piece of data that ultimately identifies an established application session). We foresee the use of the SIP INFO request against the affected call-id along with its 200 response (or other final or non-response in case of error) as an indication of session liveliness. We will use this technique protect (reclaim) limited network resources involved in some sessions established using SIP as the messenger. Has this type of messaging between established sessions been addressed in this or some other forum? Has anyone implemented this sort of functionality in their application(s). __________________________ Paul D. DeFrain IP Services SIP Feature Development ESN 444.7570 (972) 684.7570 defrain@nortelnetworks.com
- SIP session liveliness Paul Defrain
- RE: SIP session liveliness Donovan, Steven R.