[Sip] Multiple registration using single UA
E D <storedge1@gmail.com> Mon, 04 April 2011 06:08 UTC
Return-Path: <storedge1@gmail.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 83D0C3A6917 for <sip@core3.amsl.com>; Sun, 3 Apr 2011 23:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 xfrDTwoVujuB for <sip@core3.amsl.com>; Sun, 3 Apr 2011 23:08:30 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 577563A68CB for <sip@ietf.org>; Sun, 3 Apr 2011 23:08:29 -0700 (PDT)
Received: by iwn39 with SMTP id 39so6372035iwn.31 for <sip@ietf.org>; Sun, 03 Apr 2011 23:10:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=lyeSUE1JRDhrDwxN7htHMPeOIgivL0ziYJXyD2wX5FI=; b=KC7Yao53ALfrHSb/eXX1mcks2cT5f5gGi7lRfr+kqp/3rMAgWTIP8RQDvAxmn3U++q W1nOOCWvSnXoZZvmHRvwKxdGhx5ENolkQdn43oysu2usorasap2AR7W9rKpobesnai2e I38hHXcxGYNgkdQFzOdjqTzi8EkZuu7kkgHaM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fGhahOwFc45AEzGQRt2RwRkcECXBJVdsUdOHE0bsMrrcqznFqvEpGtLmSD680VZ/CE oPaI73YK2Y/E9sUMHs/rfcShPDAD814uo2D4GkTlPEko6maNOtSBW6H7SgADASdjVxJZ RfpBuCq410nQEI2OOocFODOctN0t1GhwWXJMM=
MIME-Version: 1.0
Received: by 10.231.140.24 with SMTP id g24mr5568713ibu.175.1301897411499; Sun, 03 Apr 2011 23:10:11 -0700 (PDT)
Received: by 10.231.199.8 with HTTP; Sun, 3 Apr 2011 23:10:11 -0700 (PDT)
Date: Mon, 04 Apr 2011 01:10:11 -0500
Message-ID: <BANLkTimjjn16x4x1Cih4N9YcF2QMvO807Q@mail.gmail.com>
From: E D <storedge1@gmail.com>
To: sip@ietf.org
Content-Type: multipart/alternative; boundary="0016e6476288bf16a504a0119c90"
Subject: [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 12:53:27 -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? 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? Thanks in advance