ProCall Enterprise known problems and limitations
State of knowledge
23 September 2024
Unfortunately, we cannot make any statements about a date on which the topics mentioned here will be corrected or changed. However, we will mark topics that are already in progress or indicate the version in which a correction or change has been made.
If the following known problems and limitations could lead to a high level of customer dissatisfaction or loss of reputation for one of your customers and no solution or agreement on further steps could be reached despite serious efforts, it is possible to change the status of the support ticket to "Escalation". By doing so, the attention of estos' management is focused on the case.
ProCall 8 Enterprise
ProCall 8 Enterprise from version 8.0.0 was released at the same time as ProCall 7 Enterprise from version 7.6.0.
This means that all issues marked as solved here in versions lower than 7.6.0 are also solved in any ProCall 8 Enterprise version.
General
| Reference | Description | Affected versions | Status |
|---|---|---|---|
| PROCALL-2887 | The UCServer service cannot connect to UCConnect or the push service if it is only allowed to establish an internet connection via a web proxy (with user authentication). For this constellation, an exception must be defined in the infrastructure that the UCServer is allowed to communicate unhindered with the UCConnect services. | >= 8.0.0 | RESOLVED (8.1) |
| PAIM-1461 | After adding licenses in the UCServer, some TAPI lines are not opened automatically. | >= 7.0.0 | RESOLVED (7.0.1) |
PAIM-1536 PROCALL-660 | The permissions of the public permission level does not correspond to the online help. | n.a. | RESOLVED (7.2.3) |
| RTCSP-1455 | ProCall Softphone does not support Early Media. | >= 6.4.5 >= 7.0.0 | RESOLVED (7.1.2) |
| CTIPBX-90 | On TAPI lines no consultation is possible via the call window. To establish a consultation call, a 2nd call must be placed. | >= 7.0.0 | RESOLVED (7.0.1) |
| PAIM-1626 | Access violation to local directories may occur when updating the media server. | >= 7.0.1 | UNSOLVED |
RTCSP-505 | If there are interruptions in the media data stream between client and media server (e.g. when switching from Wifi to the mobile data network or in case of network interruptions in the mobile data network), it can no longer be reconnected automatically. | >= 7.0.0 | RESOLVED (8.1.0) |
| PAIM-1676 | Permissions between users overwrite permissions that are assigned globally or via groups. | >= 7.0.0 | RESOLVED (7.0.3) |
| PAIM-1727 | No more than about 6 monitor groups/keys can be administratively configured if no schema extension is used for AD connection. | >= 7.0.0 | RESOLVED (7.0.1) |
| RTCSP-1714 PROCALL-773 | The media server of the UCServer does not support TURN over TCP [Externer Link: https://tools.ietf.org/html/rfc6062]. | >= 7.0.0 | UNSOLVED |
| RTCSP-1726 | Settings for STUN/TURN servers are not saved correctly in the UCServer administration if user name and password are entered instead of a shared secret. | >= 7.0.0 | RESOLVED (7.1.7) |
| RTCSP-1759 | In certain TS/RDS-SRV/swap workstation scenarios, the camera reports "busy" within the A/V Wizard in ProCall client. | >= 7.0.0 | UNSOLVED * |
| PAIM-1845 | Chatting is not possible (chat window remains empty). Error message in UC server "EDatabaseConnection::GetEvents;Field 'ReplyToSeqID' not found". | >= 7.0.0 | RESOLVED (7.1.2) |
| PROCALL-2027 | Using Microsoft Teams integration behind a web proxy | >= 7.3.5 | PENDING |
| CTIPBX-101 | Call forwarding cannot be set in ProCall Client (TAPI line via ECSTA for Avaya IP Office). | >=7.1.1 | RESOLVED (7.1.3) |
| RTCSP-1793 | There is no longer a warning during the UCServer update if real-time communication is taking place at the same time, which would otherwise be interrupted by the update. | >= 7.0.2 | RESOLVED (7.1.3) |
| RTCSP-1801 | If the PBX transmits SDP only in Session Progress (183) during an outgoing softphone call and not otherwise, the call is terminated after acceptance. | >= 7.0.0 | RESOLVED (7.1.3) |
| EG-186 | If the setup.exe file from the installation package is executed, then nothing is displayed on the start page. To work around this problem, please maximize the application window. A working version of the file can also be provided upon request. | >= 7.1.6 | RESOLVED (7.1.7) |
| PAIM-1789 PROCALL-593 | Google is canceling the Google Contacts API from [Externer Link: https://developers.google.com/contacts/v3/announcement] as of 19/1/2022. This means that ProCall Google integration will no longer be able to search for contacts. | ≥ 7.1 ≥ 8.0.1 | RESOLVED (8.5.0) |
| EG-277 PROCALL-1237 | Microsoft Active Directory Integration: User activation via AD SnapIn does not work. | ≥ 7.1.7 | SOLVED (7.3.3) |
| EG-315 | Call forwarding with your own additional line fails. | ≥ 7.2.1 | SOLVED (7.2.3) |
| PROCALL-1587 | "Open Federation" can no longer be activated via the UCServer administration. As a workaround, the activation can be done via a configuration file or the SIP proxy can be used. | ≥ 6.4.22 ≥ 7.3.3 | SOLVED (6.4.23) |
| PROCALL-1698 | Update service can no longer connect to server. See Update service can no longer connect to server for details. | ≥ 6.4.22 ≥ 7.3.4 | SOLVED (6.4.23) |
| PROCALL-1132 | When using Bluetooth connection with "PC audio devices", voice transmission does not work with iPhones in connection with Lenovo Bluetooth chipsets. | ≥ 7.2.1 | UNSOLVED |
| PROCALL-1939 | When using the Avaya facilities TSP, call forwarding can no longer be set via ProCall. | >= 7.4.0 | RESOLVED (7.4.1) |
| PROCALL-2364 | In the local WebService that is delivered with the UCServer installation, no intermediate certificates for TLS encryption can be inserted separately from the server certificate. This means that if an intermediate certificate is required, it must be included in the PFX file. Further external links with hints: 1), 2) | >= 7.5.0 | UNSOLVED |
| PROCALL-2125 | When using cross-device BusyOnBusy in ProCall and sharing your screen in the Teams client with Microsoft Teams presence integration active, BusyOnBusy will no longer work in ProCall. | ≥ 7.4.1 | SOLVED (7.5.2) |
PROCALL-5355 | Remote desktop mode for ProCall clients: if the user is also logged in to the UCServer via app, estos SIP GW signals "Busy Here" for incoming calls. Call acceptance not possible. | > = 8.4.2 | PENDING |
PROCALL-5847 | SIP line call forwarding is deleted after UCServer restart | ≥ 8.5.2 | SOLVED (8.5.3) |
*Since the problem cannot be solved in ProCall Enterprise but only in the infrastructure, it has been set to resolved.
ProCall for Windows
| Reference | Description | Affected versions | Status |
|---|---|---|---|
| RTCSP-1089 | Bluetooth connection for mobile phones does not work with Microsoft Windows 10 (from version 1903). | >=7.0.0 | RESOLVED (7.1.1) |
| PROCALL-768 | If Busy on Busy is set on the client for Windows, incoming calls are rejected during a screen share with Busy. | >= 7.0.0 | RESOLVED (7.5.3) |
| PAIM-1368 | On the Windows client, the call button should not work shortly after the end of the call to prevent accidental recalls. | >= 7.0.0 | RESOLVED (7.2.3) |
| PROCALL-650 | On the Windows client, the creation of a presence from private appointments does not work reliably via EWS (Exchange Web Services). | >= 7.0.0 | PENDING |
| PROCALL-764 | The order of the preview windows when sharing the screen (desktop sharing) does not correspond to the arrangement of the screens in Microsoft Windows. | >= 7.0.0 | UNSOLVED |
| PAIM-1728 | When ProCall is started, a dialog appears informing you that Microsoft Outlook should be defined as the default e-mail application. | >=7.0.0 | RESOLVED (7.0.0) * |
| PROCALL-651 | If a long note (several pages) is stored with a journal entry at the client for Windows and this note is to be printed, only the first page is printed and the remaining note is cut off. | >= 7.0.0 | POSTPONED |
PAIM-1311 | Occasionally reconnecting the Windows client to the UCServer after sleep mode fails. | ≥ 7.2.30 | PENDING |
| PAIM-1325 | Occasionally the reconnection of the client for Windows to the UCServer after hibernation fails. | ≥ 6.4.3 | NOT REPRODUCIBLE |
| PROCALL-642 | If a user is created in the file-based user administration on the ProCall client for Windows via the workplace setup, the samAccountName is used as the Users Principal Name. | ≥ 7.0.1 | PENDING |
| RTCSP-1443 | At the Windows Terminal Server (Remote Desktop Services) the call quality of the real-time communication of the client for Windows can be low under heavy load. | >= 7.0.0 | RESOLVED (7.0.3) * |
| RTCSP-1483 | If the connection between the Windows client and the UCServer is briefly interrupted, any real-time communication that is currently running is disconnected. | >= 7.0.0 | RESOLVED (7.0.2) |
| PAIM-1529 | In some cases, the telephony integration in Microsoft Outlook does not work. | >= 7.0.0 | RESOLVED (7.0.1) |
| RTCSP-1513 | With parallel softphone and TAPI calls, two independent call windows are displayed. | >= 7.0.0 | RESOLVED (7.1.0) |
| RTCSP-1577 | A screen share from the contact portal, multimedia business card, or LiveChat to the Windows client ends an ongoing video call. | >= 7.0.0 | RESOLVED (7.0.2) |
| EG-253 | With the Client for Windows SDD Replicator, the data source is not transferred. | >= 7.0.0 | POSTPONED |
PAIM-1653 | Group permissions are not considered. This means that calendar entries and lines are not displayed correctly. | >=7.0.0 | RESOLVED (7.0.2) |
| RTCSP-1654 | AV devices are not recognized correctly when starting the Windows client. | >=7.0.1 | RESOLVED (7.0.2) |
| PROCALL-777 | No playback devices with 4 channels are supported. | >= 7.0.0 | UNSOLVED |
| RTCSP-1656 | When ending an audio/video/softphone call, the Windows client may freeze. | >= 7.0.0 | RESOLVED (7.0.3) |
| RTCSP-1646 | The function "Always prepare call" is not possible for softphone calls. | >= 7.0.0 | RESOLVED (7.0.1) |
| PAIM-1718 | After a transfer after consultation, the forwarding contact is displayed as the caller. | >= 7.0.0 | RESOLVED (7.1.2) |
| RTCSP-1695 | Media port settings are reset after the server service restarts. | >= 7.0.0 | RESOLVED (7.0.1) |
| RTCSP-1694 | If a video call is not answered, the camera image is frozen afterward. | >= 7.0.0 | RESOLVED (7.0.1) |
| PAIM-583 | If a web proxy is used that is configured via Internet Explorer, there are scenarios in which e.g. call windows or chat windows of the Windows client "freeze" or appear with a long delay. | >= 7.0.0 | RESOLVED (7.0.1) |
| RTCSP-1649 | There are scenarios where there is a voice delay on outgoing softphone calls. | >= 7.0.0 | RESOLVED (7.1.2) |
| RTCSP-1706 | Push notifications for text chat do not work if the app is only logged in and the client is currently open. | >= 7.0.2 | RESOLVED (7.0.1) |
| PAIM-1776 | The Call Pickup function is offered if the user does not have permission to see the caller's phone number. | >= 7.0.0 | RESOLVED (7.0.1) |
| ECS-1706 | When using multi-terminal lines on the Mitel MiVoice MX-ONE, several call windows continue to appear. | >=6.0.0 (ECSTA) | RESOLVED (6.0.2 (ECSTA)) |
| PROCALL-799 | If the data source "ProCall user" is deactivated on the Windows client for the search on call, then it is still used for incoming softphone calls. | >= 7.0.0 | CANNOT BE RESOLVED |
| RTCSP-1888 | Procall Enterprise client crash in JabraNativeHid.dll. New Jabra SDK in ProCall Enterprise Client needs to be implemented. | >= 7.0.0 | RESOLVED (7.3.0) |
PROCALL-1376 | Missing support for Plenom Busylight Alpha Model 2/Busylight Omega Model 2 | >= 7.0.0 | RESOLVED (7.3.3) |
PROCALL-3852 | Request screen sharing: "Allow control" button is missing in certain constellations | >= 8.0.0 | RESOLVED (8.2.3.8093) |
PROCALL-3512 | Irregular behavior during cross-device Busy on Busy in the ProCall client related to Teams integration. | >= 8.0.0 | OPEN |
PROCALL-4259 | ChatApp: Chat cannot be detached | >= 8.2.3 | RESOLVED (8.3.0) |
PROCALL-4826 | The notes in journal entries cannot be edited/saved. | > = 8.3.4 | RESOLVED (8.3.5).X |
| PROCALL-5354 | End device via TAPI on the UCServer: when you pick up the receiver or dial a number on the end device, your own number is displayed in the call window as the call partner. | = 8.4.2.8888 | RESOLVED (8.3.5).X |
PROCALL-5355 | Remote desktop mode for Procall clients: if the user is also logged in to the UCServer via app, estos SIP GW signals "Busy here" for incoming calls. Answering calls is not possible. | > = 8.4.0 | OPEN |
| PROCALL-5330 | Function "Forward note as e-mail": Subject "IDS_FUNCT_FN_CALL_ABSENCE" | > = 8.4.2 | OPEN |
| PROCALL-5405 | With TAPI connection, the CalledID is no longer written to the "MSN" journal column | > = 8.4.28888 | OPEN |
| PROCALL-5787 | Procall Client for Windows in VPN-less mode does not return any results from the MetaDirectory | > = 8.4.28888 | RESOLVED (8.4.28888) |
| PROCALL-5932 | Remote Desktop Client ends the outgoing call after 8-13 sec if "Accept screen sharing prompt" is disabled for the user | > = 8.4 | RESOLVED (8.6.0) |
PROCALL-1144 | Microphone/speaker test via Audio Wizard sets the microphone level to 100% | > = 7.3.1 | OPEN |
*As the problem cannot be solved in ProCall Enterprise but only in the infrastructure, it has been set to resolved
ProCall for iOS
| Reference | Description | Affected versions | Status |
|---|---|---|---|
| PROCALL-1796 | iOS: If a PBX does not support "Forward", the function is still offered in the mobile apps in the softphone call window. | >= 7.0.0 | UNSOLVED |
| PREMPAIM-59 | Administrative favorites/monitor content and buttons are not displayed in the iOS app. | >= 7.0.0 | RESOLVED (7.1.50) |
| PREMPAIM-43 | Icons for the journal will be replaced in the iOS app. | >= 7.0.0 | RESOLVED (7.1.03) |
| PREMPAIM-33 | In the iOS app, some symbols are difficult to read in dark mode: | >= 7.0.0 | RESOLVED (7.0.10) |
| PROCALL-1062 | Push notifications are still deleted in iOS when they are read on another client. | >= 7.0.0 | RESOLVED (7.1.03) |
| RTCSP-1465 | The iOS app does not stop ringing when an incoming call is very quickly canceled or quickly answered on another device. In this state, the call can first be muted using the on/off switch on the mobile phone and then rejected when pressed twice. | >= 7.0.0 | RESOLVED (7.1.03) |
| PREMPAIM-39 | Presence profiles that include call forwarding occasionally cause crashes. | >= 7.0.0 | RESOLVED (7.0.10) |
| PROCALL-974 | In the iOS app, it is not possible to control Bluetooth headsets during outgoing calls. | >= 7.0.0 | RESOLVED (8.2.10) |
| RTCSP-1543 | In the iOS app, the speaker icon (speakerphone mode) has no function during video chat. | >= 7.0.0 | RESOLVED (7.1.31) |
| RTCSP-1664 | There are scenarios where no ringback sound is played when dialing out from iOS Mobile App. | >= 7.0.0 | RESOLVED (7.0.10) |
| RTCSP-1676 | Sometimes there are multiple push notifications of missed calls. | >= 7.0.0 | RESOLVED (7.1.1) |
RTCSP-1658 PREMPAIM-358 | The iOS app does not stop ringing sporadically even though the call was answered on another device. In this state, the call can first be muted using the on/off switch on the mobile phone and then rejected when pressed twice. | >= 7.1.10 | RESOLVED (7.2) |
PROCALL-971 | If a second SIM card (as an eSIM) is used for mobile data, there are scenarios in which the connection to the UCServer is constantly interrupted, and therefore smooth working with the app is not possible. | >= 7.0.0 | RESOLVED (8.3.2) |
| RTCSP-1106 | A softphone call via the iOS call list or contacts is not possible. Only the ProCall iOS app is opened. | >= 7.0.0 | RESOLVED (7.1.31) |
| PREMPAIM-214 | Group chats are sometimes listed multiple times in the chat view. | >= 7.0.0 | RESOLVED (7.1.21) |
| PROCALL-844 | The presence of a contact is not shown if the contact is not saved in Favorites. | >= 7.0.0 | POSTPONED |
| PROCALL-863 | Consultation and toggling are not supported. | >= 7.0.0 | UNSOLVED |
| PREMPAIM-442 | There are scenarios in which the journal in the iOS app is not updated without a relog from the user. | >= 7.1.10 | RESOLVED (7.2.2.4740) |
| PREMPAIM-714 | App usage is not possible after a password change. | >= 7.2.11 | RESOLVED (7.2.20) |
| PROCALL-1155 | iOS app crashes when clicking on "Calls | 7.3.20 | RESOLVED (7.3.21)) |
ProCall for Android
| Reference | Description | Affected versions | Status |
|---|---|---|---|
| PROCALL-1321 | Android: If a PBX does not support "Forwarding", the function is still offered in the mobile apps in the softphone call window. | >= 7.0.0 | RESOLVED (7.4.0) |
| RTCSP-1488 | If the camera is changed on a Samsung Galaxy S10 during a video chat, the smartphone reboots. | >= 7.0.0 | RESOLVED (7.3.10) |
| PROCALL-1033 | Poor call quality, echo, the other party is too quiet on Android devices. | >= 7.0.0 | RESOLVED (7.3.20) |
| PREMPAIM-42 | Icons for the journal will be replaced in the Android app. | >= 7.0.0 | RESOLVED (7.1.04) |
| RTCSP-1565 | There will be only one Android app for ProCall 6 and 7. | >= 7.0.0 | RESOLVED (7.0.0) |
| PREMPAIM-2 | In the Android app, administrative favorites/monitor content and buttons are not displayed. | >= 7.0.0 | RESOLVED (7.0.10) |
| RTCSP-1609 | If a video chat between 2 Android apps is accepted as an audio chat, there are scenarios where a video image is also transmitted. | >= 7.0.0 | RESOLVED (7.0.20) |
| RTCSP-1645 | Forwarding in the call state is not executed correctly and leads to a new call to the intended party. | >= 7.0.0 | RESOLVED (7.1.04) |
| RTCSP-1700 | In Android 11 the ProCall app may have problems with the microphone authorization. | >= 7.0.0 | RESOLVED (7.1.00) |
| RTCSP-1705 | If the phone has been locked for a long time (doze mode), video calls will be delayed and will not stop ringing. | >= 7.0.0 | RESOLVED (7.1.70) |
| PROCALL-844 | The presence of a contact is not shown if the contact is not saved in Favorites. | >= 7.0.0 | POSTPONED |
| PROCALL-848 | Consultation and toggling are not supported. | >= 7.0.0 | UNSOLVED |
| PREMPAIM-357 | In contacts from MetaDirectory and smartphone, phone numbers are not displayed and cannot be dialed. | >= 7.0.0 | RESOLVED (7.1.30) |
| PREMPAIM-483 | Android app in the background: It is not possible to answer the call or it takes a very long time to connect. | >= 7.0.0 | RESOLVED (7.0.20) |
| PROCALL-5369 | Android app continues to ring after call has been accepted on another device (e.g. Procall Client for Windows). | > = 2024.04.25 | UNSOLVED |
Please note our information on the use of "External links".