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

Martien Huysmans <martien.huysmans@ericsson.com> Tue, 28 September 2010 14:53 UTC

Return-Path: <martien.huysmans@ericsson.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 A598E3A6D1A for <martini@core3.amsl.com>; Tue, 28 Sep 2010 07:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.04
X-Spam-Level:
X-Spam-Status: No, score=-5.04 tagged_above=-999 required=5 tests=[AWL=1.559, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8+r1AL5ZrGFB for <martini@core3.amsl.com>; Tue, 28 Sep 2010 07:53:39 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 875D93A6BB1 for <martini@ietf.org>; Tue, 28 Sep 2010 07:53:35 -0700 (PDT)
X-AuditID: c1b4fb3d-b7cbfae00000264e-19-4ca2019741c2
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 27.FD.09806.79102AC4; Tue, 28 Sep 2010 16:54:16 +0200 (CEST)
Received: from ESESSCMS0365.eemea.ericsson.se ([169.254.1.32]) by esessmw0256.eemea.ericsson.se ([10.2.3.125]) with mapi; Tue, 28 Sep 2010 16:54:15 +0200
From: Martien Huysmans <martien.huysmans@ericsson.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Tue, 28 Sep 2010 16:54:13 +0200
Thread-Topic: [martini] martini-gin-08, question on public-gruu
Thread-Index: ActfCvu/Hh3r1fYjTq+VumYnBguhQQAESkIQ
Message-ID: <B1771F0F1F97A8478E2F449EA19CC7C5DA1A83A4@ESESSCMS0365.eemea.ericsson.se>
References: <B1771F0F1F97A8478E2F449EA19CC7C5DA1A7EF2@ESESSCMS0365.eemea.ericsson.se> <4CA1E348.4060408@cisco.com>
In-Reply-To: <4CA1E348.4060408@cisco.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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 14:53:44 -0000

Interesting reply (from Paul & Adam).
I expected a reply where the "who is authoritative for the ssp.example.com domain" to play a central role. 

/Martien

-----Original Message-----
From: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Sent: Tuesday, September 28, 2010 2:45 PM
To: Martien Huysmans
Cc: martini@ietf.org
Subject: Re: [martini] martini-gin-08, question on public-gruu

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