Installation guide

Customization, Troubleshooting, API and Logs
Acano solution: Deployment Guide R1.2 76-1006-06-K
Page 58
11 Customization, Troubleshooting, API and Logs
11.1 Customization
From Release 1.1 you can customize the Acano solution in a limited way (which will be
expanded in future releases). Currently you can customize the WebRTC Client login page. See
the Appendix K for details.
11.2 Diagnostics and Troubleshooting
The Acano solution’s diagnostic and troubleshooting logs can be spooled to a Syslog server to
allow a larger amount of data to be collected for troubleshooting, therefore Acano requests
access to a suitable Syslog server for this purpose. If you do not have a Syslog server available
we suggest installing solar winds’ kiwi.
It is also possible to enable additional SIP tracing using the Logs > Call Diagnostics page in
the Web Admin Interface. These logs may be useful when investigating call setup failure issues
for SIP endpoints and should be disabled at all other times. To prevent the verbose logging
being enabled for longer than necessary, it automatically shuts off after a choice of 1 minute, 10
minutes or 30 minutes.
Refer to the Acano Support FAQs on the Acano website for more troubleshooting information.
11.3 Application Programming Interface
The Acano solution supports an Application Programming Interface (API). The API uses HTTP
or HTTPS as a transport mechanism and is designed to be scalable in order to manage the
potentially very large numbers of active calls and coSpaces available in the Acano solution.
The API includes LDAP server access methods for adding, configuring and modifying LDAP
servers and support for multi tenancy for search calls through an additional Tenant ID. Other
additions include posting to coSpace message boards, the ability to filter the set of active call
legs to just those experiencing "alarm" conditions (for example, packet loss or excessive jitter)
and the ability to retrieve system-wide status values.
Multi-tenancy means that groups of users can be entirely segmented within the solution as
required by service provider deployments e.g. users will only be able to call, assign users to
coSpaces, and search in the directory within the same configured customer groups.
Refer to the Acano API Specification document for more details.
11.4 Call Detail Record Support
The Acano solution generates CDRs internally for key call-related events, such as a new SIP
connection arriving at the server, or a call being activated or deactivated.
The Acano solution can be configured to send these records to a remote system to be collected
and analyzed. There is no provision for records to be stored on a long-term basis on the Acano
solution, nor any way to browse CDRs on the Acano solution itself.