The concept of service execution in SIP was that multiple nodes could
be participatory. In the case of a 'missed call' a proxy may be just a
default forwarding device to an AS that really decides if the call is
missed. Similarly, depending on other factors, the AS itself may be
'handing off' a call to another node, say a B2B. The AS thinks that
the call is actually connected whereas the B2B knows it is not.
The question therefore arises as to who really knows that the call is
really missed and who reports. More importantly, if the notion of the
service result is shared between multiple nodes, no one node could
really report effectively.
Therefore, is the concept of 'call history' more applicable here as a
primitive that needs be specified and missed call a construct on top
of it ? I
On 9/23/05, Avasarala Ranjit-A20990 <ranjit at motorola.com> wrote:
Hi
I want to propose an internet draft on notification for missed calls/
messages thru XML event package. Plz go thru it and give your comments.
Thanks
<<draft-ranjit-missed-calls-msgs-00.txt>>
Regards
Ranjit
_______________________________________________
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
--
Arjun Roychowdhury
_______________________________________________
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