Scripting; Background - Snom 4S Administrator's Manual

Scripting is another fundamental concept of the snom 4S SIP
proxy. Although you don't need to write your own scripts, we explain the
concepts behind the scripting interface here so that you understand its
functionality though the rest of the document.
If you are not interested in scripting, you can skip this chapter.

Background

Using the script language of the snom 4S proxy, you can
customize the behaviour beyond the settings which are available on the
web interface.
There have been many proposals for defining the behaviour
of a SIP proxy. Proposals include generic approaches and SIP specific
approaches. Examples are CORBA, CPL, CTI, JAIN, Java Enhanced SIP
(JES), Java Servlet API, JINI, JTAPI, OSA-PARLAY, SIP CGI-BIN, TAPI,
TINA, TOPS, and VoiceXML. Looking at the http server history, we can
learn that simple scripting languages like perl or PHP found a broad
acceptance because of its simplicity, flexibility, stability and performance.
That was our motivation to integrate a PHP-like scripting language, even
if it is not a powerful as PHP4 is today.
Apache offers handling of domains and URLs. While the concept
of domains has been adapted in the proxy, it does not make sense to
define a script for every URL the proxy can handle. Therefore, we decided
to bind the script to the domain only.
The proxy loads a default script during the start process and
defines a number of functions. These functions are used unless overwritten
by domain specific functions. The function overriding is done within the
scope of a domain so that you can specify a completely different behaviour
for different domains. This is helpful if you are operating a number of
separate domains (e.g. as ITSP) or if you want to separate a productive
system from a test system.

Scripting

snom technology AG • 33