...
This article describes how a Meridix Studio installation is connected against a Telepo BCS installation both regarding retrieval of CDR (Call Detail Record) information through the Telepo Web API and how the catalog synchronization is handled. This is the default "off-the-shelf" way of handling the integration but the handling can be customized if a customer has special requirements.
...
No Meridix software needs to be installed on-site, the only requirements is that the management-node and the servicenodes is accessible from the Meridix off-site server and that Meridix has valid tickets and tokens for each of the required API operations.
Requirement | Reason | Notes |
---|---|---|
IP address to the Management node Administration API. With access rights from the Meridix off-site server. | To allow catalog synchronization (organizations, user ids, function numbers) | Access can be granted through IP access rules or through a VPN connection. |
API Ticket (token/secret) with rights to access the administration API methods. | To be able to sign the requests. | |
IP addresses to the Service nodes CDR API. With access rights from the Meridix off-site server. | To allow retrieval of CDR information (call logs) | Access can be granted through IP access rules or through a VPN connection. |
System token for each service node. | To be able to make the CDR API calls. | |
Organization domain to org id mapping | To be able to add the missing mapping between the CDR logs and the catalog data. | This is optional since it can be handled manually but its recommended that its automated to minimize errors. |
The following information should to be supplied to Meridix.
Type | |
---|---|
The management-node IP addresses HA, Primary and Secondary | IP addresses |
System ticket | Ticket (token and secret) |
The servicenodes IP addresses (HA, Primary and Secondary) | IP addresses |
Service node system ticket (one for each service node) | Tickets (token) |
Information about mapping | (depends on customer preference) |