Re: [Sip] Multiple registration using single UA
Paul Kyzivat <pkyzivat@cisco.com> Wed, 06 April 2011 22:15 UTC
Return-Path: <pkyzivat@cisco.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3F9F3A692F for <sip@core3.amsl.com>; Wed, 6 Apr 2011 15:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bEteEq--9d2Y for <sip@core3.amsl.com>; Wed, 6 Apr 2011 15:15:45 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 27EE63A67E9 for <sip@ietf.org>; Wed, 6 Apr 2011 15:15:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=1094; q=dns/txt; s=iport; t=1302128249; x=1303337849; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=E4MHCkrC3YjA3AZaVxkRoq50cRz2UzFLnpSbFIe+XfM=; b=QTSs20tmA5XVrO/stFo3yCbXaoTEEj+UKD5UcPLssReyG93RWPQsbnph TZshEU7XZDto5oUzPEYeIQLWm2Xk+zAIiI7PrBYvblavUzjV/1unymc+7 JMZLW8rQOxj7K1Vl4N8l5kTO10UGn6TjL8BhmaesOgJwhBopVVXXKOlQw o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYHAAzmnE2rRDoI/2dsb2JhbACYco0Nd4h5nhucZIVsBI08g2M
X-IronPort-AV: E=Sophos;i="4.63,312,1299456000"; d="scan'208";a="290830134"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by sj-iport-3.cisco.com with ESMTP; 06 Apr 2011 22:17:29 +0000
Received: from [10.86.240.127] (che-vpn-cluster-1-127.cisco.com [10.86.240.127]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p36MHSKx031678 for <sip@ietf.org>; Wed, 6 Apr 2011 22:17:28 GMT
Message-ID: <4D9CE677.1060009@cisco.com>
Date: Wed, 06 Apr 2011 18:17:27 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: sip@ietf.org
References: <BANLkTimjjn16x4x1Cih4N9YcF2QMvO807Q@mail.gmail.com>
In-Reply-To: <BANLkTimjjn16x4x1Cih4N9YcF2QMvO807Q@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Sip] Multiple registration using single UA
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2011 22:15:46 -0000
On 4/4/2011 2:10 AM, E D wrote: > If I wanted to register two distinct numbers through a single UA Device > say 34111111 and 34111112 through one/single UA Device. > Should I expect the "Call-ID" to be Unique or Identical? > RFC3261 seem to imply that the only the "SIP Tag" needs to be unique > for the SIP Server or Registrar to > understand that both Numbers are being registered from one device only. > How could the SIP Server or > Registrar verify that these two numbers are in fact originating from the > same Device? Why would a registrar want/need to determine this? Thanks, Paul > Thanks in advance > > > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is essentially closed and only used for finishing old business. > Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP implementation. > Use dispatch@ietf.org for new developments on the application of sip. > Use sipcore@ietf.org for issues related to maintenance of the core SIP specifications.