- Joined
- Dec 17, 2018
- Messages
- 20
- Reaction score
- 3
Hi all
We have V16 latest alpha installed and running with the vTiger server integration configured. On incoming calls we can get contact/company information displayed in the web or app interfaces but whenever we try and allow auto-pop of the CRM record we receive the error "Illegal request" displayed within the browser window it is trying to pop the record to. Pressing F5 to refresh does not work and causes the same error BUT if you click in to the address field of the window and hit Go to load the page then (as long as we have previously logged in to the vTiger system in that browser session using a web authenticated vTiger user) then the record loads.
We have worked extensively with the vTiger developer supporting this customers CMR and they cannot see what the problem is. We believe it is something to do with the way the API integration is trying to pull the data as we think, although cannot be certain, it is related to how the API is passing the request from 3CX.
We have a deal potentially resting on this integration working as indicated in the documentation so would be very interested to hear of anyone else using this integration on V16 and if they have it working as documented?
J.
We have V16 latest alpha installed and running with the vTiger server integration configured. On incoming calls we can get contact/company information displayed in the web or app interfaces but whenever we try and allow auto-pop of the CRM record we receive the error "Illegal request" displayed within the browser window it is trying to pop the record to. Pressing F5 to refresh does not work and causes the same error BUT if you click in to the address field of the window and hit Go to load the page then (as long as we have previously logged in to the vTiger system in that browser session using a web authenticated vTiger user) then the record loads.
We have worked extensively with the vTiger developer supporting this customers CMR and they cannot see what the problem is. We believe it is something to do with the way the API integration is trying to pull the data as we think, although cannot be certain, it is related to how the API is passing the request from 3CX.
We have a deal potentially resting on this integration working as indicated in the documentation so would be very interested to hear of anyone else using this integration on V16 and if they have it working as documented?
J.