Re: Implementation detail about tags.
Shail Bhatnagar <shbhatna@cisco.com> Tue, 16 November 1999 17:37 UTC
Received: from lists.research.bell-labs.com (lists.research.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20691 for <sip-archive@odin.ietf.org>; Tue, 16 Nov 1999 12:37:57 -0500 (EST)
Received: by lists.research.bell-labs.com (Postfix) id D7E9552AB; Tue, 16 Nov 1999 12:35:24 -0500 (EST)
Delivered-To: sip-outgoing-local@paperless.dnrc.bell-labs.com
Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 568F252DB; Tue, 16 Nov 1999 12:35:24 -0500 (EST)
Delivered-To: sip-local@paperless.dnrc.bell-labs.com
Received: from scummy.research.bell-labs.com (research.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id DC97D52AB for <sip@lists.research.bell-labs.com>; Tue, 16 Nov 1999 12:35:05 -0500 (EST)
Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Tue Nov 16 12:34:48 EST 1999
Received: from bounty.cisco.com ([161.44.2.72]) by dusty; Tue Nov 16 12:33:37 EST 1999
Received: from cisco.com (bounty.cisco.com [161.44.2.72]) by bounty.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) with ESMTP id MAA16618; Tue, 16 Nov 1999 12:33:57 -0500 (EST)
Message-ID: <38319585.687FEB01@cisco.com>
Date: Tue, 16 Nov 1999 12:33:57 -0500
From: Shail Bhatnagar <shbhatna@cisco.com>
Organization: CISCO
X-Mailer: Mozilla 4.51C-CISCOENG [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Rick Dean <Rick_Dean@mw.3com.com>
Cc: sip@lists.research.bell-labs.com, Jerry Mahler <Jerry_Mahler@mw.3com.com>
Subject: Re: Implementation detail about tags.
References: <86256827.00608F51.00@mwgate02.mw.3com.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-sip@lists.research.bell-labs.com
Precedence: bulk
Content-Transfer-Encoding: 7bit
Rick Dean wrote: > > Whenever my SIP UA sends an invite, > it includes a "From" tag. This makes the case > of me calling myself through > a proxy easier. Otherwise, matching messages to > call-leg-ends is more painful. I believe this > is allowable within the spec, and you have now > been warned, so don't let it break your stack. > > When responding to an invite, I always include > a "to" tag even though I sometimes don't have to. > Thus, if I ever receive a invite with a "to" tag, yet have > no record of the call, I know the invite is > a re-invite, and either could be for someone else > or is ancient, thus I return "481 Call Leg > does not exist". Not sure what this achieves. When you say "yet have no record of the call", you have probably done some kind of lookup based on Call-ID. It does not optimize your decision to send 481 in any way, does it ? > > Does anyone have a problem with this? > > -- > Rick Dean > 3Com
- Re: Implementation detail about tags. Jonathan Rosenberg
- Re: Implementation detail about tags. Rick Dean
- Re: Implementation detail about tags. Shail Bhatnagar
- Implementation detail about tags. Rick Dean