[SIPForum-discussion] Multiple SIP devices with same URI

[technocrat voip]

In asterisk we have the same concept what sreeji was stating.

On Sat, Oct 4, 2008 at 1:58 AM, Sreeji Gopal <sreeji_g at yahoo.com> wrote:

> hi Csaba,
> Wellcome to Sip Forum.
>
> So here is some of my thoughts.....When 2 devices is registerd with the
> same SIP URI, and with the same contact then which ever device is registered
> last will be getting the ring. The concept is which ever is send register
> last will have the binding with the SIP URI, with port.
>
> -Sreeji
> *Sreeji Gopal *|* 94490 22324*
>
>
> ----- Original Message ----
> From: Sz.Cs. <kumite84 at freemail.hu>
> To: discussion at sipforum.org
> Sent: Friday, October 3, 2008 3:51:59 PM
> Subject: [SIPForum-discussion] Multiple SIP devices with same URI
>
>
>
> Dear list members!
>
> First of all, I've just registered SIPForum, this is my first letter here,
> so hello everyone:)
>
> I would like to ask some questions in the future, because I'm developing
> SIP related technologies during my studies.
> My question for now is: what happens when I call someone, who registered
> with more than one devices on the same SIP uri. For example I register my pc
> shoftphone and my VoIP client on my cellphone with: myuser at mydomain.com.
> If someone calls the myuser at mydomain.com which device should ring? I've
> read a lot of RFC-s, but didn't find my answer.
>
> Thank you for helping me!
>
> Csaba SZ.
>
> ________________________________________________________
> Szakíts, ha bírsz!
> <http://bookline.hu/control/producthome?id=71786&type=22&tabname=book&affiliate=frekaakar6748>
>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20081006/fc8dcde5/attachment-0002.html>