Call Log Stream FAQs

The following are frequently asked questions for the Call Log Stream feature.

Q: What is the Call Log Stream feature, and what does it do?

A: Refer to Call Log Streams for more information.

Refer to ECLE field names (Q & A) for more information about the complete field list.

Q: What is a WebSocket API?

A: First referenced in the HTML5 spec, WebSockets provide a full-duplex communication channel over TCP. Unlike the request/response pattern of API standards like REST or SOAP, WebSockets maintains a persistent connection where data is pushed. Refer to https://en.wikipedia.org/wiki/WebSocket for more information.

Q: How does Call Log Stream differ from Call Log Export?

A: The Call Log Export feature has a 1-1.5 hour delay, providing the same information as Call Log Stream, but in a CSV file delivered to S3. Call Log Export is ideal for traditional data warehousing and long-running analytics or queries. Whereas Call Log Stream was designed to provide real-time, fine-grained traffic data, mainly for operational views of traffic health and status.

Q: Can I create multiple channels?

A: Currently, one channel per customer is supported, and one token per channel can be active at any time.

Q: Do Call Log Streams work with the Distributed API Management Organizational Management feature (DAPI)? Can I create a channel exclusively for my organization?

A: No, currently, channels are Area-wide, and there is no organizational distinction.

Q: Who can set up a Call Log Stream profile?

A: Area administrators are the only people who have access to create channels or view the configuration.

Q: My connection to the Channel has disconnected. What do you recommend?

A: As a best practice, we recommend adding auto-reconnect to your client. There are many factors that may impact the stability of your connection, such as network issues and client issues. To overcome this, ensure your client library is updated to the latest version. You can utilize your preferred Java client sample or download the most recent ECLS Java client from here. Additionally, we have implemented the Ping-Pong feature of the WebSocket protocol, so that if you have a low-traffic set of APIs, enabling ping-pong on your client can prevent connections from shutting down due to inactivity.

Q: If the connection is disconnected, do I lose data?

A: The Call Log Stream feature does not currently queue data or provide an offset feature; therefore, you receive data when you are connected, and data that was in the stream when you were disconnected is not available.

Q: I am a Boomi Cloud API Management - Local Edition user; I have found that the logs in the Call Log Stream are not real-time. Is Call Log Stream compatible with Local Edition?

A: Call Log Stream provides call data in near real time from the moment the data is received in the Cloud API Management infrastructure. For Cloud API Management customers, we manage that delivery and can therefore control the delivery timeline. For Local Edition customers, latency is dependent on the frequency of log synchronization with Cloud API Management (SaaS). For customers on Local Edition 5.x, we recommend utilizing the Log Service in place of Call Log Stream for access to Call Log data.

Q: How many active connections per channel are allowed?

A: You can have up to five active connections per channel.