Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

408 profile views

A_nd_y's Achievements


Rookie (2/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. I have done everything described in the instructions but unfortunately it just does not work properly. The link with Zoho is done, theuser auth code is generated, the user credentials for Zoho are also correct. But it just does not work properly. Apparently something is not right on the pbx side. I don't see any log output which has to do with the CRM integration. Unfortunately I can't post any more screenshots here to prove the points -> Attachment Quota limit
  2. OK, now the check mark and dom_crm.htm is always set. But unfortunately Zoho integration still does not work. The "CRM related events" are still not visible in the log settings. With these log settings I don't see any output related to Zoho:
  3. I think we are approaching the problem: When I enable Zoho support on the /dom_crm.htm page, the red x turns into a green check mark. When I reload the page, there is a red x again. Also, I can't find the "CRM related events" in the log settings:
  4. Thanks for the answer! With these instructions I have set up the interface. But unfortunately I do not really get on with this. There are currently no IP restrictions set up in the firewall. For testing purposes any IP is allowed to access the system. Unfortunately, the instructions do not mention how the interface works, what ports and protocols are used. This makes it very difficult for me to debug the behavior. Are port forwardings simply missing here in the firewall?
  5. Hello, we are trying to get the Zoho integration to work with our PBX installation. Unfortunately the integration is only half working. But first, some info about the setup: We are using PBX version 67.0.5 on premise. The system is running with a static public IP and has the following firewall rules for incoming connections: 5060 TCP 5060 UDP 5061 TCP 15000-30000 UDP 443 TCP Outgoing connections are not restricted. The Auth Token has been set up in Zoho and it is also possible to start a call from within Zoho. But Zoho gets stuck in the connecting state: However, the telephony connection is established. Incoming connections are not displayed in Zoho at all. What is going wrong here? Is there a firewall configuration missing? Where can I find helpful information (Logfiles etc.)? For help I would be really grateful Best regards A_nd_y
  6. 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.)
  7. 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.
  8. Thank you! We will test it. Is there a timeline yet for when a maintenance release of the app will be released?
  9. 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", "The app wants my login data every time I start it". This is crap when basic functions of the app suddenly stop working. But the browser interface works as normal. Thanks a lot for your help
  10. 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.
  11. 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.
  12. 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?
  13. 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 Incoming call from 0xxxxxxxxxxx [0:01:38:703]:7 Notify new call to TAPI [0:01:38:703]:5 TSPI_lineCloseCall [0:01:38:719]:5 CSTA Tx: <?xml version="1.0" encoding="UTF-8"?> <ClearConnection xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed6"> <connectionToBeCleared> <callID>05af1c4a@pbx</callID> <deviceID>17@************.com</deviceID> </connectionToBeCleared> </ClearConnection> [0:01:38:719]:7 Clear connection with 0xxxxxxxxxxx [0:01:38:719]:4 Call was not accepted by TAPI [0:01:38:719]:5 CSTA Rx: <?xml version="1.0" encoding="UTF-8"?> <ClearConnectionResponse xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed4"/> [0:01:38:766]:5 CSTA Rx: <?xml version="1.0" encoding="UTF-8"?> <ConnectionClearedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed4"> <monitorCrossRefID>39</monitorCrossRefID> <droppedConnection><callID>05af1c4a@pbx</callID><deviceID>17</deviceID></droppedConnection> <releasingDevice><deviceIdentifier>17</deviceIdentifier></releasingDevice> <localConnectionInfo>null</localConnectionInfo> <cause>normalClearing</cause> </ConnectionClearedEvent>
  14. 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
  • Create New...