[SIPForum-techwg] Overview of Registration Mode - Proposed text

[Bharrat, Shaun]

Dave:

This will probably be clear when we get examples but a question
on the following:

> registered. The SP-SSE does this following the normal procedures for
routing requests to registered SIP endpoints, except that it skips the
request-retargeting step; i.e. based on locally configured data, the
SP-SSE does not overwrite the enterprise Public Identity contained in
the Request-URI with the SIP signaling address of the SIP-PBX. The
SP-SSE identifies the SIP-signaling address of the SIP-PBX in an
out-of-dialog request only if the request contains a Route header, as
described in Section 17.7.

I was presuming that the above applied to the username but that hostname
and parameters would be replaced with the registered contact values.

>From the current text, it seems that if the IP-PBX registered with
REGISTER sip:fqdn1
To: <sip:user1 at fqdn1>
From: <sip:user1 at fqdn1>
Contact: user1 at fqdn2;param=value1

And the SP-SSE got 
INVITE sip:user2 at fqdn1 SIP/2.0
To: sip:user2 at fqdn1
From: sip:anybody at anyfqdn

Then according to the text above, what is sent is exactly the above and NOT
INVITE sip:user2 at fqdn2;param=value1 SIP/2.0
To: sip:user2 at fqdn1
From: sip:anybody at anyfqdn

Am I interpreting this correctly?

Thanks and cheers,
Shaun



-----Original Message-----
From: techwg-bounces at sipforum.org on behalf of David Hancock
Sent: Tue 4/21/2009 6:12 PM
To: techwg at sipforum.org
Subject: [SIPForum-techwg] Overview of Registration Mode - Proposed text
 
On last week's call, Richard asked me to write some introductory text in
section 17 that provides an overview of the Registration mode. Here is
my 1st-pass attempt at doing that. This is pretty high-level at this
point - I could add more detail if people think necessary. I'm also
working on a new "Registration Examples" section that hopefully provides
more details by documenting some of the registration examples we've been
discussing on the reflector. 

 


17 Annex A: Registration Mode


In the Registration mode, the SIP-PBX provides its SIP signaling address
to the SIP-SSP using the SIP registration procedure defined in RFC 3261.
In effect, the SIP-PBX registers with the SP network, just like a
directly hosted SIP endpoint would register. Once the SIP-PBX has
registered, the SP-SSE uses the location binding information established
during registration to route subsequent dialog-initiating requests to
the SIP-PBX.

 

Prior to registration, the SIP-PBX and the SP-SSE are each configured
with the enterprise Public Identities served by the SIP-PBX. This
includes the single Main Public Identity that identifies the SIP-PBX
itself, and the zero or more Alternate Public Identities that identify
the individual enterprise users served by the SIP-PBX (see Section 9 for
a more detailed definition of Main and Alternate enterprise Public
Identities). 

 

When the SIP-PBX first starts up (or comes back online after a failure),
it registers the assigned Main Public Identity following normal SIP
registration procedures. The registration of this single Main Public
Identity does two things within the SP-SSE:

*	It creates a binding in the SP-SSE between the Main Public
Identity and the SIP signaling address of the SIP-PBX that was
identified in the Contact header of the REGISTER request ,
*	It implicitly registers the assigned Alternate Public
Identities, thus creating a binding between these alternate identities
and the SIP signaling address of the SIP-PBX.

 

When the SP-SSE receives an out-of-dialog request containing a
Request-URI that identifies either the Main or an Alternate Public
Identity assigned to the SIP-PBX, it routes the request to the SIP-PBX
using the location binding that was established when the SIP-PBX
registered. The SP-SSE does this following the normal procedures for
routing requests to registered SIP endpoints, except that it skips the
request-retargeting step; i.e. based on locally configured data, the
SP-SSE does not overwrite the enterprise Public Identity contained in
the Request-URI with the SIP signaling address of the SIP-PBX. The
SP-SSE identifies the SIP-signaling address of the SIP-PBX in an
out-of-dialog request only if the request contains a Route header, as
described in Section 17.7.

 

Thanks

David