Mute by extension
When sending a Mute request by Voicenter extension SIP ID, all the active calls on
this extension will be muted (multiple calls can be in case of a conference call,
attended transfer calls, etc.).
Important. In case a Mute request by extension was sent, and after that the extension
will make a new call, the initial Mute request will not include the new call and
another mute request must be sent to mute the new call.
For example, a representative who speaks to a customer and is about to get the
customer credit card number.
The representative will send a mute request at this
stage so this part of the call will not be recorded.
If after the representative sends the Mute request the customer asks the representative to call another person to get the credit card details, this new call will not be muted, unless the representative sends another Mute call request.
URI
https://<monitorX>.voicenter.co/api/MuteUnmuteCalls
Please notice that <monitorX> is the name of the monitor server assigned to your account.
You can ask Voicenter support for the static monitor server of your specific account, or deploy the RealTimeAPI to get this list dynamically.
https://www.voicenter.com/API/real-time
Acceptable request types
1. POST-JSON
2. GET
Possible Response formats
1. POST-JSON
Client Request Parameters
| Field name | Description | Type | Remarks |
| extension | SIP ID of the extension, as found in the Cpanel. | String | Mandatory |
| state | 0 – Unmute . 1 - Mute. | String | Mandatory |
Client Request Example (GET)
https://YOUR_MONITOR.voicenter.co/api/MuteUnmuteCalls?extension=XXXXXXXX&state=1
Client Request Example (POST - JSON)
Voicenter Response Parameters
| Field name | Description | Type |
| ErrorCode | Describes the status of the client reqeust. The status 200 will indicate a succesfull reqeust. | Integer |
| Message | Response status description. Response status description: "Success" – No errors. "UniqueIvrID not found" - The Code value or format is invalid. "Parameters are not valid, should be \"ivrid\" and \"mute\" - The sent parameters are invalid. | String |
| ActionID | Unique ID of the action perfromed. | String |
Voicenter Response Example
Mute by a specific call
A Mute request can be sent to mute a specific call.
To do so the Mute request must contain the call unique ID – ivrid.
The call ID can be found in real time by using:
1. Real-time API
Real-time API provides real-time events of calls and call status changes as well
as user status changes in your organization.
One of the real-time events parameters is “ivrid”.
2. Active call API
Active calls API can be used to get the details of every active call upon
request.
One of the active call parameters is “ivrid”.
URI
https://monitor1.voicenter.co/api/MuteUnmuteCalls?ivrid=XXXXXXXXXXXXXXXXXXXXXXX&state=1
Acceptable request types
1. POST-JSON
2. GET
Possible Response formats
1. POST-JSON
Client Request Parameters
| Field name | Description | Type | Remarks |
| ivrid | Unique ID of the call. | String | Mandatory |
| state | 0 – Unmute. 1 - Mute. | String | Mandatory |
Client Request Example (GET)
https://YOUR_MONITOR.voicenter.co/api/MuteUnmuteCalls?ivrid=XXXXXXXXXXXXXXXXXXXXXXX&state=1
Client Request Example (POST-JSON)
Voicenter Response Parameters
| Field name | Description | Type |
| ErrorCode | Describes the status of the client reqeust. The status 200 will indicate a succesfull reqeust. | Integer |
| Message | Response status description. Response status description: "Success" – No errors. "UniqueIvrID not found" - The Code value or format is invalid. "Parameters are not valid, should be \"ivrid\" and \"mute\" - The sent parameters are invalid. | String |
| ActionID | Unique ID of the action perfromed. | String |
Voicenter Response Example