The proposal to sort of publish to caller's supension and resumption state was
also resulting from previous comments, that just unsubscribe to the
call-completion information won't (or better: has not to) change the CC state.
So when the monitor calculates who's next for CC, a unsubscribed caller ('s
agent) would still be considered to be the next candidate for the CC call
somehow if he is on top of the queue, which then of course would reduce the
performance of the service.
To avoid this publishing sus/res information seems to be a valid and explicit
solution.
BR, Martin
>
>
> >OTOH, its far from clear to me that this is preferable to
> the existing
> >proposal for the candidate caller to unsubscribe when it
> doesn't want to
> >be called back.
>
> Why? Could you describe the issue?
>
> Greetings,
> Denis Alexeitsev
>
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
