CounterPath Bria 3.0 Configuration Guide – Retail Deployments - Manual (Page 19)

Bria 3 Configuration Guide – Retail Deployments
15
2.10 Feature Enabling: Enabling Other Features
Other features are enabled and configured through other settings. See:
• “File Transfer” on page 15
• “Directory” on page 12
• “MWI Notification” on page 16
• “Presence” on page 18
• “Voicemail: “Send to Voicemail”” on page 20.
• “User Experience” on page 19.
2.11 File Transfer
File transfer lets users send and receive files. .
To use XMPP for file transfer, both the sender and the recipient must have XMPP accounts and the local user
must be subscribing to the recipient’s presence through the XMPP account. In addition, both sides must be
enabled for XMPP file transfer.
To enable XMPP file transfer on the local client, set feature:file_transfer:enable to true.
XMPP file transfer is direct if a peer-to-peer connection exists between the two sides. If such a connection is
not possible, then the transfer is sent via the XMPP proxy that the XMPP service provides or via the public
server proxy.jabber.org.
2.12 License
Provisioning the License
The license key can be provided to the client through remote provisioning. See “Provisioning Bria OEM
Edition” for details.
Or the key can be provided to the user outside of Bria, through an e-mail, for example. In this case, the user
chooses Help > Enter License Key to display the Enter License dialog.
Revoking Licenses
Whether you provision licenses or users enter the license key manually, you can manage licenses by logging
onto your account on the CounterPath store.
Note that to revoke a license, you must do so through the store. It is not enough to remotely provision an empty
license key string the next time that the user logs on, because after the initial provisioning, the key is stored
outside of settings and Bria reads it in that outside location.