[SIPForum-discussion] Fwd: Multiple SIP devices with same URI

[Tiago Palma]

Hello Csaba,

I am also new to this Forum and to SIP, however I'll do my best in trying to
answer to your question.
When you have 2 or more terminals registered to the same AOR (Address of
Record), the inbound proxy will read the terminals addresses register on
that AOR in the Location Service database and then it can have two different
approaches:

Sequential search: Where the proxy tries to call each terminal one after
another.
Parallel search: The proxy tries to call all the terminals simultaneously.

This is situation is called Forking.

Hope it was helpful,
Tiago Palma

---------- Forwarded message ----------
From: Sz.Cs. <kumite84 at freemail.hu>
Date: 2008/10/3
Subject: [SIPForum-discussion] Multiple SIP devices with same URI
To: discussion at sipforum.org




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/20081003/df476c05/attachment-0002.html>