Elastix & Vtiger CRM Integration
Kindly I need to Integrate VtigerCRM with Elastix server, I have VtigerCRM webpage on windows server 2008r2 I use it by Xamp app "192.168.1.241" . and I have Elastix server 2.5 "192.168.1.209,
I downloaded VtigerAsteriskConnector on /VtigerAsteriskConnector
the Configuration :
- Copyright (C) www.vtiger.com. All rights reserved.
- @license Proprietary
// Location where the application server will be running.
ServerIP = 192.168.1.209
ServerPort = 8383
// Call Recordings storage path
StorageDir = /VtigerAsteriskConnector
// Enable(true) or Disable(false) call recordings
Recording = true
// Location where the applications database files will be stored.
AsteriskAppDBPath = /VtigerAsteriskConnector
// Asterisk Server Details
AsteriskServerPublicIP = 192.168.1.209
AsteriskServerIP = 192.168.1.209
AsteriskServerPort = 5038
AsteriskUsername = vtiger
AsteriskPassword = 11111111
// Vtiger CRM URL
VtigerURL = http://192.168.1.241:8888/
VtigerSecretKey = 20539342065c0ec973464d7
//Enable(true) or Disable(false) Asterisk Events and Database Logs in Connector
AsteriskLog = true
DatabaseLog = true
anyone can help me
Kindly I need to Integrate VtigerCRM with Elastix server...
That some people still run Elastix is pretty bad, but doing a NEW integration between it and vTiger? This seems crazy. You are aware that Elastix has been out of business for a few years (they were bought by 3CX and shut down) and had no products for years before that, right? They've had no production release for three years and that was only a patch to an already incredibly dated system.
Don't put a single moment into supporting Elastix. Get that replaced ASAP. Do your effort for integration on a current phone system. Doing this will only increase your technical debt and make it that much harder to fix the problem you are already having.
JaredBusch last edited by
I have VtigerCRM webpage on windows server 2008r2
You should fix this. This is horrible. vTiger is free and runs better on free Linux. Get Fedora, Ubuntu, CentOS, whatever. Get something current. Never use XAMP, it should not exist. Everything about this setup is bad, but can be fixed.
You have two major things to fix here, the web server and the phone system. Both are very high priorities and both can be fixed for free. You aren't trapped with either, so just fix these. Then worry about integration once you've resolved the critical issues.