RE: [Sip] Cannot REGISTER Ad Hoc SIP Conference?

["Rosen, Brian" <Brian.Rosen@marconi.com>]

We make this work roughly (code is evolving) the following way:
	We provision (actually, it's learned) the name of the local
		conference factory uri.  This is a fixed uri, and is
		local to the domain of the conference host.
	The conference host registers with this well known
		address.  It is an actual "user" in the system.
	We start with a 1on1 call, between the first two parties
	When we add the third party, the UA initiating this action
		sends an INVITE to the conference factory uri.
	The conference host returns a Contact header with
		a unique conference uri.  The conference uri is
		constructed using a pattern known to the outgoing proxy
	The UA initiating the conference REFERs all three parties to
		the conference using the conference uri
	Invites with a username matching the pattern are routed to
		the conference host

Brian


> -----Original Message-----
> From: Matt Guertin [mailto:mguertin@sonexis.com]
> Sent: Wednesday, September 10, 2003 11:20 AM
> To: sip@ietf.org
> Subject: [Sip] Cannot REGISTER Ad Hoc SIP Conference?
> 
> 
> I read through all the SIP specs that I know of, and believe to have
> implement our SIP Conference "focus" correctly.  We have what 
> is sometimes
> referred to as a SIP Conference Bridge Marshal Server (in vocal speak
> anyway).  When I go to do a REGISTER request, the 
> authentication fails,
> because the username/password does not match with the 
> ConferenceURI.  I can
> only register with ConferenceURIs which have 
> usernames/password provisioned.
> This doesn't work for Ad Hoc conferences, and even for 
> scheduled conferences
> for that matter.  It is unacceptable in a practical 
> application to send mail
> to an administrator every time a new conference is scheduled 
> to generate a
> username/password for the conference.  The administrator may 
> not get around
> to adding the new username/password for hours or even days.  
> Am I missing
> something?  We are using the contact field the way it is 
> spec'ed in the
> conference framework draft (ie., the isfocus flag is set).
> 
> 
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip