Cameron_TechPath

Hi @Support Any more clues? The Customer is adamant that it only occurs when two users try to answer the same call at the same time.

Hi @Support The issue only occurs when answering a call and never making a call. We've tried multiple users on the same device and the issue continues. We have also tried the same user on different machines across multiple locations in the country - Same outcome.

G'day, We've recently deployed a 120 seat customer who's using a mix of Soft Phones (100) and Desk Phones (20). We chose to use the the In-Bult Vodia Phone and Client interface as a crucial requirement was for the staff to see the ACD statuses and other staff status. Since day one a mix of users have been getting an error in either the Desktop App or Web App - The customer is certain it is when multiple Agents try answer the same call at the same time, We have tested this theory and been unable to replicate across 200 test calls (Yes it was painful) We thought it may be browser related so tested with Internet Explorer, Edge and Firefox yet the error was still shown. After speaking with Vodia Support they believed the error had to do with the headset becoming disconnected and reconnecting while the call answer action is being performed. The customer is using brand new Jabra Evolve & Engage 65's which are Bluetooth or USB/DECT base stations. We tested a hard wired headset with the same outcome. By posting here I hoped others had seen the error message before and had a resloution?

Hi @Support We're looking for the same thing - We want the ActionURL to be triggered as soon as a caller hits the IVR and then hangup after the message is played. The purpose is to allow users to break out of a Agent Group and then land on a IVR Node to trigger a call back event via an ActionURL to an external CRM system. At the moment we can only get the ActionURL to trigger once the message finishes and does not account for the user hanging up mid way through the message and the ActionURL isn't triggered.

Hi @Vodia PBX Unfortunately the suggestion only effects new calls and not calls already queued. Is there a way to apply this for calls already in the queue and waiting?

Hi, We're wanting exactly this. We're using version 63.0.0 and still not working. Any way to get this function working? First call allows for an ext outside the group to pickup the call however if there is an active call in the agent group talking to an agent the subsequent calls do not flash on the external ext and if the button is pressed they become part of the queue listening to the hold music.

I have updated the ticket I already had where they said post on the forum... Ticket# 484930

@support No - We checked the TAPI via Debug and nothing showed up. I was hoping to get a log from the PBX to see what it does when a call is made from the handset and the pbx is rejecting the calls as "Busy" I made a video of it to demo the issue if I could send it somewhere for review? Is there a log of just the TAPI/TSP? Software-Version: 63.0 (CentOS64) Build Date: Apr 18 2019 16:50:33

@support Any comment on this?

Hi, We recently activated the TAPI integration with ConnectWise Manage for our support desk however we quickly found an issue that led us to having to disable it straight away, ISSUE: With TAPI enabled and ConnectWise open we can make calls from the desk phones however afterwe trigger a call from ConnectWise and then try make a call from the desk phone all iInbound and Outbound calls to/from that extension show Busy as soon as the call starts to ring. If we then try to trigger a call from ConnectWise the call works fine. If we close ConnectWise then the desk phone works straight away no issues. If we open ConnectWise again it remains working until we trigger a call from ConnectWise. I've mentioned ConnectWise alot however we are also talking to them to see if there are any issues they could assist with at the same time.

Ticket #5074 is now open.

Od because it installed just fine.. We will open a ticket now and provide reference to this topic.

Hi, We have updated to 63.0.4 and this still has not fixed the issue. Snom D735: PBX Version: PBX Extension: Phone Screen: We would like to work with a developer to test this in a real environment rather than following the bouncing balls for months. Because we also noticed other things are now broken like the Screen transparency which was fixed in the last version and the User Portal has switched back to the old version...

Good Morning, We will test 63.0.4 tomorrow and report back. In regards to the certificate we do use "ACME" across all our PBX however this certificate error only appears when we populate the extensions photo. If we remove the photo or try an extension without an existing photo the phone does not get this error.

Hi, We have upgraded to 63.0.3 on our development pbx and this is still faulty. The phone is provided with an certificate error: