| Page Properties | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Keyword to enable feature | Add a new hidden keyword to enable this feature into the SIP section of the callctrl.cfg file. In the future this keyword may be used to enable RFC2833 if the capabilities to do so has been added to the product. This parameter shall be an enabled/disabled setting and will default to false. | Must Have | TBD: callctrl.cfg or btcall.cfg setting. |
| 2 | Advertise support for RFC 2833 | When the feature is enabled, the outbound SDP will show support for RFC2833. It shall show support for events 0-15. a=rtpmap:101 telephone-event/8000 | Must Have | |
| 3 | No RFC2833 events | The SR140 is not required to generate any RFC2833 events. DTMF tones generated will not change from the current implementation. The tones will be sent as a part of the RTP audio stream. Support for generating RFC2833 or RC4733 events may be added at a future time but it is not a requirement for this feature request. | Must Have | |
| 4 | Documenation | The documentation for this feature shall state that this parameter only advises support for RFC2833 and that the product will not generate RFC2833 events. This parameter should be only enabled when advised by tech support. | Must Have |
References
- RFC 2833: RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals - http://www.ietf.org/rfc/rfc2833.txt
- RFC 4733 (obsoletes RFC 2833): RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals - http://www.ietf.org/rfc/rfc4733.txt
- RFC 4734 (updates RFC 4733): Definition of Events for Modem, Fax, and Text Telephony Signals - http://www.ietf.org/rfc/rfc4734.txt
- RFC 5244 (updates RFC 4733): Definition of Events for Channel-Oriented Telephony Signaling - http://www.ietf.org/rfc/rfc5244.txt
...