[SIPForum-discussion] Parent Child registration vs Wildcardregistration

[Chris Gatch]

Greg,

 

I have not seen the wildcard example implemented, but I do know that the
first approach of using the parent/child is broadly implemented.  The
source of the concept is the original SIPconnect Interface Specification
that was produced before it went through the SIP Forum Technical Working
Group.  The explicit parent/child language was dropped in favor of a
more 'pure' approach.  

 

However, we left language that implicitly allowed parent/child while not
encouraging it.

 

SIP Application Servers MUST be prepared to accept (but MUST NOT
require) registrations for any valid URI that the

Service Provider has assigned to an Enterprise. This interface
specification does not define any specific action that is

triggered by a successful registration; however one possible use of this
information might be to update a DNS entry

associated with the PBX in a DNS zone managed by the Service Provider.

 

In the case of Cbeyond, for example, we use the registration of the
parent user to update the registration information of all SIP users
associated with the account that was registered.   If you need more
information on the way we handle this, feel free to contact me directly,
and I can provide some more detail.

 

Chris

 

________________________________

From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org] On Behalf Of Zweig, Greg
Sent: Friday, October 26, 2007 9:21 AM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] Parent Child registration vs
Wildcardregistration

All,

 

I was curious to get forum members' opinion on the two prevalent methods
of registering users that are behind a PBX.  Some carriers use a parent
child registration that creates a concept of an "alpha" subscriber while
others create a wild card so that subscribers within a group can more
easily be registered together.   I believe the latter was created by
Cisco

 

Using the parent child method, the PBX creates a binding between one of
its phone numbers as the address of record (AoR) and Contact-URI in the
REGISTER message. The registrar understands that a single AoR actually
represents many addresses, and so it registers them implicitly. 

 

Using the wild card a "." in the address serves as the wild card - up to
32 digits-- so that a variety of users at the same address can be
implicitly registered 

An example might look like Contact: <sip:12345..... at 15.3.33.29:5060>

 

I would appreciate any practical experience forum members have that
would provide advantages or disadvantages for the two methods.

 

Thanks, 

 

Greg 

 



**********************************************************************
This email may contain confidential information. If you are not
the intended recipient, please advise by return email and delete
immediately without reading or forwarding to others.
 -- Cbeyond 
**********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20071030/beba135a/attachment-0002.html>