Version 6.4 437 March 2012
SIP User's Manual 20. Configuring the IP Media Parameters
20.1.2.3.1.5 Using Proprietary Scripts
You may use cgi or servlet scripts released with the version for recording to a remote
HTTP server using the POST or PUT method.
20.1.2.3.1.6 Dynamic HTTP URLs
Voice streaming supports dynamic HTTP URLs. The following terminology is used:
Static audio content: Traditional audio file URLs containing references to specific
files (.wav, .au or .raw). For example: http://10.50.0.2/qa/GOSSIP_ENG.wav
Dynamic audio content: URLs referencing to cgi scripts or servlets. For example:
http://10.50.0.2/cgi/getaudio.cgi?filename=DEFAULT_GREETING.raw&offset=0
In the case of dynamic URLs, the device performs the GET command with the supplied
URL and as a result, the servlet or cgi script on the Web server is invoked. The Web server
responds by sending a GET response containing the audio.
The URL format can be as follows (RFC 1738 URLs, section 3.3):
http://<host>:<port>/<path>?<searchpart>
where,
:<port> is optional.
<path> is a path to a server-side script.
<searchpart> is of the form: key=value[&key=value]*
Note: At least one key=value pair is required.
Another example of a dynamic URL is shown below:
http://MyServer:8080/prompts/servlet?action=play&language=eng&file
(See also RFC 2396 URI: Generic Syntax.)
The servlet or cgi script can respond by sending a complete audio file or a portion of an
audio file. The device skips any .wav or .au file header that it encounters at the beginning
of the response. The device does not attempt to use any information in the header. For
example, the device does not use the coder from the header. Note however, that the coder
may be supplied through Web or ini file parameters.
20.1.2.3.1.7 Play LBR Audio File
You may play a file using low bit rate coders for .wav and .raw files.
Note: This feature is relevant for both NFS and HTTP.
To Next Page
Loading...
