Installation • Configuration Pages:
Connection • Dial • Actions URL
<< Up | ### Actions URL | Page Index
Firewall Configuration

Action URL Settings
The snom phone can send these call events to a web server via Actions URL: incomming, outgoing, offhook, hangup, connected, disconnected (only snom 360) The TAPI driver contains a micro-webserver to receive these events. The snom 360 supports additional parameters like: "local", "remote" and "call-id". If these parameters are not supported by snom phone (e.g. snom 190), the TAPI driver will scan the log files to get the remote caller-address. The TAPI driver also scans the log files to detect "connected" and "disconnected" for snom 190. The scan interval is 1,5 sec. Hint: The TAPI driver clears the log file in some call states to minimize the data traffic and to avoid resulting speech gaps. Firewall:Firewall Configuration for micro-webserver TCP Port
Local IP Address | IP Address of your own computer (NOT the snom IP!). The micro-webserver will listen on this IP Address. This must be the same IP address like in: [snom web configuration > Actions URL.].
TCP Port | The micro-webserver is binded to this local TCP port. If port 80 is already occupied by a real webserver you can set another port like 88 or 8888. Hint: Firewall Configuration for micro-webserver TCP Port
State | State of micro-webserver; Active or Inactive; It may be "Inactive" if the TAPI line is closed.
Start | Click to [Start] button to start the micro-webserver manually. If an error occurs like "Initialization failed" you should try another TCP port.
Supported Actions URLs: | These Actions URLs are supported by the TAPI driver (micro-webserver).
Transfer Configuration to Snom | Click to this button if you want to transfer the "Supported Actions URLs" to snom phone. Hint: You have to set the connection parameters first, because these parameters are used to transfer the configuration by HTTP.
Open Snom Web Configuration | Here you can check if the configuration was transfered as expected.