Jump to content

A_nd_y

Members
  • Content Count

    13
  • Joined

  • Last visited

Everything posted by A_nd_y

  1. Next Bug: Every second or third call has only one-side audio. This is not the case for versions smaller than 3.5.5. (That's what the colleagues say.)
  2. Nope! The login problem is still there. The bug occurs after restarting the app. After a (session!?) timeout the login is possible again. Do you have a public bug tracker? I have discovered more bugs that I would like to report.
  3. Thank you! We will test it. Is there a timeline yet for when a maintenance release of the app will be released?
  4. Hello Vodia Team, can you provide a link to the app in a version < 3.5.3? The versions 3.5.3 and 3.5.4 are just not really usable for us. In the version 3.5.4 are now the following new bugs immediately noticed: * The user "null" is now always displayed in the upper right corner. * The login process hangs most of the time. Here you have to restart the Ap several times and/or delete the configuration. * The app window still shows version 3.5.3. I get emails here all the time with messages like: "Login doesn't work anymore", "My user is wrong", "I can't turn off DND", "T
  5. The app looks like an electron application to me. If so, it is a small thing to implement the missing features. It just needs to be done.
  6. Same here! And also for all other colleagues. We using an self hosted pbx version 66.0.6 and the app in version 3.5.3.
  7. I tested it again on two clean VM's (only Windows , the TAPI driver and EPhoneX64.exe). On the first VM with Windows 7 on the last patch level it works. On the second VM with Windows 10 1909 the call is rejected. But it is noticeable that under Windows 7 the trace log is written first after EPhone opens the TAPI session. Under Windows 10 the log is filled directly after the Windows logon. I need the TAPI connection for our CRM system and my colleagues wait for a solution. What can I do to get a working fix for the problem?
  8. Hi! I'm just trying to get the TAPI client up and running and I've encountered a strange problem: The driver is configured and outgoing calls can be started. However, all incoming calls for an extension are immediately rejected as soon as any TAPI client is registered for it. If I close the TAPI Client again, the phone rings again too. Does anyone have a tip for me what this could be? Some additional Infos: Software version 65.0.8 (Debian64) Build date May 30 2020 18:30:57 [0:01:38:703]:7 DeliveredEvent(0xxxxxxxxxxx, yyyyyy17, 05af1c4a@pbx) [0:01:38:703]:7
  9. Hello, there. Since a few days we have massive problems with our telephone server. The phones always get the answer 403 No mor licenses from the pbx. But no new extensions have been added to the system and the license info in the web interface also looks good. What goes wrong here? I would be grateful for quick help! Best regards Andy
  10. Thank you! With this file it works again
  11. Hi! In the meantime we have updated to 60.0.3. However, the delay is still present. And yes, we use Snom (870) phones. What else can we do to reduce the delay?
  12. Hello, everybody since the last update to version 60 we have a curious behaviour with our telephone system. The phones signal an incoming call immediately on the display but the ringing starts two to three seconds later. Where does this behaviour come from and how can I change this so that the devices ring again immediately? Best regards A_nd_y
  13. Hi at all, we have an old snom one (Version 4.5.0.1090) und want to upgrade it to to the current PBX V5 (56.0). I've exported the pbx.tar archive from the old system, but i don't find a import option on the webinterface of the new pbx. So my question is: How can i import my old configruation into the new system? best regards A_nd_y
×
×
  • Create New...