[Vtigercrm-developers] Asterisk Good News

[vtiger at camden.net]

In FreePBX
Connectivity --> Trunks  (select your trunk you want to use for vtiger outbound calling, you might only have 1 trunk to use, you might a few to pick from, dont matter if its SIP, DAHDi, IAX or what ever, if you have more than 1 trunk you need to pick one)
General Settings and Outgoing Settings Sections will both have "Trunk Name"
In Vtiger 
Settings --> CRM Settings -- > Integration --> PBXManager 
"Outbound Trunk"
all 3 must match

*************************************************************************************************************************
In Vtiger 
Settings --> CRM Settings -- > Integration --> PBXManager 
"Outbound Context" must match a context in extensions.conf in that context you must have exten => _X.,1,agi(agi://0.0.0.0/incoming.agi)
i used "vtiger_outbound" so I have "vtiger_outbound" in the "Outbound Context" field in PBX Manager and
[vtiger_outbound]exten => _X.,1,agi(agi://0.0.0.0/incoming.agi)
in extensions.conf

you still need all the other setting that have been posted before
check all the settings in VtigerAsteriskConnector.properties
ServerIP = 127.0.0.1serverport = {pick a unused port}
make sure in the PBX Manager "vtiger Asterisk App URL matches, should be 
http://127.0.0.1:{the port you picked}

AsteriskServerIP = 127.0.0.1AsteriskServerPort = {your AMI or Proxy Port}AsteriskUserName = {your AMI or Proxy User Name}AsteriskPassword = {your secret to the above user}

make sure your AMI user (in manger.conf or refer to your proxy documentation) for above with

read = all,system,call,log,verbose,command,agent,user,config, originatewrite = all,system,call,log,verbose,command,agent,user,config, originate
*** proxy should be used for large deployments, astmanproxy works well

make sure webapp.sh and agi.sh are actually running on your server and set to start on boot

the above will get click to call to work and your 99% setup for inbound

for inbound notification you need to put exten => _X.,1,agi(agi://0.0.0.0/incoming.agi) in a existing context in extensions.conf that will fire on inbound, this may not be same for everyone
we used [from-internal] which will make vtiger agi fire for any call goign though PBX on our system from outside or inside to inside
we could have used [from-trunk] that would make vtiger agi fire only on outside calls coming from the trunk
yours may be different, this would be more of question for your asterisk admin then vtiger as to how you should do this

 

----------------------------------------
From: "Zebra Hosting" <support at zebrahosting.eu>
Sent: Wednesday, August 20, 2014 10:49 AM
To: "vtigercrm-developers at lists.vtigercrm.com" <vtigercrm-developers at lists.vtigercrm.com>
Subject: Re: [Vtigercrm-developers] Asterisk Good News 


Thanks for sharing the good news!





Unfortunately I can't get it to work. Guess a few more steps needed in your descriptions :-)





This part:

keep in mind Asterisk has a general settings and a outbound settings for each trunk both have trunk name and they must match

Left me puzzled.. 


 
The outbound trunk you mention, is a SIP trunk or something you setup for vTiger only? (I am on FreePBX so things might be a little different. 


 
Thanks, 


 
Bastiaan Houtkooper 
Zebra Hosting 






From: "vtiger at camden.net" <vtiger at camden.net>

Reply-To: <vtiger at camden.net>, <vtigercrm-developers at lists.vtigercrm.com>

Date: Tue, 19 Aug 2014 21:36:16 -0400

To: Rishab K <rishab.k at vtiger.com>, <vtigercrm-developers at lists.vtigercrm.com>

Subject: [Vtigercrm-developers] Asterisk Good News


after starting from scratch the Asterisk Connector and PBX Manager are working consistently with one minor issue



click to call:



when you call out the person you call sees caller ID as them self



IE:



I click my cell phone number, my extension rings, I answer my extension and Asterisk calls my cell



my cell phone rings, but the callerID on my cell is saying I am getting a incoming call from my cell, when it should be the default outbound CID of my extension



the call does connect, just has the wrong callerID



on phones that support both Cname and CiD, the CID still comes up as the person you are calling see the CID as them selfs but



the Cname is set to the Display Name of the Extension which is technically correct but the whole callerID string should be set to the Outbound CID string of the extensions settings



most companies will have the display name as the person real name or just the extensions number where outbound CID will be "NAME"<NUMBER> of how the company wants outside callers to see the callerID info 




for those that are going to ask how we got it to work



you must be on rev 14179 or higher, you must also update PBX Manager



you need to have



[vtiger_outbound]
exten => _X.,1,Agi(agi://0.0.0.0/incoming.agi)



in extensions.conf and outbound context in PBX Manager also set to "vtiger_outbound"
actually as long as both match it will work



the outbound trunk is the name of your trunk in Asterisk to use for outbound calling, keep in mind Asterisk has a general settings and a outbound settings for each trunk both have trunk name and
 they must match



for inbound even though we tried to set default context to "vtiger_inbound" in asterisk we never got the AGI to fire from there and for us it broke other stuff, we put "exten
 => _X.,1,Agi(agi://0.0.0.0/incoming.agi)"
 into the from-internal context in extensions.conf as that is our default context and it works just fine



yes that is correct you will have 2 contexts in extensions.conf both with "exten
 => _X.,1,Agi(agi://0.0.0.0/incoming.agi)"



 _______________________________________________ 
http://www.vtiger.com/
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20140820/8112f8a0/attachment-0001.html>