Hi, Problem with dual registrations without Outbound comes with forking. When a device registers itself twice with different Contact addresses, it will receive every request destined to the AOR twice if the server implements parallel forking or if the device rejects the first forked request. On the other hand if the contact addresses are the same within the dual registrations, without Outbound that is just a registration refresh instead of dual registration, correct ?
Please tell if I miss some point of specified behaviour here. For instance 3GPP is considering using Outbound to solve this problem of multiple registrations even if there would not be any NATs in the access network. --- A long time ago I posted a long email suggesting Outbound to be split to two drafts, addressing two different problems: - One that specifies the keepalive behaviour (needed for NATs) - One that specifies multiple registration behaviour (needed for increased reliability) But it was not very popular suggestion and did not get many responses. Perhaps the suggestion was raised too late, at that time many were just waiting to get Outbound frozen and published as RFC. Regards, Erkki >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of ext Dean Willis >Sent: 06.October.2008 04:08 >To: SIP IETF >Subject: [Sip] Dual registration without Outbound > > >I'm hearing from some people that they're being forced to use >Outbound >even when there are no NATs to consider, because Outbound is the only >way for a device to have dual registrations. > >Personally, I seem to remember some systems that were doing multiple >registrations long before Outbound, so I'm wondering who's missing >what here, and what if anything we need to document or specify. > >Thoughts? > >-- >Dean > >_______________________________________________ >Sip mailing list https://www.ietf.org/mailman/listinfo/sip >This list is for NEW development of the core SIP Protocol >Use [EMAIL PROTECTED] for questions on current sip >Use [EMAIL PROTECTED] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
