Interactive Voice Response SIP UserAgent (ivr)
Description
SIP-calls auto-service service using administrator’s preconfigured IVR-scripts. Also provides call initiation functionality from within the system.
Reserved and scaled in mode Active-Active.
Code |
|
Mode of operation |
|
Backup mode |
|
Types of sites |
|
Layer |
|
Placement |
|
Saving and restoring state on reboot |
|
appendix |
|
Parameters
Name | Type | Default | Description |
---|---|---|---|
|
|
required |
Name. May consist of Latin letters and numbers, must begin with a letter. |
|
|
required |
Role Type. Possible values: |
|
|
required |
The alias of the server network interface on which the roles will interact internally with each other. |
|
|
empty |
Additional role options. Contains a json object or list. |
|
|
empty |
Role activity flag. When set to false, the role does not participate in validation and is not started. |
|
|
required |
Role ID. |
|
|
required |
An indication that the role has been allocated to a separate node. |
|
required |
Local UDP port for SIP. The same port handles both TCP. |
|
|
required |
Local TCP port for SIP. If a value other than UDP is specified, it will be raised additionally. |
|
|
|
Switch for logging events to log |
|
|
|
Media function logging switch |
|
|
|
Switch for logging the communication protocol with the MGC controller to the logger |
|
|
|
Switch for logging dialog state machine trace to logs |
|
|
|
SIP traffic logging switch to log |
|
|
|
Switch to apply media gateway role b2b for calls initiated by the current role instance ivr. |
|
|
|
Service Field. Using the Media Gateway by Role ivr. |
|
|
|
List of audio codec names used for call initiation (shoulder call).
The three basic formats, |
|
|
empty |
List of video codec names used to initiate a call (shoulder call). As a value, a list containing the names of video codecs in format
|
|
|
true |
Switch to downgrade the priority of local MG media gateways located on the same server as the currently active signaling server. |
|
|
empty` |
Enables the called party emulator mode. |
Configuration example
The configuration is managed in an application available to master domain administrators. The application hides the full content of the configuration, but it is nevertheless accessible via the API.
The configuration contains a section to describe all instances of all roles. Parameters are defined for each specific role instance.
{
"name": "ivr1",
"roletype": "ivr",
"iface": "eth0",
"roleid": 11270,
"separate": true,
"tcp": 5085,
"udp": 5085,
"log_cdr": true,
"log_trn": true,
"log_sip": true,
"log_media": true,
"log_mgct": true,
"b2bmedia": true,
"payloads_audio_offer": [
"PCMU/8000", "CN/8000", "G722/8000"
]
}