[SIPForum-discussion] Basic questions about Presence Event Package (RFC 3856)

Jayantheesh Sirmushnam - NPD, Chennai jayanteeshs at npd.hcltech.com
Tue Jul 11 07:38:22 UTC 2006


Hi,

         Please see my response inline.

 

-----Original Message-----
From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org]On Behalf Of Rodrigo Pimenta
Carvalho
Sent: Monday, July 10, 2006 7:30 PM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] Basic questions about Presence Event Package
(RFC 3856)

Hi.

 

I had redden the IETF RFC 3263 (Locating SIP Servers), the RFC 3680 (Event
Package for Registrations) and the RFC 3856 (Presence Event Package)

 

Now, I have some questions. Any hint about the following questions will help
me a lot.

 

1)      The FRC 3856 says that a watcher can subscribe to a kind of server,
to get information about the presence of some user. The presence of the user
is updated with the PUA action, like following shown.

 

 

   Watcher             Server                 PUA (Presence User Agent)
      | F1 SUBSCRIBE      |                    |
      |------------------>|                    |
      | F2 200 OK         |                    |
      |<------------------|                    |
      | F3 NOTIFY         |                    |
      |<------------------|                    |
      | F4 200 OK         |                    |
      |------------------>|                    |
      |                   |                    |
      |                   |   Update presence  |
      |                   |<------------------ |
      |                   |                    |
      | F5 NOTIFY         |                    |
      |<------------------|                    |
      | F6 200 OK         |                    |
      |------------------>|                    |
 
 
      If the user turns off your device (Ex: turning off his SIP Phone), the
PUA will update the user's presence with the Server. Then, the watcher can
know the user is no more present in some device. However, if the same user
turns on another device, but in some place completely out off the PUA/Server
domain, how can the Server be updated correctly?

       >>>There are two ways to implement it.

             1. Server can check the domain. If it is some other domain then
it can forward the request stateless.

 
Or

             2. Status of the user A in the server 2.com has to be updated
in the server 1.com, by means of Subscribe-Notify mechanism.

 

2)      Where the Server must be running? 

            >>> Can be in the same box or a different one.

3)      How many PUA does exist for a user?

            >>> There is no limitation

4)      How many Servers do exist for a user?

            >>> There is no limitation

5)      Where the PUAs must be running?

            >>> There is no specific location

6)      Does a SIP Phone have a PUA? If yes, how can it know where is the
Server? If not, is it possible putting a PUA inside of a SIP Phone?

            >>> Need to specify in the configuration.

7)      How can the watcher and the user(PUA)  know that they are using a
same Server?

            >>>> By means of configuration parameters.

8)      If the Server is a service, who should serve it? A private company?
A public one? 

 

 

Thanks.

 

Rodrigo Pimenta Carvalho.

Brazil.

 

Thanks,

Jayantheesh


Disclaimer:

This message and any attachment(s) contained here are information that is confidential, proprietary to HCL Technologies and its customers, privileged or otherwise protected by law. The information is solely intended for the individual or the entity it is addressed to. If you are not the intended recipient of this message, you are not authorized to read, forward, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20060711/5dc19636/attachment-0005.html>


More information about the discussion mailing list