Hi Francois,
I agree with you that there are a few necessary issues such as this that are
not addressed in the Signalled Digits draft.
At the moment a number of people are working on another draft for using
SUBSCRIBE/NOTIFY to request/receive key events which plans to
- define the behaviour of call-leg specific subscriptions (using a
reusable mechanism, hopefully to be eventually rolled into the main SIP
Events draft)
- supports the transport of entities other than DTMF based tones (eg
keyboards and user-defined buttons)
I'm not sure what Rohan's plans for the Signalled Digits draft are.
We hope to have the draft ready within a few weeks.
Regards,
Robert.
> -----Original Message-----
> From: Lessing, Francois [mailto:[EMAIL PROTECTED]]
> Sent: 06 October 2001 01:50
> To: [EMAIL PROTECTED]
> Subject: [Sip-implementors] Signalled digits question
>
>
> Hi everyone,
>
> I have two questions:
>
> In the draft called "Signaled Digits in SIP", the example in
> section 5 suggests that the SUBSCRIBE
> is sent using the call leg of the existing INVITE. Does this mean that
>
> SUBSCRIBE CallId == INVITE CallId
> SUBSCRIBE To == INVITE To (the Tag of To excl.)
> SUBSCRIBE From + Tag == INVITE From + Tag
> SUBSCRIBE Cseq > than previous Cseq for this leg
>
> How should the SUBSCRIBE 'terminate' when a BYE is received
> for that call leg ?
>
> should
> 1. the SUBSCRIPTION be left to 'timeout' ?
> 2. A final notify/subscribe with Expires = 0 be sent ?
> 3. the SUBSCRIPTION just dies with the call leg.
>
> thanx,
>
> Francois Lessing
> Trillium Digital Systems, an Intel Company
>
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
