Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The CDR data is made available for external systems by Telepo BCS through a HTTP based API. To get the CDR data a HTTP request is made against each of the services nodes CDR APIs. The request need to include a valid system ticket that is defined in the file /opt/servicenode/application/conf/cdr-pipelines.xml on each service node. (See Telepo document TelepoBCS_CDRs_3.6.xxxx.pdf section 7.2). This service ticket will be appended to the HTTP request that will return CDR information in the Response body as comma separated data (CSV).
Example of the HTTP request URL that is used:

...

Meridix has an application that makes these calls to each of the servicenodes from which CDR should be retrieved. The only technical requirement is that the servicenode IP address is accessible from the Meridix server (off-site). The access can be setup as a IP rule or through an VPN connection into the sub net where the Telepo service nodes reside. It is not recommended to make the servicenode publicly available from the outside.The servicenode IP used in the request should be the HA address of the service node because the Telepo system handles the routing to the correct server (Primary or Secondary).

Example of a valid section that defines the token in the cdr-pipelines.xml

Code Block
<system-tickets>
	<token>fsafghgdsfhjgfdjhvcir67iujytedrsf7eu65</token>
</system-tickets>

Meridix requires

Meridix needs to have access to each of the servicenodes IP addresses and have valid system tickets for each of them.
No Meridix software needs to be installed on-site.

...