[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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