Re: [Sip] Multiple registration using single UA
Brett Tate <brett@broadsoft.com> Mon, 04 April 2011 13:15 UTC
Return-Path: <brett@broadsoft.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 A83433A693B for <sip@core3.amsl.com>; Mon, 4 Apr 2011 06:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level:
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311]
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 hB7e-GaYbkgG for <sip@core3.amsl.com>; Mon, 4 Apr 2011 06:15:46 -0700 (PDT)
Received: from smtp-out01.seaservers.net (smtpedge.partnerhosted.com [173.225.22.21]) by core3.amsl.com (Postfix) with ESMTP id 3B9733A67DF for <sip@ietf.org>; Mon, 4 Apr 2011 06:15:46 -0700 (PDT)
Received: from EXMBXCLUS01.citservers.local ([fe80:0000:0000:0000:a488:d1ec:167.6.58.109]) by casumhub01.citservers.local ([172.16.98.57]) with mapi; Mon, 4 Apr 2011 06:17:28 -0700
From: Brett Tate <brett@broadsoft.com>
To: E D <storedge1@gmail.com>, "sip@ietf.org" <sip@ietf.org>
Date: Mon, 04 Apr 2011 06:17:24 -0700
Thread-Topic: [Sip] Multiple registration using single UA
Thread-Index: Acvyx40qlfumGLqGSUCoydQ2NiKT2wAAOUkg
Message-ID: <7FF1E5E16911C54BB2D57D4C4A2ED35A082FC7813C@EXMBXCLUS01.citservers.local>
References: <BANLkTimjjn16x4x1Cih4N9YcF2QMvO807Q@mail.gmail.com>
In-Reply-To: <BANLkTimjjn16x4x1Cih4N9YcF2QMvO807Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 04 Apr 2011 13:15:46 -0000
> 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? Unique. I assume that you are not attempting to use rfc6140 or rfc5626. > How could the SIP Server or Registrar verify that these > two numbers are in fact originating from the same Device? As far as I know, that is outside of the scope of rfc3261 unless you want to make assumptions/deductions concerning some header values (such as Contact or User-Agent). RFC 6140 may be of interest.