IETF Logo Mail Archive

Re: [sipcore] RFC5626 and REGISTER with multiple contacts

"Kevin P. Fleming" <kpfleming@digium.com> Fri, 04 May 2012 15:04 UTC

Return-Path: <kpfleming@digium.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B67121F860B for <sipcore@ietfa.amsl.com>; Fri, 4 May 2012 08:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.15
X-Spam-Level:
X-Spam-Status: No, score=-106.15 tagged_above=-999 required=5 tests=[AWL=-0.151, BAYES_00=-2.599, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0xfyaYYUOXYu for <sipcore@ietfa.amsl.com>; Fri, 4 May 2012 08:04:09 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id B630F21F85CE for <sipcore@ietf.org>; Fri, 4 May 2012 08:04:09 -0700 (PDT)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1SQK3E-0007G5-DE for sipcore@ietf.org; Fri, 04 May 2012 10:04:08 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 6A7EAD8004 for <sipcore@ietf.org>; Fri, 4 May 2012 10:04:08 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l451OJEyPvmG for <sipcore@ietf.org>; Fri, 4 May 2012 10:04:08 -0500 (CDT)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id 0BC34D8002 for <sipcore@ietf.org>; Fri, 4 May 2012 10:04:08 -0500 (CDT)
Message-ID: <4FA3EFD8.2080903@digium.com>
Date: Fri, 04 May 2012 10:03:52 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: sipcore@ietf.org
References: <3A324A65CCACC64289667DFAC0B88E12197E3BB890@ESESSCMS0360.eemea.ericsson.se> <CD5674C3CD99574EBA7432465FC13C1B22726A0AA4@DC-US1MBEX4.global.avaya.com> <3A324A65CCACC64289667DFAC0B88E12197E3BBBC8@ESESSCMS0360.eemea.ericsson.se> <CALiegfmdb5PHiXk0fiveHAiM6zwUTB8Fi5gPhM-WgzYT_J2uUg@mail.gmail.com> <3A324A65CCACC64289667DFAC0B88E12197E3BBDF5@ESESSCMS0360.eemea.ericsson.se> <CALiegfk5t5p=sw0MVcrzVshYs2Z3kiw0KYmqzLRGmdcPZj3YfA@mail.gmail.com> <3A324A65CCACC64289667DFAC0B88E12197E3BBEA3@ESESSCMS0360.eemea.ericsson.se>
In-Reply-To: <3A324A65CCACC64289667DFAC0B88E12197E3BBEA3@ESESSCMS0360.eemea.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [sipcore] RFC5626 and REGISTER with multiple contacts
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2012 15:04:10 -0000

On 05/04/2012 07:54 AM, Ivo Sedlacek wrote:

> applications have different capabilities, indicated in the associated contacts using the mechanism in RFC 3840. The home proxy then uses the mechanism in RFC 3841 to choose the correct contact (and correct UA, if multiple UAs have registered for the same AoR).

You are using a non-SIP term here, 'applications'. Contact URIs aren't 
bound to an AoR for applications, they are bound for SIP UAs. Each 
Contact header you provide in a REGISTER request represents a distinct 
SIP UA. If you want your individual applications (with differing 
capabilities) to be selected by a proxy/registrar, even if they all 
physically reside in the same endpoint, they will need different 
sip.instance values because they are separate UAs.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

v2.34.0 | Report a Bug | By Email | System Status