Re: [sipcore] RFC5626 and REGISTER with multiple contacts

Hello,

> This is, if your device registers various bindings for the AoR in the REGISTER's 
> To header, when that AoR is called your device would receive the request with parallel 
> forking for each binding. What is the purpose of that? 

Applications have different capabilities, indicated in the associated contacts using the mechanism in RFC 3840.
The registrar then uses the mechanism in RFC 3841 to choose the correct contact.

Kind regards

Ivo Sedlacek 

Ericsson
GF Technology, Terminal Standardization
Sweden
Office: +46 10 711 9382
ivo.sedlacek@ericsson.com
www.ericsson.com

This communication is confidential. We only send and receive email on the basis of the term set out at www.ericsson.com/email_disclaimer

-----Original Message-----
> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On Behalf Of Iñaki 
> Baz Castillo 
> Sent: 3. května 2012 16:02 
> To: Ivo Sedlacek 
> Cc: sipcore@ietf.org 
> Subject: Re: [sipcore] RFC5626 and REGISTER with multiple contacts 
> 
> 2012/5/3 Ivo Sedlacek <ivo.sedlacek@ericsson.com>: 
> > Is there a reason why REGISTER with multiple contacts, each having the  
> > same sip.instance, the same IP address and port and the same reg-id,  
> > should be rejected? 
> 
> Let me first a question please: what is the purpose of registering various Contact 
> URI's in the same REGISTER (so an unique To header 
> AoR) pointing all of them to the same "device"? 
> 
> This is, if your device registers various bindings for the AoR in the REGISTER's 
> To header, when that AoR is called your device would receive the request with parallel 
> forking for each binding. What is the purpose of that? 
> 
> -- 
> Iñaki Baz Castillo 
> <ibc@aliax.net> 
> _______________________________________________ 
> sipcore mailing list 
> sipcore@ietf.org 
> https://www.ietf.org/mailman/listinfo/sipcore 
> 