Re: R: [Sipping-tispan] [CCBS/CCNR]

Tessa Silvia wrote:
> REQ-1:
> The entity providing the CCBS/CCNR service needs to know the change of
> the status of a UA (e.g., in CCBS a transition from busy to idle or in
> CCNR a transition from idle to another state) and it should have the
> ability to recognize if the UA is able to provide such indication.
> 
>

I think we need to split this into two requirements, one to monitor the 
callee (the status is dependent on whether CCBS or CCNR is used); the 
other is to monitor the caller, to check that he is not busy.

REQ-1:
   The entity providing the CCBS/CCNR service needs to know the change of
   the status of the callee (e.g., in CCBS a transition from busy to idle
   or in CCNR a transition from idle to another state) and it should
   have the ability to recognize if the UA is able to provide such
   indication.

REQ-1bis:
   The entity providing the CCBS/CCNR service needs to know the status
   of the caller at the time of allocating a timeslot to execute a
   pending CCBS/CCNR pending request. Should the caller be busy at that
   time, the CCBS/CCNR service will (check the action) de-queue the
   caller and send him a notification.

How about that?

/Miguel
-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.an.garcia@openlaboratory.net
Nokia Research Center      Helsinki, Finland

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan