Well, this is certainly getting exciting. Andy, I took your advice and re-read the RFP. Andy--I don't think you are a good candidate for a beginner's book on *, but if you send my your address, I'll send you a copy on me. :-)
So, gentlemen, help me out here. The spec says: "The Address of record is the "SIP address that the registry knows the registrand. . ."" "A Sip message is either a request from a client to a server or a response from a server to a client. " "A client uses the REGISTER method to register the address listed in the TO header field with a SIP Server." And as Nick so cogently pointed out "Once a client has established bindings at a registrar, it MAY send subsequent registrations containing new bindings or modifications to existing bindings as necessary. The 2xx response to the REGISTER request will contain, in a Contact header field, a complete list of bindings that have been registered for this address-of-record at this registrar." I don't see how two different clients can register with a server as the same address of record. Doesn't the second registration from a new client change the address of record for the registered client? If the second client is trying the same registration as the first client, and it's the responsibility of the client to provide the complete list of bindings, how does the second client know the list of bindings for the first client that bound the registration? So isn't this the problem * has? The first client registers as the address of record, then the second client comes in with the same registration and becomes the address of record? Andy, I'm in your hands. Paul Paul Mahler [EMAIL PROTECTED] Signate, LLC 665 Third Street Suite 100 San Francisco, CA 94107-1901 Asterisk Services and Training > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Nicholas Bachmann > Sent: Sunday, July 11, 2004 12:41 PM > To: [EMAIL PROTECTED] > Subject: Re: [Asterisk-Users] New Asterisk bounty: SIP simultaneous > > Mike Machado wrote: > > >On Sun, 2004-07-11 at 12:31, Paul Mahler wrote: > > > > > >>The whole point of a SIP registration is to identify a > UNIQUE device. > >>You CAN'T HAVE multiple devices registered as the same SIP device. > >>That's WHY the last device that registers gets the traffic. > >> > >>This doesn't have ANYTHING TO DO WITH ASTERISK. This is a > SIP issue, > >>not an Asterisk issue. You should just be happy that > Asterisk will do > >>what you want, even if SIP won't. > >> > >>If you really, really want to do this, up the bounty to > about $50,000 > >>and get the SIP specification changed. > >> > >> > >Did you even read the RFC? Section 10.2.1 clearly talks about adding > >multiple bindings to the same address-of record. > > > Just to quote and save everybody the searching: > > Once a client has established bindings at a registrar, it MAY send > subsequent registrations containing new bindings or > modifications to > existing bindings as necessary. The 2xx response to the REGISTER > request will contain, in a Contact header field, a complete list of > bindings that have been registered for this > address-of-record at this > registrar. > > > Nick > > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
