[SIPForum-discussion] Multiple SIP devices with same URI

[neeraj]

hi Csaba,

During registartion each UE has to register its terminal capability. For example in your PC, u have audio as well as video capabiltiy. but other terminal you only have audio or video. similarly there are n number of capability associate with each PUI registartion. All this information is knoe to your proxy server. 

So when new request receive to your proxy server, it checks in the contact or accept contact header to get the capability requirment to handle the request. Based on the incoming request, it route it ot the correct terminal. For more detail you can check RFC 3840, 3841.

Thanks,
Neeraj
---- Original Message ----- 
  From: Sz.Cs. 
  To: discussion at sipforum.org 
  Sent: Friday, October 03, 2008 3:51 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! 


------------------------------------------------------------------------------


  _______________________________________________
  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/03694167/attachment-0002.html>