Datasheet

Acano X Series Server and Virtualized Deployments
Acano Solution R1.6: Support FAQs 76-1022-08-K
Page 19
If users are not imported, try the following:
4. If possible, delete all LdapSources through the API, configure these sources using the Active
Directory Web interface, and then check if users are imported when synchronizing.
5. If first method is not possible, modify the filter to be a simple one; for example,
“objectClass=person” and try to import users from an OU. This will confirm that the issue is
with the filter.
I cannot log in using an Acano client in a deployment with separate Acano
Core and Edge servers because authentication fails. What should I check?
The first thing to check is that the appropriate ports are open on both firewalls:
 External to DMZ firewall
 DMZ to Internal firewall
See Appendix B of the Acano solution Deployment Guide for a full description of the Acano
solution’s port requirements. The document is available from the Partner web site.
I suspect a firewall issue stopping WebRTC. Can I check this?
In a browser type https://apprtc.appspot.com/. Then open another tab, and type
chrome://webrtc-internals/ which will show ICE information.
Why isn’t a coSpace Call ID dialable?
A feature of the Acano Call Bridge is that it supports one or more dial in PSTN phone numbers
for the IVR, and also supports connections via the Web Bridge. In both of these cases, to be
able to join a coSpace you need to enter the ID for the coSpace that you want to join.
In a multi-tenant environment, it is not possible to determine which tenant you are calling from
(or connecting from) in these cases. This means that the call ID you use has to be unique on the
Acano Call Bridge so that the coSpace does not clash with any other coSpace for any
configured tenant. Dialable IDs (URIs) for coSpaces aren't as restricted because the domain of
the URI determines which tenant the call is for: multiple tenants can use "test.cospace" for
example, because this might be dialed as "[e-mail]" for one tenant and
"[e-mail]" for another tenant.
I want Acano users to be able to enter a +E.164 number and no @domain
suffix to dial out, how can I configure the Acano dial plan to do this?
Enter a “match all” dial plan rule. Assuming that all of your current outbound dial plan rules have
a domain entered, enter one additional rule with the lowest priority with nothing in the Domain
field. This creates a “match all domains” rule.
Set it to the IP of your proxy server. For example if the “match all” rule is set to use 10.10.20.20
as the SIP Proxy to Use and the user dialed 12345, the call would go out to that proxy as
12345@10.10.20.20. How the proxy then handles the call is outside the scope of Acano.