Reference9:Gateway/CDR

From innovaphone wiki
Revision as of 09:48, 6 February 2019 by Slu (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
There are also other versions of this article available: Reference | Reference9 (this version)

The transmission of the so-called CDRs (Call Detail Records) is disabled as standard (Off). After selection of a CDR type, the transmission of detailed CDRs is enabled, as are the relevant entry fields. To prevent data loss in the event of failure of the first CDR server (CDR0), it is possible to specify a second CDR server (CDR1).

  • Off: CDR is disabled.
  • TCP: The device transmits the CDR entries via a TCP connection.
    • In the Address field, you enter the IP address at which the TCP connection is to be set up.
    • In the Port field, you specify the port to which the connection is set up.
  • SYSLOG: The CDR entries are transmitted to a syslog recipient (also referred to as syslogd, syslog server or syslog daemon ), which is then responsible for their further evaluation or storage.
    • In the Address field, you enter the IP address of the syslogd server.
    • In the Class field, you enter the desired message class that will be responsible for further processing of the CDR entries.
  • HTTP: The CDR entries are transferred to a Web server, where they can be further processed. Each individual CDR entry is transferred to the Web server in HTTP format.
    • In the Address field, you enter the IP address of the Web server that carries out further processing of the transmitted data.
    • Method:
      • Default: Use HTTP POST without Content-Type and send CDR as xml raw data in the request body
      • GET: Use HTTP GET and send the CDR as xml (URL-encoded) in the parameter msg (example: /cdr/cdrwrite.asp?event=syslog&msg=logmsg)
      • POST: Use HTTP POST with Content-Type: text/xml and send CDR as xml raw data in the request body. CDR Events will be send without Content-Type and contain the data URL-encoded in the body
    • In the Path field, you enter the relative URL of the form program on the Web server.
  • HTTPS: Same as HTTP, just a secure transmission(TLS) is used. Please read the wiki article on certificate management for additional information.
  • LOCAL:The CDR entries are transmitted to the local Compact Flash card. This will be place on the CF card where the CDR`s are stored \\Ipaddress\drive\CF0\log
    • In the Max File Size field (Kbyte) - you enter a size, if the current log file reaches this size the file is backed up and a new file is created.
    • In the Backup Time field (hour:min) - you enter the time of the day when the current log file should be backed up and a new file should be created (independent of the size).
  • LOCAL-AP:The CDR entries are transmitted to the local Linux application platform. Relay CDRs are stored under \\AP-IP\webdav\cdr\
  • REMOTE-AP:The CDR entries are transmitted to a remote Linux application platform. Store path is the same as under LOCAL-AP.
    • In the Address field, you enter the IP address of the remote Linux application platform.
    • In the Port field, you specify the port to which the connection is set up.
  • REMOTE-AP-S:Same as REMOTE-AP, just a secure transmission is used.