RE: [Sipping] Internet draft on missed calls / msgs notification

[henry at sinnreich.net]

> I think the "server vs. peer-to-peer" distinction is a bit too simple.
>In reality, a SIP call could go through multiple levels of routing 
>and translation, each of which has its own logical view of "call history".

This is true and comes with a price tag however and the point of view
differs if you are the payer or the payee :-)

A user group such as "Our Class Reunion" can set up an ad hoc P2P network at
no cost if their SIP UA can support P2P and its features, such as voice
mail.

A "hot line" or emergency call center has obviously very different
requirements that may be better implemented in complex SIP server clouds;
though it could be argued that a self organizing P2P SIP server cloud has
lower cost for operations and is more resilient as well.

The proposed P2P SIP BOF at the 64 IETF may bring some light on this.

Call history and the logs can be very critical for legal reasons or help
with CALEA type of requirements but may be of less importance for small
communities of interest.

Thanks, Henry

-----Original Message-----
From: Dale R. Worley [mailto:dworley at pingtel.com] 
Sent: Friday, September 30, 2005 10:29 AM
To: Sipping
Subject: RE: [Sipping] Internet draft on missed calls / msgs notification

I think the "server vs. peer-to-peer" distinction is a bit too simple.
In reality, a SIP call could go through multiple levels of routing and
translation, each of which has its own logical view of "call history".

Consider a "hot line" AOR that routes to a changing group of people who
answer the hot line.  One of those people has his own AOR, which has a
several contacts.  One of those contacts is a mobile phone, which is
sometimes off-network.

The mobile can keep a call history, but of course it can't log calls
missed because it was off-network, though it can log calls that were
missed because it was busy.

The individual's AOR has to be handled by a server (or a coordinated
distributed set of agents which perform logically like a server), and
that server (those servers) can keep a call history for calls that
routed through the individual's AOR.

The hot line AOR's server similarly keeps a call history.  But of course
calls placed directly to the individual's AOR don't feature in the hot
line AOR call history.


This also points out that the record for a call ideally contains
information about the responses of all end-points of the call -- it's
possible that one UA was busy, and a second UA was unreachable (off-
network).  To keep sensible state, both of those data need to be
recorded.

We may also want to consider logging information from the "call
redirection" information that people are talking about.

Dale



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP




_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sip at ietf.org for new developments of core SIP