Page tree
Skip to end of metadata
Go to start of metadata
Introduction

Maxwell offer the sending of an Action URL on occurrence of predefined Events.

These Events are:

  • Registration succeeded
  • Registration failed
  • Connection established
  • Connection terminated
  • Off Hook
  • On Hook
  • Incoming call
  • Outgoing call

The Action URLs can be set via the Web-UI on the page Settings/Desk Phone/Events.

Furthermore there is the possibility to set the Action URLs for Events via provisioning.


Provisioning parameters
System.Events.RegistrationSuccessed
System.Events.RegistrationFailed
System.Events.ConnectionEstablished
System.Events.ConnectionTerminated
System.Events.OffHook
System.Events.OnHook
System.Events.IncomingCall
System.Events.OutgoingCall
Action URL using Programmable Keys

In addition to the above mentioned predefined events Maxwell offer the possibility to trigger the sending of Action URLs via Programmable Keys.

These keys are:

  • Messages
  • DND
  • Hold
  • Conference

The Action URLs can be set via the Web-UI on the page Settings - Desk Phone - Keys and LEDs.

Furthermore there is the possibility to set the Action URLs for Events via provisioning.

The parameters can be found here.

Action URL using Function Keys - Maxwell 3 only

In addition to the above mentioned predefined events Maxwell 3 offers the possibility to trigger the sending of Action URLs via Function Keys.

These Action URLs can be set via Web-UI on the page Settings -Desk Phone - Keys and LEDs.

Furthermore there is the possibility to set the Action URLs for Events via provisioning.

The parameters can be found here in the section Function Keys.

The Type is 8, a display name can be set and the URL is defined with the parameter "PhoneUI.Keys.FunctionKeys.X.URL".


Configuration

The request is basically a HTTP or HTTPS GET request.

Entry fields
"Action URL" incorporates two entry fields:

  • name
  • URL

Syntax
<URL>?value1=$parameter1&value2=$parameter2 ...
[ ? is the separator between URL and parameter part // & connects different parameter ]

Example for a call center sign in:
http://192.168.1.1/callcenter?ip_address=$ip_address&key=$active_key => http://192.168.1.1/callcenter?number=5025&key=4

Fixed Variables (Maxwell 3 Function Keys only)
These variables are fixed phone settings.

  • $mac_id [phone mac id]
  • $ip_address [phone ip address]
  • $fw_version [firmware version]

Runtime Variables (Maxwell 3 Function Keys only)
These variables are temporarily valid values and relates to the current situation.

  • $active_key [number of the pressed key]
  • $active_url [user and host part of an account which places or receives a call]
  • $active_user [user part of an account which places or receives a call]
  • $active_host [host part of an account which places or receives a call]
  • $url_remote [user and host part of the remote account which places or receives a call]
  • $display_local [display name of a local account which places or receives a call]
  • $display_remote [display name of a remote account which places or receives a call]
  • $callid [call_id of the current session]
  • $firstName [phonebook searchstring]
  • $lastName [phonebook searchstring]

* Authentication*
The "Action URL" function does not support authentication. If the device gets back a 401 message no authentication processing is started.
HTTP digest username and password is exclusive for provisioning.


Reason: Authentication would mean that each "Action URL" key needs an own authentication management.


  • No labels