Sends a log file specified by the parameter.
Service Pre-requisites
The service requires the JSESSIONID obtained in the Log In Service.
Service Invocation
An HTTP GET or POST method must be addressed to the following URL:
http://<server>:8080/callrec/sendlogfile
Input Parameters
The service expects to receive:
- The previously obtained
JSESSIONIDto identify the user in the form of:- A cookie
- An append to the URL immediately after the servlet name, as follows:
jsessionid=<sessionid>
- The
sendLogIdxlog ID parameter
| Log File ID | Log File Name |
|---|---|
0 | core.log |
1 | audit.log |
2 | rs_eth1.log |
3 | rts_jtapi.log |
4 | ds.log |
5 | web.log |
6 | webadmin.log |
7 | genesys.log |
8 | screenrec.log |
9 | mixer.log |
10 | naming.log |
11 | msgs.log |
12 | configmanager.log |
13 | rmi.log |
14 | ipcc.log |
15 | ipccex.log |
16 | prerecording.log |
17 | rts_skinny_1.log |
18 | rts_sip_1.log |
19 | slr.log |
20 | instreamer.log |
21 | tools.log |
22 | migration.log |
Tip: One method of discovering the log file IDs for a Call Recording installation is by viewing the JavaScript log file links in the Web GUI (Settings > Logs). For example, the link for core.log is: javascript:changeLog(0, 'core.log'), where 0 is the log ID.
Output
The specified log file is returned in a .zip archive named in a similar manner to the log file itself, for example: core_log.zip
Request a Log File with the Send Log File Service Example
With Firefox:
Enter the following URL into the browser to download the audit log file, after first logging in using the Log In Service step above:
http://<server>/callrec/sendlogfile?sendLogIdx=1
The server will respond by sending the log file in a zip, triggering the browser to display the file open/save dialog.
With cURL:
Use the following command, after first completing the Log In Service step above:
curl -v -b cookies.txt -c cookies.txt -X POST -d "sendLogIdx=1" -H"Content-Type: application/x-www-form-urlencoded" \ -H"Accept: application/octet-stream" -o audit-log.zip http://<server>/callrec/sendlogfile
The server will respond by sending the log file in a zip:
* About to connect() to myserver port 80 (#0)
* Trying 10.0.0.1... % Total % Received % Xferd Average Speed Ti
me Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0co
nnected
* Connected to myserver (10.0.0.1) port 80 (#0)
> POST /callrec/sendlogfile HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18
> Host: myserver
> Cookie: JSESSIONID=8A355EC61B5D804447704B8CB64DF535
> Accept: */*
> Content-Length: 12
> Content-Type: application/x-www-form-urlencoded
>
} [data not shown]
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Disposition: attachment; filename=audit_log.zip
< Content-Type: application/zip;
< Transfer-Encoding: chunked
< Date: Wed, 15 Jun 2011 13:46:56 GMT
<
{ [data not shown]
100 301k 0 301k 0 12 644k 25 --:--:-- --:--:-- --:--:-- 666k
* Connection #0 to host myserver left intact
* Closing connection #0
See the description of the Send Log File Service for more details about log file IDs.