Support A2Billing :

provided by Star2Billing S.L.

Support A2Billing :
It is currently Wed Oct 17, 2018 11:26 am
Auto Dialer Software


All times are UTC




Post new topic Reply to topic  [ 24 posts ]  Go to page Previous  1, 2
Author Message
 Post subject:
PostPosted: Thu Apr 12, 2007 8:51 pm 
Offline

Joined: Fri Apr 28, 2006 5:11 am
Posts: 426
greekman wrote:
At least ugly solution....
normaly the code of A2B must be reviewed for compatibility on PHP5 I think.

I use A2B with PHP5 (Gentoo) and MySQL5 about one year with no problems. Many testing and productions machines from Pentium3 (~266MHz and up) to P4. No delays, all works very fast, same on all. Thanks to Areski.


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 13, 2007 12:06 pm 
Offline

Joined: Mon Apr 09, 2007 9:49 pm
Posts: 8
Location: France
I found the evil off all finaly !

There is unofficial repo for Opensuse 10.1 & 10.2 containing php 4.4.6 (backport) and php 5.2.1 (upgrade)

http://omar.owahab.com/Omar/node/28

Originaly Opensuse 10.1 comes with php 5.1.2

I tested both ,

php 5.2.1 --> var:deprecated are almost disapearing from logs (only 3 lines )

php 4.4.6 --> All is perfect.

PHP5 appears to be a bit faster then PHP4


Ehe-he...and PHP 6 is comming....


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 13, 2007 4:10 pm 
Offline

Joined: Sun Mar 12, 2006 2:49 pm
Posts: 954
Location: Barcelona
Great news !!!

8) 8) 8) 8) 8)


Top
 Profile  
 
 Post subject: I am still confuses
PostPosted: Sun Dec 02, 2007 6:57 pm 
Offline
User avatar

Joined: Sat Jun 02, 2007 5:59 am
Posts: 63
Location: Orlando, Fl
I really appreciate the attention given to this topic. I am however still confused as to what to do to solve this problem.

I am experiencing the same issue. AGI is being processed very slowly. I turned debug and verbosity off and the initial statement to enter pin arrives much more quickly. This however does not solve the real problem. What is causing this to happen.

I have run A2B on a laptop with 20GB HHD and .5GB of RAM and it ran like a champ. I am now running the system on a DUAL P3 blade server and evrything is screaming except for the AGI processing. Can anyone help?

Thanks in advance!

Seth


Top
 Profile  
 
 Post subject: VERY DESPERATE
PostPosted: Sun Sep 14, 2008 3:35 pm 
Offline

Joined: Sun Aug 17, 2008 1:52 pm
Posts: 93
I have exactly the same problem for two weeks now and I've been working on my Dell server (quad code dual cpu/ 4GB RAM 15k Rpm HDD).

but this problem is not there on my PC core 2 duo.

I tried php 5.2.6 and it did'nt solve .
I couldn't find php4 to install on my centos5.1 but is there any specific solution to this?

If I turn on logging it takes 5 second to load a2billing ivr and if I turn it off is less than one second.



Thanks


Top
 Profile  
 
 Post subject: Re: VERY DESPERATE
PostPosted: Sun Sep 14, 2008 8:47 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
hellbound wrote:
If I turn on logging it takes 5 second to load a2billing ivr and if I turn it off is less than one second.
And if you enable logging but kill your syslog daemon?
Did you try latencytop as I suggested in your own thread on this topic?


Top
 Profile  
 
 Post subject:
PostPosted: Sat Dec 20, 2008 11:14 am 
Offline

Joined: Thu Oct 04, 2007 10:04 am
Posts: 20
Hi,

Did somebody found a solution for this ?
I installed a fresh a2billing and having exactly the same problem.
When I turn of the debuging it runs normal.

thanks


Top
 Profile  
 
 Post subject:
PostPosted: Sat Dec 20, 2008 11:47 am 
Offline

Joined: Sun Aug 17, 2008 1:52 pm
Posts: 93
Maarten wrote:
Hi,

Did somebody found a solution for this ?
I installed a fresh a2billing and having exactly the same problem.
When I turn of the debuging it runs normal.

thanks


It is related to syslogd but I also don't have solution for it.


thanks


Top
 Profile  
 
 Post subject:
PostPosted: Mon Dec 22, 2008 12:52 am 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 2:19 pm
Posts: 2890
Location: Devon, UK
Specifically, unless my memory deceives me, it was the version of syslog-ng shipping with CentOS 5.2, and the problem is that it burns 100% CPU with very little input to log. I've never seen this problem using any version of syslog-ng on Gentoo so I can't suggest what the root-cause of the problem may be. You could try switching to a different syslog-daemon, if CentOS provide that option.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 24 posts ]  Go to page Previous  1, 2
Hosted Voice Broadcast


All times are UTC


Who is online

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