|
|
@ -1907,24 +1907,25 @@ Disables call recording for the call. This can be sent during a call to imediatl |
|
|
`block DTMF` and `unblock DTMF` Messages |
|
|
`block DTMF` and `unblock DTMF` Messages |
|
|
---------------------------------------- |
|
|
---------------------------------------- |
|
|
These message types must include the key `call-id` in the message. They enable and disable blocking of DTMF |
|
|
These message types must include the key `call-id` in the message. They enable and disable blocking of DTMF |
|
|
events (RFC 4733 type packets) for a call, respectively. |
|
|
|
|
|
|
|
|
events (RFC 4733 type packets), respectively. |
|
|
|
|
|
|
|
|
When DTMF blocking is enabled for a call, DTMF event packets will not be forwarded to the receiving peer. |
|
|
|
|
|
If DTMF logging is enabled, DTMF events will still be logged to syslog while blocking is enabled. Blocking |
|
|
|
|
|
of DTMF events happens for an entire call and can be enabled and disabled at any time during call runtime. |
|
|
|
|
|
|
|
|
|
|
|
`block media` and `unblock media` Messages |
|
|
|
|
|
------------------------------------------ |
|
|
|
|
|
Analogous to `block DTMF` and `unblock DTMF` but blocks media packets instead of DTMF packets. DTMF packets |
|
|
|
|
|
can still pass through when media blocking is enabled. |
|
|
|
|
|
|
|
|
|
|
|
Media can be blocked for an entire call if only the `call-id` key is present in the message, or can be blocked |
|
|
|
|
|
|
|
|
Packets can be blocked for an entire call if only the `call-id` key is present in the message, or can be blocked |
|
|
directionally for individual participants. Participants can be selected by their SIP tag if the `from-tag` key |
|
|
directionally for individual participants. Participants can be selected by their SIP tag if the `from-tag` key |
|
|
is included in the message, or they can be selected by their SDP media address if the `address` key is included |
|
|
is included in the message, or they can be selected by their SDP media address if the `address` key is included |
|
|
in the message. In the latter case, the address can be an IPv4 or IPv6 address, and any participant that is |
|
|
in the message. In the latter case, the address can be an IPv4 or IPv6 address, and any participant that is |
|
|
found to have a matching address advertised as their SDP media address will have their originating media |
|
|
|
|
|
|
|
|
found to have a matching address advertised as their SDP media address will have their originating RTP |
|
|
packets blocked (or unblocked). |
|
|
packets blocked (or unblocked). |
|
|
|
|
|
|
|
|
Unblocking media for the entire call (i.e. only `call-id` is given) does not automatically unblock media for |
|
|
|
|
|
participants which had their media blocked directionally, unless the string `all` is included in the `flags` |
|
|
|
|
|
|
|
|
Unblocking packets for the entire call (i.e. only `call-id` is given) does not automatically unblock packets for |
|
|
|
|
|
participants which had their packets blocked directionally, unless the string `all` is included in the `flags` |
|
|
section of the message. |
|
|
section of the message. |
|
|
|
|
|
|
|
|
|
|
|
When DTMF blocking is enabled, DTMF event packets will not be forwarded to the receiving peer. |
|
|
|
|
|
If DTMF logging is enabled, DTMF events will still be logged to syslog while blocking is enabled. Blocking |
|
|
|
|
|
of DTMF events can be enabled and disabled at any time during call runtime. |
|
|
|
|
|
|
|
|
|
|
|
`block media` and `unblock media` Messages |
|
|
|
|
|
------------------------------------------ |
|
|
|
|
|
Analogous to `block DTMF` and `unblock DTMF` but blocks media packets instead of DTMF packets. DTMF packets |
|
|
|
|
|
can still pass through when media blocking is enabled. Media packets can be blocked for an entire call, or |
|
|
|
|
|
directionally for individual participants. See `block DTMF` above for details. |