Re: [martini] martini-gin-08, question on public-gruu

Paul Kyzivat <pkyzivat@cisco.com> Tue, 28 September 2010 12:44 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7D713A6D1C for <martini@core3.amsl.com>; Tue, 28 Sep 2010 05:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.488
X-Spam-Level:
X-Spam-Status: No, score=-110.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 S14aqBNmwHws for <martini@core3.amsl.com>; Tue, 28 Sep 2010 05:44:17 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 3970B3A6AED for <martini@ietf.org>; Tue, 28 Sep 2010 05:44:17 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALR/oUxAZnwN/2dsb2JhbACiHHGsBZx4AoVCBIo6gn8
X-IronPort-AV: E=Sophos;i="4.57,247,1283731200"; d="scan'208";a="164509108"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 28 Sep 2010 12:44:56 +0000
Received: from [161.44.174.118] (dhcp-161-44-174-118.cisco.com [161.44.174.118]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o8SCiuSQ007067; Tue, 28 Sep 2010 12:44:56 GMT
Message-ID: <4CA1E348.4060408@cisco.com>
Date: Tue, 28 Sep 2010 08:44:56 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: Martien Huysmans <martien.huysmans@ericsson.com>
References: <B1771F0F1F97A8478E2F449EA19CC7C5DA1A7EF2@ESESSCMS0365.eemea.ericsson.se>
In-Reply-To: <B1771F0F1F97A8478E2F449EA19CC7C5DA1A7EF2@ESESSCMS0365.eemea.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] martini-gin-08, question on public-gruu
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <martini.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/martini>
List-Post: <mailto:martini@ietf.org>
List-Help: <mailto:martini-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 12:44:18 -0000

That's how it will work unless the pbx optimizes it.

Its not really any different than when one UA of the pbx sends an INVITE 
to sip:+12145550102@ssp.example.com, which could arise in many ways. The 
pbx can optimize this by recognizing its own addresses.

	Thanks,
	Paul

On 9/28/2010 3:33 AM, Martien Huysmans wrote:
> Ch 7.1.1 describes that a UA behind a SIP-PBX can receive the following
> contact header
>
> <allOneLine>
>
> Contact: <sip:line-1@10.20.1.17>;
>
> pub-gruu="sip:+12145550102@ssp.example.com;gr=urn:
>
> uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6;sg=00:05:03:5e:70:a6";
>
> +sip.instance="<urn:uuid:d0e2f290-104b-11df-8a39-0800200c9a66>"
>
> ;expires=3600
>
> </allOneLine>.
>
> Assume this UA (UA1) send an INVITE to UA2 where UA1 includes in it’s
> contact the above public GRUU.
>
> Assume that UA1 and UA2 are both registered with the same SIP-PBX.
>
> Next UA2 uses the above public GRUU in an out-of-dialog INVITE request
> to UA2. That INVITE would look like
>
> INVITE
> sip:+12145550102@ssp.example.com;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6;sg=00:05:03:5e:70:a6
> SIP/2.0
>
> As the SIP-PBX is not authoritative for the ssp.example.com domain, the
> SIP-PBX will route the request to the SSP,
> where the RURI is updated and the following INVITE is send to the SIP-PBX.
>
> INVITE sip:+12145550102@198.51.100.3;sg=00:05:03:5e:70:a6 SIP/2.0.
>
> Is this how it will work?
>
> Regards Martien
>
> line
>
> *MARTIEN HUYSMANS Ir* *
> System Engineer*
>
>
> Ericsson
> ETM/DAB
> Ericssonstraat 2
> 5121 ML RIJEN, Netherlands
> Phone +31 161 24 9941
> Fax +31 (0)161 24 99 22
> Mobile +31 6 5120 3734
> martien.huysmans@ericsson.com
> www.ericsson.com
>
>
>
> http://www.ericsson.com/ <http://www.ericsson.com/>
>
> This Communication is Confidential. We only send and receive email on
> the basis of the terms set out at www.ericsson.com/email_disclaimer
> <http://www.ericsson.com/email_disclaimer>
>
>
>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini