1 / 13

A SIP Event Package for DTMF Event Monitoring draft-zebarth-sipping-dtmfad-00.txt

IETF 58. A SIP Event Package for DTMF Event Monitoring draft-zebarth-sipping-dtmfad-00.txt. Joe Zebarth, Vice Chair T1S1.7. This document: Was prepared on behalf of Committee T1 Defines A SIP Event Package for DTMF Event Monitoring

mahola
Download Presentation

A SIP Event Package for DTMF Event Monitoring draft-zebarth-sipping-dtmfad-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. IETF 58 A SIP Event Package for DTMF Event Monitoring draft-zebarth-sipping-dtmfad-00.txt Joe Zebarth, Vice Chair T1S1.7

  2. This document: • Was prepared on behalf of Committee T1 • Defines A SIP Event Package for DTMF Event Monitoring • Was prepared to support IANA Registration perRFC 3427 (BCP 67) Change Process for the Session Initiation Protocol

  3. Event Package "DTMFAD" proposes use ofSUBSCRIBE and NOTIFY to collect DTMF digits • to implement: • Committee T1 Technical Report T1.TR.82-2003 • “SIP Network Operators Implementers Guide for • Pre-Paid Calling Card, with DTMF Detection at • the PSTN-IP Gateway”

  4. Usage Scenario This event package MAY be used to allow an Application server (subscriber) to request DTMF monitoring and notification of detection from a receiving agent (notifier) in order to enable a caller-initiated re-origination request while a call is in progress. It is recognized that there may be other possible applications of this event package.

  5. This document: • Defines new Event Header Field parameters: • duration • event-set • maxrate • Defines a new MIME type: • application/DTMF-event • Was prepared to support IANA Registration perRFC 3427 (BCP 67) Change Process for the Session Initiation Protocol

  6. Characteristics of Event Package • Very Simple • Compact

  7. Relationship to KPML Event Package • Less sophisticated • Simpler • Processing intensity at different locations • KMPL package requires processing intensity at the Notifier • DTMFAD package requires processing intensity at the Application Server • Seen as complementary, not competitive

  8. Our desire: This ID be published as an Informational RFC so that IANA registration of this event package can be obtained

  9. Thank You

  10. Duration Parameter: • An optional parameter that: • defines the duration of a continuous DTMF tone (in milliseconds) that will cause the notifier to send a NOTIFY request before detecting the end of thetone • If omitted requires event notification to occur only when the end of the DTMF tone is detected Recommended that this parameter be omittedfor normal implementations to reduce messages

  11. Maxrate Parameter: • An optional parameter defining a maximum number of NOTIFY transactions per minute initiated to report DTMF events. • If "maxrate" is omitted, the notifier MUST limit reporting to forty (40) NOTIFY transactions perminute • When defined SHOULD NOT exceed 60. For this particular usage scenario this parameter may be omitted

  12. Event-set Parameter: • An optional parameter that: • defines the set of events that are to be detected by the notifier • If omitted, it must detect the following set of events: • digits 0 through 9 (decimal 0-9) • the * key (hexadecimal a) • the # key (hexadecimal b); and • special digits A through D (hexadecimal c-f) For this particular usage scenario this parameter may be omitted

  13. Defines a new MIME type: • MIME media type name: application • MIME subtype name: DTMF-event • Mandatory parameters: none • Optional parameters: none • Encoding considerations: binary encoding scheme • Notifier shall encode DTMF-event as four octets 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | event |E|R| volume | duration | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

More Related