A_nd_y Posted July 21, 2020 Report Share Posted July 21, 2020 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> Quote Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.