Support A2Billing :

provided by Star2Billing S.L.

Support A2Billing :
It is currently Sat Apr 27, 2024 9:47 pm
Predictive Dialer


All times are UTC




Post new topic Reply to topic  [ 12 posts ] 
Author Message
 Post subject: a2billing HangUP/doesn't answer
PostPosted: Fri Nov 27, 2009 11:51 am 
Offline

Joined: Wed Nov 25, 2009 12:01 pm
Posts: 90
hi..i am having problem with receiving call from outside to my a2billing..when i call the system hang up or get message say " service can not e connected".

but i can receive call to my extension phone.. i have set up the a2illing with trunk exactly as in pbx trunk and the call card, rate, customer,,etc.

i am running trixox 2.8 with a2biling 1.4

i've created inbound route in pbx with custom Destination with: a2billing,${X},1
i've added the script to extensions_a2billing.conf.
1) do i have to delete the rest script or add the script with the rest?
2) do i have to add this script to extensions_custom.conf as well?

[custom-a2billing]
exten => _X.,1,Answer
exten => _X.,n,Wait(1)
exten => _X.,n,DeadAGI(a2billing.php|1)
exten => _X.,n,Hangup

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

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

[a2billing-cid-callback]
exten => _X.,1,DeadAGI(a2billing.php|2|cid-callback|1
exten => _X.,n,Hangup

[custom-a2billing-allcallback]

[custom-a2billing-did]
exten => _X.,1,deadAGI(a2billing.php|1|did)
exten => _X.,2,Hangup

i've would really appreciate your help.

thank you.


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Fri Nov 27, 2009 3:11 pm 
Offline

Joined: Fri Jun 23, 2006 3:56 pm
Posts: 4065
Quote:
i've created inbound route in pbx with custom Destination with: a2billing,${X},1


I don't see your A2Billing context listed?

Joe


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Sat Nov 28, 2009 2:40 pm 
Offline

Joined: Wed Nov 25, 2009 12:01 pm
Posts: 90
hi..Joe thanks for the quick replay..i am a newbe so please be patience..

i got the following in the a2illing config..


A2Billing config file


; Global Database Setup - select the database type and authentication as required.

[database]
hostname = localhost
; port for postgres is 5432 by default
port =
user = a2billinguser
password = a2billing
dbname = mya2billing
; dbtype setting can either be mysql or postgres
dbtype = mysql


; config for the daemon process
[daemon-info]
uid =
gid =
pidfile = /var/run/a2billing/a2b-callback-daemon.pid
;pidfile = ./a2b-callback-daemon.pid


; config for the logger
; article on http://www.red-dove.com/python_logging.html
[loggers]
keys=root,callbackLogger


[handlers]
keys=consoleHandler,FileHandler,RotatingFileHandler


[formatters]
keys=callbackFormatter


[logger_root]
;level=DEBUG
level=INFO
handlers=consoleHandler,RotatingFileHandler


[logger_callbackLogger]
;level=DEBUG
level=INFO
handlers=consoleHandler,RotatingFileHandler
qualname=callbackLogger
propagate=0


[handler_consoleHandler]
class=StreamHandler
;level=DEBUG
level=INFO
formatter=callbackFormatter
args=(sys.stdout,)


[handler_FileHandler]
class=FileHandler
level=DEBUG
formatter=callbackFormatter
args=('/var/log/a2billing/a2b-callback-daemon.log', 'a')
filename=/var/log/a2billing/a2b-callback-daemon.log
mode=a


[handler_RotatingFileHandler]
;class=handlers.RotatingFileHandler
class=handlers.TimedRotatingFileHandler
level=DEBUG
formatter=callbackFormatter
; TimedRotatingFileHandler
args=('/var/log/a2billing/a2b-callback-daemon.log', 'midnight', 1)


[formatter_callbackFormatter]
format="%(asctime)s - %(name)s - %(threadName)-10s - %(levelname)s - %(message)s"
datefmt=


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Sat Nov 28, 2009 3:31 pm 
Offline

Joined: Fri Jun 23, 2006 3:56 pm
Posts: 4065
Hi

a2billing.conf is not relevant here.

you need an A2Biling context, such as:-

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

or you need to change your custom destination to point to a context that exists.

Joe


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Sat Nov 28, 2009 4:36 pm 
Offline

Joined: Wed Nov 25, 2009 12:01 pm
Posts: 90
hi..thank you so much for your help..

i put my extensions_a2billing.conf to default..now i have the following

[a2billing]
exten => s,1,Answer
exten => s,n,Wait(1)
exten => s,n,deadAGI(a2billing.php,1)
exten => s,n,Hangup

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

From a2billing

[a2billing-cid-callback]
exten => s,1,deadAGI(a2billing.php|1|cid-callback|34) ;last parameter is the callback area code
exten => s,n,Hangup

[a2billing-all-callback]
exten => s,1,deadAGI(a2billing.php|1|all-callback|34) ;last parameter is the callback area code
exten => s,n,Hangup

[a2billing-did]
exten => s,1,deadAGI(a2billing.php|1|did)
exten => s,2,Hangup

[a2billing-voucher]
exten => s,1,deadAGI(a2billing.php|1|voucher)
exten => s,n,Hangup


point the custom destination context in PBX to

a2billing,s,1


when i try to call in, I get message "the service can not be connected"

According to the asterisk log:

[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [4119417@ext-did:1] Set("SIP/4119417-099890b0", "__FROM_DID=4119417") in new stack
[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [4119417@ext-did:2] Gosub("SIP/4119417-099890b0", "app-blacklist-check,s,1") in new stack
[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [s@app-blacklist-check:1] GotoIf("SIP/4119417-099890b0", "0?blacklisted") in new stack
[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [s@app-blacklist-check:2] Return("SIP/4119417-099890b0", "") in new stack
[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [4119417@ext-did:3] ExecIf("SIP/4119417-099890b0", "0 ?Set(CALLERID(name)=02084712971)") in new stack
[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [4119417@ext-did:4] Set("SIP/4119417-099890b0", "__CALLINGPRES_SV=allowed_not_screened") in new stack
[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [4119417@ext-did:5] Set("SIP/4119417-099890b0", "CALLERPRES()=allowed_not_screened") in new stack
[Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Executing [4119417@ext-did:6] Goto("SIP/4119417-099890b0", "a2billing,s,1") in new stack
[color=#FF0040][Nov 28 16:27:29] VERBOSE[2891] logger.c: -- Goto (a2billing,s,1)
[Nov 28 16:27:29] WARNING[2891] pbx.c: Channel 'SIP/4119417-099890b0' sent into invalid extension 's' in context 'a2billing', but no invalid handler


invalid extension 's' in context 'a2billing?

i'm well confused.....


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Sun Nov 29, 2009 1:02 am 
Offline

Joined: Wed Feb 13, 2008 11:11 am
Posts: 224
rboy,
confused.com
Read what Joe Says.
Code:
Hi
a2billing.conf is not relevant here.
you need an A2Biling context, such as:-
[a2billing]
exten => _X.,1,DeadAGI(a2billing.php|1)
exten => _X.,n,Hangup
or you need to change your custom destination to point to a context that exists.

Joe

You say
Code:
i've created inbound route in pbx with custom Destination with: a2billing,${X},1

custom-a2billing,${EXTEN},1

or simply register incoming DID directly to custom-a2billing
context=custom-a2billing

Rgds
Eamonn


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Tue Dec 01, 2009 4:36 pm 
Offline

Joined: Wed Nov 25, 2009 12:01 pm
Posts: 90
Thank you guys for your help...i manged to get it working...

much appreciated.

:D


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Tue Dec 08, 2009 4:26 am 
Offline

Joined: Mon Nov 23, 2009 6:14 am
Posts: 36
HI,
is this the right syntax?

exten = xxxxxxxxxx,1,(a2billing_default,${EXTEN},1)

Regards,

Al


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Tue Dec 08, 2009 2:35 pm 
Offline

Joined: Wed Nov 25, 2009 12:01 pm
Posts: 90
Hi..


i got the following in my extension_custom

[a2billing]
exten => _X.,1,Answer
exten => _X.,n,Wait(1)
exten => _X.,n,DeadAGI(a2billing.php,1)
exten => _X.,n,Hangup

[custom-a2billing]
exten => _X.,1,Answer
exten => _X.,n,Wait(1)
exten => _X.,n,DeadAGI(a2billing.php,1)
exten => _X.,n,Hangup

and point the context in your custom destination in PBX:

custom-a2billing,${EXTEN},1

that should do it..


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Tue Dec 08, 2009 11:50 pm 
Offline

Joined: Mon Nov 23, 2009 6:14 am
Posts: 36
Hi,

Any other ideas.

I have this on my file

[DID_IP Communications_default]
;exten = XXXXXXXXXX,1,Set(TIMEOUT(absolute)=180) ;timeout is in seconds
;exten = XXXXXXXXXX,2,DISA(no-password|CallingRule_International)
exten = XXXXXXXXXX,1,(a2billing_default,${EXTEN},1)

The first two lines are dissable I am testing A2billing on a server opeational with those options.

Is this line right?

exten = XXXXXXXXXX,1,(a2billing_default,${EXTEN},1)


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Wed Dec 09, 2009 6:46 am 
Offline

Joined: Fri Jun 23, 2006 3:56 pm
Posts: 4065
Code:
exten = XXXXXXXXXX,1,(a2billing_default,${EXTEN},1)


The extension you have put in means that it will only be called is some one actually calls XXXXXXXXXX, and X is not a button normally found on a phone.

I think you may want to be pattern matching, so change it to _XXXXXXXXXX which will match any 10 digit number.

Joe


Top
 Profile  
 
 Post subject: Re: a2billing HangUP/doesn't answer
PostPosted: Wed Dec 09, 2009 6:51 am 
Offline

Joined: Mon Nov 23, 2009 6:14 am
Posts: 36
Hi,

Sorry but I replaced incoming number with Xs.

Regads,

Al


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 12 posts ] 
VoIP Billing solution


All times are UTC


Who is online

Users browsing this forum: No registered users and 33 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