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

["Roy, Radhika \(AEAD\)" <RoyR at saic-abingdon.com>]

Let me try to add couple of scenarios.

>From server modeling point of view, an application server (e.g., proxy
with B2BUA, AS) will be in charge providing services, and it is supposed
to know that the call has been missed (others like user policies may
also play a role). It is a clear cut specific approach where a simple
solution can be found based on this assumption. However, it is one sided
centralized server model.

For P2P point of view, if a call is not accepted by a given peer, it may
be forwarded to the next peer and so on. Depending on the peering
modeling schemes (it is an assumption because we have not developed the
P2P-SIP protocol yet), it appears that it will create an history along
the peering path what has been the faith of the call. However, we have
to develop the p2p protocol first before solving this using peering
schemes.

The other end of the spectrum is to dig into analysis what Dean has
already proposed based on many if and what scenarios using the usual SIP
schemes. In this way, we can also see whether we can see the light at
the end of the tunnel.

Best regards,
Radhika

-----Original Message-----
From: sipping-bounces at ietf.org [mailto:sipping-bounces at ietf.org] On
Behalf Of Arjun Roychowdhury
Sent: Wednesday, September 28, 2005 7:10 AM
To: Avasarala Ranjit-A20990
Cc: sipping at ietf.org
Subject: Re: [Sipping] Internet draft on missed calls / msgs
notification

The intent of the draft is well placed and useful. However, I wonder
if this draft makes an assumption that the network service is only
provided by one entity.

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