Re: [Asterisk-Dev] RFC2833 Event Duration

2005-11-05 Thread Kevin P. Fleming
Ryan Courtnage wrote: ... to it. In other words, Asterisk isn't passing along the duration of the original event. Correct. Is this by design? Can * be made to pass on the initial event duration? It is by design, i.e. not accidental. There is no way to pass on the duration at this time,

Re: [Asterisk-Dev] RFC2833 Event Duration

2005-11-05 Thread Andrew Kohlsmith
On Saturday 05 November 2005 14:17, Kevin P. Fleming wrote: It is by design, i.e. not accidental. There is no way to pass on the duration at this time, because incoming events are turned into AST_FRAME_DTMF as they pass through the Asterisk core, and those frames do not currently have any way

[Asterisk-Dev] RFC2833 Event Duration

2005-11-04 Thread Ryan Courtnage
Hello all, When holding down a digit on my (rfc2833) SIP phone, I see that (using Ethereal) the phone will send: RFC2833 RTP Event EventID: DTMF Five 5 (5) -- Duration: 47040 -- ... to Asterisk, where 47040 matches the amount of time I held down the 5 digit. If I've called another SIP