RE: [Sipping-tispan] Requirements -02h

["Elwell, John" <[e-mail]>]

Miguel,

In my opinion the recall should be presented to the UA(s) concerned, which
should each have the possibility to accept the recall. The decision to
accept could be based on policy (e.g., automatically accept if there is no
call in progress) or based on the outcome of interaction with the user
(e.g., the user might choose to interrupt an ongoing call in order to accept
the recall if he considers the CCBS/CCNR call more important. But I am only
guessing at what TISPAN might have in mind.

John
 

> -----Original Message-----
> From: Miguel Garcia [mailto:[e-mail]] 
> Sent: 03 October 2005 12:48
> To: Elwell, John
> Cc: '[e-mail]'.org'; Alexeitsev, D
> Subject: Re: [Sipping-tispan] Requirements -02h
> 
> Hi John:
> 
> Good point, I don't even know myself. This could be:
> 
> a) there is already at least one more SIP session going on 
> from that UA 
> or from any other UA that the caller is using.
> 
> b) similar to a), but with a number of predetermined 
> simultaneous sessions.
> 
> c) the caller does not answer an invitation for a CCBS/CCNR callback.
> 
> d) the caller declines the previous invitation.
> 
> Something like that?
> 
> /Miguel
> 
> Elwell, John wrote:
> 
> > Miguel,
> > 
> > "REQ-CCBS/CCNR-15: Should the caller be busy at the time of 
> executing
> >                      CCBS/CCNR request, the request is 
> suspended until
> >                      its status changes (back to free status)."
> > 
> > What is meant by caller busy? Is this the human user (or 
> application)? Or
> > the UA from which CCBS/CCNR was requested? Or all the 
> caller's UAs? Or any
> > of the caller's UAs? This is important as it will determine the SIP
> > signalling needed to determine whether the caller is busy.
> > 
> > John
> > 
> > 
> >>-----Original Message-----
> >>From: Miguel Garcia [mailto:[e-mail]] 
> >>Sent: 30 September 2005 11:00
> >>To: '[e-mail]'
> >>Cc: Alexeitsev, D
> >>Subject: [Sipping-tispan] Requirements -02h
> >>
> >>ok, so here it goes with a new iteration:
> >>
> >>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin
> >>g-tispan-requirements-02h.txt
> >>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin
> >>g-tispan-requirements-02h.html
> >>
> >>And the diff version:
> >>http://people.nokia.net/~miguel/drafts/pre/draft-jesske-sippin
> >>g-tispan-requirements-02g-to-h.html
> >>
> >>Changes:
> >>- Clarification that we don't list every single requirement 
> >>that we have.
> >>- Calling Party Category requirements are now in the general section
> >>- New CCBS/CCNR requirements for the callee to be able to reject a 
> >>request for the service and to be able to use any given terminal.
> >>- Clear of ACR text related to the override feature.
> >>
> >>Note that I am still trying to classify my e-mail. Since 
> you all have 
> >>been very active in the last few days, I wouldn't be 
> surprise to see 
> >>that I have forgotten to add or modify something that has 
> been agree 
> >>upon. In such case, please drop me an e-mail and I will add 
> it in the 
> >>next iteration.
> >>
> >>/Miguel
> >>-- 
> >>Miguel A. Garcia           tel:[phone]
> >>sip:[e-mail]
> >>Nokia Research Center      Helsinki, Finland
> >>
> >>
> >>_______________________________________________
> >>Sipping-tispan mailing list
> >>[e-mail]
> >>https://www1.ietf.org/mailman/listinfo/sipping-tispan
> >>
> 
> -- 
> Miguel A. Garcia           tel:[phone]
> sip:[e-mail]
> Nokia Research Center      Helsinki, Finland
> 

_______________________________________________
Sipping-tispan mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/sipping-tispan