It seems the essence of your draft has nothing to do with how hold is
signaled - only with what the UA should do in that case. We don't
normally specify much about what the UA should do in those cases - the
UA has latitude to do as it wishes, which provides room for innovation.
Certainly a UA this is not receiving media is free to play something
locally if it wishes. But some people would prefer not to have that.
Also note that hold applies to any kind of media, not just audio. What
to do with video, or whiteboard, or IM or realtime text will be
different than what to do for audio.
The issues that have arisen with hold have to do with people getting the
signaling wrong - sometimes in a way that prevents getting off hold.
Thanks,
Paul
[EMAIL PROTECTED] wrote:
> In many mailing lists I read of problems with SIP signaling protocol and
> call on hold. In the actual implementation, "hold" is not different from
> "mute".
> This problem also occurred during my work.
> I wrote this draft:
> http://tools.ietf.org/id/draft-giordano-sip-call-hold-revision-00.txt
> What's your opinion.
> Thanks.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sip mailing list https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [EMAIL PROTECTED] for questions on current sip
> Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
