[Vtigercrm-developers] Asterisk Connector & Asterisk 11

[vtiger at camden.net]

we got this working under rev 14179, not 14176 as you suggested, but its 
buggy
everything works fine until you run a "core restart gracefully" or "core 
restart now" on asterisk CLI

then we get 100% CPU for 10 minutes thenFatal error: Maximum execution time 
of 600 seconds exceeded in /var/www/html/admin/libraries/php-asmanager.php 
on line 276
 then CPU usage jumps around 
 we have tracked CPU usage to AGI.sh 
 vtiger also gets stuck in a endless loop poping up the last incomming call 
every 3-5 seconds after the CLI restart and click to call pops up with 
"call failed" 
 a soft restart of the server does not fix 
 full power down fixes, until the next time you restart asterisk  

 we are going though logs to see if it possible anything on our setup 

 to go from 14176 to 14179 and get PBX manager to work, we had to delete 
the vtiger directory, delete vtiger database, svn new copy, is there a 
command we can run to get vtiger to correctly update everything after each 
svn?? 

 there still is not settings under "my preferences" to disable inbound 
notification as suggested 

 forcing all calls to record, is probably a better sounding idea then it is 
in practice, there are many places this is not legal to do with out consent 
from all parties on call, also you can not expect for all calls to go 
though vtiger.... it may be better to query the Asterisk CDR database for 
call records to tie to vtiger and if recording happens to be turned on link 
to the file audio file asterisk makes, in other words let the asterisk 
administrators and PBX owners decide when and what calls are going to be 
recorded via Asterisk, then you should have check box in PBX Manager if 
they want vtiger users to even have access to the recordings, I dont think 
many companies are going to want regular employees having access to 
recordings, its a very large liability 

   

    

----------------------------------------
From: "Rishab K" <rishab.k at vtiger.com>
Sent: Monday, August 11, 2014 12:13 PM
To: vtiger at camden.net
Subject: Re: [Vtigercrm-developers] Asterisk Connector & Asterisk 11 

Hi, 

 Please provide us temporary access to your Asterisk server where Vtiger 
connector is installed so that we can verify from our end. Along with this 
share the credentials of the user where the Vtiger 6.1 is installed so that 
debugging the issue will be easier. 

 AGI vs AMI: 
Based on the suggestions from the previous I want to clarify few points 
that Why AGI and AMI? Why can't we use AMI alone? 

 I agree with the scenario that you related with webform where in you want 
to update the personal information of the customer through webform. Same 
you can relate to PBXManger, using AGI we can update the call the records 
everytime when asterisk trigers a new event. Suppose for an inbound call, 
if second leg is answered then asterisk would trigger "Bridge Event" 
specifing who is the source and target and other info. So until the call 
gets terminated asterisk be trigerring new events by updating few 
parameters. 

 In this case based on the events generated, Vtiger connector would parse 
the events and notify Vtiger regarding type of event and Vtiger will decide 
what needs to be done like to create new record or update the existing 
record.  

 		Asterisk <-> Vtiger Connector (AGI request) <-> Vtiger (Http request)  

 Why AGI? Why not AMI alone? 
Earlier version of PBXManager had a client file which used to connect to 
Asterisk server and wait for the events that are triggered by asterisk, 
parse and update in Vtiger. This was completely based on AMI alone where in 
Vtiger had to request Asterisk and check if there are any new events every 
seconds which is not proper or effient way as it would affect the 
performance of the product and some times overload server also.  

 Hence Vtiger Connector was written so the we can eleminate the need of 
polling or requesting asterisk every second. Based on the AGI URL 
sepecified in asterisk, asterisk knows where the connector is and will 
forward the event to connector. Connector has the information about Vtiger, 
it parses the event and sends HTTP request to connector and viceversa.  

 We may achieve complete process using AMI alone but it has so many 
disadvantages which are overcomed using AGI. 



 Incoming Call Popup: 
These are action mappings that are added in profiles. So each profile under 
PBXManager, there will be two check boxes with these action names. 

 Currently we have provided an option where in you can restrict the calls 
to particular profile so that all the users who belong to that profile will 
not receive calls. But if you want to restrict few users from one profile 
then currently there is no option(except removing extension from "CRM Phone 
Extension"). May be as suggested we need to add "checkbox" in MyPreference 
so that user can restrict incoming calls.  

 Closing Incoming Call Popup: 
Currently if the popup is closed, it will be closed permanently. But as you 
suggested it would be great if we can allow users to set the time in 
MyPreferences so that popup will reappear based on the value they configure 
here(similar to default event duration). 


Regards, Rishab 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20140812/7d003846/attachment.html>