Support A2Billing :

provided by Star2Billing S.L.

Support A2Billing :
It is currently Thu May 28, 2020 10:37 pm
Hosted Voice Broadcast


All times are UTC




Post new topic Reply to topic  [ 3 posts ] 
Author Message
 Post subject: Question about Web CallBack Configuration
PostPosted: Mon Feb 21, 2011 6:12 pm 
Offline

Joined: Wed May 26, 2010 5:39 pm
Posts: 30
Hi, I have A2Billing 1.8.5

I have the following in extensions_a2billing.conf

[a2billing-callback]
exten => _X.,1,DeadAgi(a2billing.php|1|callback)
exten => _X.,n,Hangup

Also in extensions_custom.conf

[custom-a2billing-callback]
exten => _X.,1,DeadAgi(a2billing.php|7|callback)
exten => _X.,n,Hangup

In a2Billing system settings/callback group, I have
context_callback=custom-a2billing-callback

If I understand right, for the A-Leg (Callback Leg) of the call, because I have context_callback=custom-a2billing-callback,
the callback deamon will use agi_conf7 instead of agi-conf1 as in the [a2billing-callback] context, hence [a2billing-callback] will not be used. On the other hand, the B-Leg of the call is just another voip call, and is being handled by [a2billing] in extensions_a2billing.conf.

Hence, to modify how Web Callback is done, I just need to modify agi_conf7 according to the setup described above.

Please confirm, anyone ....
Thanks.


Top
 Profile  
 
 Post subject: Re: Question about Web CallBack Configuration
PostPosted: Tue Feb 22, 2011 12:01 am 
Offline

Joined: Sun Mar 12, 2006 2:49 pm
Posts: 954
Location: Barcelona
In Web Callback, once a callback request is received, the daemon will outbound
the call to asterisk and redirect it on the context defined in the setting "context_callback"

So in your case it will use :
[custom-a2billing-callback]
exten => _X.,1,DeadAgi(a2billing.php|7|callback)
exten => _X.,n,Hangup

therefore, the agi-conf 7 will be used for the configuration...

Yours,
/Areski


Top
 Profile  
 
 Post subject: Re: Question about Web CallBack Configuration
PostPosted: Fri Feb 25, 2011 12:56 pm 
Offline

Joined: Wed May 26, 2010 5:39 pm
Posts: 30
Thanks Areski,

Works beautifully, including the CallerID's on the A-Leg (I use PD Caller ID for the callback leg, otherwise A-Number gets whatever the VOIP provider sends) and the B-Party gets the Caller's CallerID (I have auto_setcallerid=YES and cid_sanitize=CID).

Suggestion: Wouldn't it be more practical that the B-Party sees whatever the A-Number enters as CallerID? At least as an option in the conf file (jOption: Just use whatever the A-Number is for CallerID)

Example scenario:

The customer is in a place where he/she has access to a fixed phone that does not belong to her. She gives that number as A-Number, and enters the number to call to the B-Number.

The called party sees whatever the caller has in her CallerID/DID list (and actually randomly if he/she has more than one).

Called party cannot answer the phone, but tries to return the call (by calling the number on the CallerID received) and the A-Party is not there.

Keep up with the good work!

Burak


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 
Predictive Dialer


All times are UTC


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group