Help center support eXpress
We've collected answers to popular questions to make eXpress easy and convenient to use. Didn't find the answer to your question? Contact our support team.
- Welcome to eXpress
- eXpress Support
- Introducing eXpress & Glossary
- About eXpress
- eXpress Federation Architecture
- Glossary
- Installation & Updates & Requirements
- Registering & Logging In
- User Profile
- Chats, Channels & Threads
- Contacts
- Tags & Tabs
- Files
- Calls & Conferences
- Push Notifications & Counters
- Fixing Background Work on Mobile
- Bots & SmartApps
- Diagnostics & Logs & Cache
- Admin Panel
- Jira Support Portal
- Technical Support for Admins
- Database Modifications Policy
- eXpress Documentation
- Privacy Policy
eXpress Federation Architecture
- Regional Transport Server, RTS
- Corporate Transport Server, CTS
- Enterprise Transport Server, ETS
- Server Interaction in the Federation
Corporate and public servers are united in the common eXpress federation:
What is the eXpress Federation?
It's a network of regional and corporate eXpress servers. It includes all public regional (What Does the Federation Offer?
Within the federation, users of different organizations can:
- Exchange messages and files
- Schedule conferences and calls
- Interact with users from other companies
Regional Transport Server, RTS 
It is a public cloud server. In eXpress, RTS affiliation is indicated by green icons for contacts and servers.
For Administrators: Purpose & Features of RTS
Purpose of RTS
- Global routing of messages between all members of the federation (both corporate and external users) in any apps;
- Initial user registration on RTS,Lite,CTS(including working with SMS codes), and guest profiles;
- Sending push notifications to eXpress client apps for RTS,Lite,CTSusers.
Features of RTS
- There are several such servers located in Russia at the disposal of the eXpress vendor.
- You can register on RTSfor free via personal non-corporate account in eXpress, but the app's capabilities will be limited in such case.
Who Administrates the RTS?
Server-side administration is handled by eXpress support.Corporate Transport Server, CTS 
- Litecorporate server is aCTScorporate server with limited functionality.
- A corporate server that follows ETSinstead ofRTSis calledeCTS.
For Administrators: Purpose & Features of CTS/eCTS
Purpose of CTS/eCTS
- Authentication of corporate users and guest profiles (if configured);
- Routing and storing files and messages of corporate users;
- Corporate phonebook;
- Direct interaction with other corporate servers (of this organization or a partner organization);
- Other functions for corporate communications (conferences, bots, etc.).
Features of CTS
- CTSprovides basic messaging functions within an isolated, secure corporate network. Employees of the organization need to register on the corporate server to communicate with each other.
- All CTS(andLite) servers are connected toRTSdirectly and use it for registration and sending push notifications.
- An organization may have several corporate CTSservers, and trusted connections (trusts) can be established between them. Users from one trust server can search for users from another, and traffic is routed directly between trust servers, bypassing the intermediateRTS.
Who Administrates the CTS?
Server-side administration is handled by your organization support, or by partner, or by paid eXpress technical support.Can a Regular CTS Be Disconnected From the Federation?
Isolated operation ofEnterprise Transport Server, ETS 
For Administrators: Purpose & Features of ETS
Purpose of ETS
- ETStakes over the functions of the publicRTSserver for the branded app;
- Routing of messages between users, allowing employees of one eCTSto communicate securely with employees of anothereCTS;
- Initial registration of users within the organization’s contour (including working with SMS codes);
- Sending push notifications to branded client apps within the organization.
Features of ETS
- ETSinstallation occurs exclusively within the organization's perimeter.
- The organization independently manages security policies and contour access.
- Customizable initial registration of users within the organization’s contour.
- Users are connected to ETSusing a dedicated ETS client app, which is distributed by the organization. It's code can be additionally pre-checked before publishing to app stores.
- Users can not stay on the ETS, it is required to register on eCTS.
- RTSusers can register on theETSclient app. If the user was a corporate user in eXpress, a logout is required, otherwise an error is displayed.
- Users' phonebooks are stored on ETS.
- ETSis independent ofRTS, but is linked toRTSby default so thatETSapp users could communicate with RTS and otherCTSusers. NeweCTSare created onETS, andRTS“does not know” about them. Autonomous operation ofETSin complete isolation is also possible.
Who Administrates the ETS?
Server-side administration is handled by your organization support, or by partner, or by paid eXpress technical support.Server Interaction in the Federation 
Below is a brief summary of how servers interact within the federation, with references to the relevant FAQ articles.
What Unites Servers in the Federation?
- Routing of messages, files, and calls. RTSacts as a global gateway for all types of traffic between non-trustCTSand for traffic to/from public users.ETSperforms a similar role inside an enterprise's “mini-federation” for itseCTSservers.
- End-to-end user identification using HUID, provided by RTSorETS.
- Trusted connections (trusts). A trust connection can be established between a pair of corporate servers (CTS/eCTS— from the same or different organizations). Trust servers enable direct traffic exchange bypassingRTS, trust search for users, and extended permissions for invitation links and files from within the corporate network (CDTN).
For Administrators: How to Manage Trusts
Management is performed by the administrator on the Trusts tab in the admin panel.CTSeCTS - Distributed storage of chats and files. Each interserver chat/channel, interserver calls and conferences recordings, and shared files are replicated to the servers of all participants — see “Storage and Deletion of Chats” and “Files”. This also explains the visibility of history when adding a new participant from a “fresh” server — see “Chat History”.
- Isolated ETSdoes not participate in the common federation: its users cannot see users fromRTS/CTS/otherETSservers, and vice versa — see the definition of “Isolate”.
- Emergency mode of a corporate server when the root server is unavailable disables trust connections and interaction with external users — see details below.
- eXpress global chat is the only system chat that comes from RTSto all federation users; the administrator of a specific corporate server can disable it locally — see “Global Chats”.
For Administrators: How to Configure My Server to Operate in the Federation?
CTS
ETS
eCTS
Details on administering trusts, network perimeter restrictions, and links with public / corporate / trust access levels can be found in the admin panel FAQ.
For Administrators: Corporate Server Emergency Mode When RTS Is Unavailable
Lite
CTS
eCTS
If | App Function | CTS Lite |
eCTS (non-isolated ETS ) |
|---|---|---|
| Registration and login of new corporate users | Not working (current sessions remain active) | Working, but a synchronization queue with the federation builds up |
| SMS code verification | Not working | Working |
| Push notifications | Not working | Working (except when push notifications are proxied through RTS ) |
| Synchronization of user public keys | Not working | Working, but a synchronization queue with the federation builds up |
| Trusted server connections | Working as long as authentication tokens are valid | Working |
| Creating chats, calls, and conferences | Working as long as authentication tokens are valid, but only with users from this server and trusted servers. Guests must be created on this server — more details. | Working, but only with users from this server and trusted servers. Guests must be created on this server — more details. |
| Server contact directory | Working as long as authentication tokens are valid, but becomes outdated over time, and users from other servers start showing as "Unknown User" | Working, but becomes outdated over time, and users from other servers start showing as "Unknown User" |
- CTS/Liteserver does not support fully autonomous operation without a connection toRTS— access must be provided on both the corporate server side and the client side.
- eCTSserver in the federation (under a non-isolatedETS) can operate without a connection toRTSfor a certain period of time.
- eCTSserver under an isolatedETSnormally operates without a connection toRTS.
How Does Traffic Flow in an Interserver Chat/Call?
| Participant Composition | Route |
|---|---|
| Single server ( CTS /eCTS ) |
Local only on the server |
| Only trusted CTS /eCTS |
Directly between servers, bypassing RTS |
| Non-trust corporate servers | Via RTS |
| At least one public (external) user | Via RTS |