When a new event if fire the object item arrives to the trigger class and it can have different variables and values according to is type.
| variable | description |
|---|---|
| odbc_ | prefix variable to get results from odbc query, usage in condition variable odbc_name; usage in action: ${odbc_name} |
| http_response_code | prefix variable to get results from http action when the response is a code |
| http_response_body | prefix variable to get results from http action when the response is a body |
| http_json | prefix variable to get results from http action when the response is a json string, usage in condition variable http_json-name; usage in action: ${http_json-name} |
| variable | description |
|---|---|
| class_name | the class name where to fire the event |
| sensor_name | the sensor name, for example, endpoint |
| event_name | the event name fired |
| profile_name | when a endpoint the SIP profile where the event was triggered |
| account_name | the directory account name |
| account_description | the directory account description |
| domain_name | the directory domain name |
| network_ip | the network ip from where the event was received |
| network_port | the network port from where the event was received |
| user_agent | the user agent from where the event was received |
| variable | description |
|---|---|
| class_name | the class name where to fire the event |
| sensor_name | the sensor name, for example, line |
| event_name | the event name fired |
| line_name | the line name |
| status | the line status |
| status_txt | the line status text |
How to alert a line register/unregister/ping_up/ping_down: At the start you need to modify the default sip line template: Telephony → General → Line → default sip line
Then go to Monitor → Trigger → Add new class
How to alert an account register/unregister/expire:
You can create a trigger to be alerted of register, unregister and expire on SIP accounts. At the start you need to modify or create a SIP template:
Directory > Template > Endpoint (SIP) > Add
Monitor > Trigger > Add a new rule
Configure the action to execute when the trigger condition is met.
Adding a trigger rule that sends an automatic email, one per hour, if a ping type probe reports 100% packet loss:
Messages-Waiting: yes
Message-Account: sip:100@commsmundi.com
Voice-Message: 3/0
Adding a trigger rule that check status as account 'example' in odbc query:
Adding a trigger rule that check response of the query and send one email to responsable:
Check if this class has custom event key enabled, for example 123. Then use a URL like this with your respective data: 192.168.10.156:1080/mon/event.php?sensor_name=in&key=123&account=304