Lines are combined into groups. The properties of a group apply to all lines in the group.
Settings for declining calls
In many cases, the wide variety of configurations possible for telephone systems necessitates settings in UCServer which determine whether or not calls should be declined, and if so, how.
Note: The SIP responses and numbering in parentheses (e.g. "Decline (603)") listed below correspond to the RFC3261 definition for SIP (Session Initiation Protocol) and are therefore not translated in menus.
- Client not logged on or on Call Protection
If no client is logged into UCServer or the line is set to Do Not Disturb (DND), calls are automatically answered server-side. This option offers a choice of SIP responses for the UCServer to answer incoming calls.
The default setting is "Busy Here (486)" and signals "busy". Other possible settings include "Temporarily Unavailable (480)", "Decline (603)" and "Ringing (180)", i.e. instead of being declined, the call is placed in a "Ringing" state until the caller hangs up or the call is forwarded or "picked up" by another participant.
This setting applies only when no call forwarding of the type "Forward calls on logged off ProCall" is set for the called line at the ProCall client and when no administrative call forwarding is assigned.
- Reject calls by clients
If calls are being declined by clients, this selection of SIP responses can determine how they are declined, or how a decline is emulated.
The default setting is "Busy Here/Decline (486/603)". Depending on the situation, the client can choose to decline the call using either "Busy Here" or "Decline".
Fixed selection options are "Busy Here (486)", "Temporarily Unavailable (480)", "Decline (603)" and "Ringing (180)", i.e. instead of being declined, the call is placed in a "Ringing" state until the caller hangs up or the call is forwarded or "picked up" by another participant. The client is "unaware"of this; it is normally separate from the call, while the "Ringing" state is maintained on the server.
The server setting is used for fixed selection options, regardless of the client. For example, if the client sends a "Decline" to decline a call and the server is set to "Busy Here", the call is answered with "Busy Here" as well.
- Hide Decline button in client
Depending on each case, it may make sense not to give a client user the ability to reject the call via the Decline button. If this option is set, the Decline button is hidden when calls are made to the client (default: option not set).
Administrative call forwarding
- With logged off client, forward calls to 'voice mailbox'
If a phone number is assigned to the 'voice mailbox' field of the user, all calls are forwarded there if no client is logged on to UCServer. In this case no phone calls are automatically declined server-side, since the configuration setting for declining calls if no client is logged on is not applied.
Settings for call forwarding
This menu item is not displayed if a telephone system has the SIP feature '302 Removed' (also known as 'Call Deflection').
- Forward calls through
If incoming calls should be forwarded before the call is accepted (e.g. in case of call forwarding) even though the telephone system does not support this, this functionality can be provided through UCServer.
<Forward calls by making new call>
In case of an incoming call, UCServer places a new call to the called party and remains active during the call (Call Bridge).
In this type of forwarding, many telephone systems do not display the caller's telephone number to the party being called, but rather the number of the party being forwarded. In such cases, the option <Forward calls by answering, holding and transferring> can help.
<Forward calls by answering, holding and transferring>
The incoming call is being answered, held and transferred via SIP refer (Blind Transfer).
Until the called party accepts the call, the caller will hear the on-hold music configured in the telephone system as the call is being forwarded.
Please note with this selection that if a forwarded call is refused by the client, the caller stays on hold until he or she hangs up. However, this behavior is also dependent on settings and on the type of telephone system.
- Activate journal for all lines
Every call is written to the journal database for all the line group's lines.
Line phone numbers and names
- Set phone numbers automatically
Phone numbers are automatically generated from the SIP Registration. If this option is deactivated you can configure the phone numbers manually in the line details properties.
- Group location
Defines a Location for all lines in a line group. In addition to location selection, the following options may also be configured:
Permits assignment of different locations in the line properties for each line.
The UCServer automatically determines the line's location based on the phone number. This setting only works if the line can be assigned to a location via the extension number. Line phone numbers here must be transferred from the SIP Registration, i.e. automatically set (no manual assignment of line phone number).
Line group properties - Functions
Here you can configure advanced settings for certain functions.
- Activate/deactivate functions:
-If you deactivate a function, it will never be offered irrespective of the status of the call.
- If you activate a function, it will be offered accordingly if permitted by the status of the call.
Line group properties - Feature codes
Here you can configure advanced settings for certain functions.
Line group properties - Media
- Feature codes
Here is where you can store the telephone system's CTI feature codes which are offered in the estos ProCall line menu if no telephone calls are being made on the corresponding line.
Every Feature Code consists of a name, displayed in the line menu, and a code which is dialed on the telephone system when the user clicks the Feature Code. If a ProCall Feature Code is clicked, a softphone conversation window opens. Many telephone systems acoustically signal (e.g. via the headset) the success or failure of an action. Other telephone systems just hang up with no acoustic feedback after dialing the feature code. Please refer to your telephone system manual for available feature codes and acoustic signals.
- Pickup feature code
Allows a feature code to be configured in order to perform a pickup. The code must contain "<NUMBER>" for the number of the line from which a call is to be picked up. Example: *59<NUMBER>.
Clicking on the ProCall pickup function will open a softphone conversation window to carry out the pickup conversation.
Here is where you can configure advanced media settings for softphones. UCServer includes a media server, which is connected to the PBX on one side and to the ProCall client on the other side. The media server is used to convert data (media streams) into the correct format (e.g. codecs, encryption). Active audio codecs are listed at the top based on their priority, if more than one codec should be provided. To change the priority of a selected codec, change its order using the appropriate keys.
This setting is available depending on the connected telephone system and should only be changed after consulting with the estos ProCall Support.
- Audio codecs - PBX direction
Codec priority should correspond to the settings in the PBX. PBXs typically offer at least one G.711 codec (default, aLaw or uLaw variant). G711 has a constant bit rate of 64 kBit / s and provides good call quality. The uLaw variant is generally preferred by the PBX in North America and Japan, and aLaw is generally preferred in the rest of the world.
- Audio codecs - WebRTC direction
The ProCall client normally communicates with the media server in a WebRTC-compatible format (e.g. encryption via DTLS-SRTP).
The media server requires the least computing power when the same setting (e.g. 'G.711 aLaw') is used to the PBX and correspondingly towards the WebRTC (i.e. to the ProCall client).