Datasheet

Acano X Series Server and Virtualized Deployments
Acano Solution R1.6: Support FAQs 76-1022-08-K
Page 16
What the Acano solutions sends to Lync is a function of what video we have to send to Lync and
what Lync client says that it wants to receive. Lync sends us “Size Hints” during a call that tells
us what it wants to receive: if it is telling us to only send 640x480, the Acano solution must obey
this.
With Lync 2013, you will only get 720p if the Lync window is full-screen. If opened as small
window or even Maximized, it will only tell us to send 4x3 resolution @ 640x480. Therefore for
HD ensure that you have clicked the Full Screen button.
Also, only in Lync 2013, screen resolution can make a big difference. In most cases with Lync
2010, we can get 720p on most Full Screen calls as long as the screen is set to a resolution of
1280x720 or greater. However, in Lync 2013 and using the same PC, it has been observed that
screen resolutions of 1280x800 or higher are required to get the Lync client to request 720p in
calls.
Why do I need the UDP port range 50000-59999 open across the firewall for
calls from a Lync client when using the Acano solution?
Lync clients have the ability to send media to the Lync Edge server over a TCP connection to
port 443 or over UDP in the 50000-59999 range. However, the Acano solution only supports
UDP for audio and main video (because this is preferable to TCP for several reasons). Therefore
the ports need to be open to allow the Lync client to use UDP.
Can calls between SIP endpoints and Lync users be hosted on the Lync
AVMCU?
In R1.6, multipoint calls between SIP endpoints and Lync users can be hosted on the Lync
AVMCU, using the Acano server as a gateway. No special configuration is needed; just the
standard Lync integration configuration working as detailed in the Acano solution Deployment
guides. If you want to use this setup for external and federated Lync users also, you must
enable the Lync Edge Integration and make sure that you set up Lync Federation correctly, and
open the correct UDP and TCP ports for that as described in the Ports Used appendix of these
Deployment guides.
Should I see the LDAP server configured on the Web Admin Interface in the
API?
The Web Admin Interface-configured LDAP server works slightly differently to those configured
via the API, and is only recommended for simple deployments and testing. If you are interested
in multi-tenancy then we recommend that you remove the configuration from the Web Admin
Interface Configuration > Active Directory page and use the API to configure LDAP imports.
From R1.1 can use either the API or the Sync now button at the bottom of the Configuration >
Active Directory page to synchronize the LDAP servers.
How do I import a security group from the Active Directory server using the
API?
1. Create a security group on the Active Directory Server and add some users to the group.
2. On the Directory information tree structure, create ldapServers, ldapMappings and
ldapSources using the Acano solution API. (See the API Reference guide for details.)
When posting ldapSources, a POST URL format has to be used: see the following example.