Changes between Initial Version and Version 3 of Ticket #2036
- Timestamp:
- Sep 10, 2018 3:02:19 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2036
- Property Status changed from new to closed
- Property Resolution changed from to fixed
- Property Milestone changed from release-2.7.1 to release-2.8
-
Ticket #2036 – Description
initial v3 2 2 3 3 Considering that this is a proprietary feature (see [https://tools.ietf.org/html/rfc6086#section-2 here]) and it may not be desirable on some system, e.g: SIP INFO message burst may introduce congestion on the network and may cause load spike on SIP server, the feature should be configurable and by default it is disabled. 4 5 This ticket will introduce ```pjsua_dtmf_method``` to specify the DTMF sending method. 6 7 '''PJSUA API''' \\ 8 To send DTMF as SIP INFO: \\ 9 Set ```pjsua_call_send_dtmf_param.method``` to ```PJSUA_DTMF_METHOD_SIP_INFO``` when calling ```pjsua_call_send_dtmf()```. 10 11 To get the notification of incoming DTMF: \\ 12 Use ```on_dtmf_digit2()``` callback. 13 14 '''PJSUA2 API''' \\ 15 To send DTMF as SIP INFO: \\ 16 Set ```CallSendDtmfParam::method``` to ```PJSUA_DTMF_METHOD_SIP_INFO``` when calling ```Call::sendDtmf()```. 17 18 To get the notification of incoming DTMF: \\ 19 Use ```Call::onDtmfDigit()``` callback.