CounterPath Bria Professional 2.5 Configuration Guide - Manual (Page 18)

CounterPath Corporation
14
2.9 Feature Enabling
This group of settings covers features that are enabled by only one or two settings. Features that need more
extensive configurationare covered in other sections in this manual: “File Transfer” on page 14, “LDAP” on
page 15, “MWI Notification” on page 16, “Presence” on page 18, “Voicemail: “Send to Voicemail”” on
page 20.
For other settings related to features, see “User Experience” on page 19.
2.10 File Transfer
File transfer lets users send and receive files. There are two ways to support file transfer.
Via Content Indirection
When content indirection is used, files are transferred to a content indirection server. At the same time, a
message is sent through a SIP IM session to the other party to provide the URL of the content indirection server.
Content indirection requires that the local user is subscribing to the recipient’s presence.
Configuring to Receive Files
For the local user to be able to receive a file transfer, feature:file_transfer_content_indirection:enable must be
true.
Configuring to Send Files
For the local user to be able to initiate a file transfer, the following configuration must be performed:
1. The setting feature:file_transfer_content_indirection:enable must be true.
2. In the presence-enabled SIP account, specify the URL of the content indirection server in the
proxies:proxyn:send_file_server setting.
3. Configure the content indirection server to allow the PUT HTTP method. If you have enabled WebDAV on
an HTTP server, then PUT is automatically enabled. (WebDAV may be used for remote storage; see
“Resources” on page 19).
4. Create the root folder on the content indirection server. This folder is part of the URL specified in the
setting proxies:proxyn:send_file_server. In order for the upload to the server to work, the root folder must
exist; Bria Professional will not automatically create it on the first upload.
Once this configuration is in place, then for content indirection to be possible from the sending side, the
recipient must exist as a contact with a SIP address and presence must be enabled for that contact. If the sending
side is set up appropriately, the transfer should succeed if the recipient’s client supports file transfer via content
indirection. The recipient’s client does not have to be configured for a content indirection server.
Via XMPP
When XMPP is used 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.