<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.telephony.pbx.asterisk.user">
    <title>gmane.comp.telephony.pbx.asterisk.user</title>
    <link>http://blog.gmane.org/gmane.comp.telephony.pbx.asterisk.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275877"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275876"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275875"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275874"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275873"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275872"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275871"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275870"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275869"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275868"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275867"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275866"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275865"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275864"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275863"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275862"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275861"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275860"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275859"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275858"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275877">
    <title>Re: Asterisk Log rotate not working</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275877</link>
    <description>&lt;pre&gt;
How can you tell that the logrotate cron job was run?

At what time it was configured to run? Did you see its output in the
logs?

And please, do make some minimal effort to RTFM and answer questions on
your own. Some tools for your disposal:

  rpm -ql logrotate | grep cron
  grep -i crom /var/log/messages

Cron jobs which have failed and/or had an output send a message to the
user who ran them (root, in your case). Is there a "sendmail" (sendmail,
postfix, whatever) running on the system? If so, where does root's mail
go to? Read it.

&lt;/pre&gt;</description>
    <dc:creator>Tzafrir Cohen</dc:creator>
    <dc:date>2013-05-23T05:25:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275876">
    <title>Diversion vs. P-Asserted-Id vs. Remote-Party-Id vs. P-Charge-Info vs. From Fields</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275876</link>
    <description>&lt;pre&gt;We have a scenario where we wish to present a toll-free caller id, yet have
our calls rated based on our billing-telephone-number.   Is it possible to
present a number in the sip header for billing and another number in the
header for jurisdicional call rating?

Whereas today, all of our calls are billed at the highest rate
(intra-state) because we're presenting a number that isn't in the lerg...
 i.e., toll-free...

Does anyone have any experience with this?

Thanks,
Optimistic...
--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Positively Optimistic</dc:creator>
    <dc:date>2013-05-23T00:04:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275875">
    <title>Re: Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275875</link>
    <description>&lt;pre&gt;

Easily, as long as you have no media :)

Use -sn uac_pcap instead of -sn uac to test with RTP (and watch your call count drop). Add recording (MixMonitor()) to your dialplan and watch the call count go down even more. ;)

A rough way to see if call quality is deteriorating would be to call your Asterisk box while the SIPP test is running and listen to some message played via Background().


--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Marie Fischer</dc:creator>
    <dc:date>2013-05-22T21:30:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275874">
    <title>Re: Asterisk Log rotate not working</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275874</link>
    <description>&lt;pre&gt;Jim,

Cron and Logrotate already installed in my machine and already configured
as the steps you enlisted. But still logrotate is not running.


Date: Tue, 21 May 2013 12:28:31 -0700


&lt;/pre&gt;</description>
    <dc:creator>Ahmed Munir</dc:creator>
    <dc:date>2013-05-22T18:54:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275873">
    <title>Re: Failed to authenticate device "Ext 110"</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275873</link>
    <description>&lt;pre&gt;
There are no REGISTER requests in that trace.  All I see are SUBSCRIBE, NOTIFY,
OPTIONS, and INVITE dialogs.


This is just a failed INVITE probably due to the username and/or password being
incorrect.  It's also possible that bad ACLs (see the 'permit/deny/acl' settings
in sip.conf) could be to blame.  It's hard to say without seeing a full SIP
trace and Asterisk CLI output.


Start there and work through the obvious issues one by one.  First, figure out
why the phone is showing up on port 5062 and correct it if necessary.  Then,
double-check the username and password.  Keep going down that path until it
leads to a resolution or report back to the list if you run into a roadblock.

Regards,

Matthew Roth
InterMedia Marketing Solutions
Software Engineer and Systems Developer

--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Matthew J. Roth</dc:creator>
    <dc:date>2013-05-22T17:18:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275872">
    <title>Re: Fw:  Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275872</link>
    <description>&lt;pre&gt;El 22/05/13 12:25, Paul Belanger escribió:
Hi!
   I haven't used it, but there is a quality test algorithm provided by 
ITU.

http://stackoverflow.com/questions/2329403/how-to-start-a-voice-quality-pesq-test
http://en.wikipedia.org/wiki/PESQ
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&amp;amp;arnumber=6043771&amp;amp;queryText%3DDevelopment+of+a+Speech+Quality+Monitoring+Tool+based+on+ITU-T+P.862



-----
CeSPI 
Centro Superior para el Procesamiento de la Información

Universidad Nacional de La Plata
-------------------------------------------------------------------------------
Proteja el Medioambiente. No imprima este mail si no es absolutamente necesario

--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Matias Banchoff</dc:creator>
    <dc:date>2013-05-22T15:50:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275871">
    <title>Re: Fw:  Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275871</link>
    <description>&lt;pre&gt;
Once upon a time, we set out to create exactly this for testing 
asterisk.  Our goal would have been to run the test every week, 
comparing the results from the previous week, to make sure asterisk's 
performance was not getting worse as new commits happened.

We came up with the idea of loading testing asterisk using SIPp or some 
other dialer, then determining at what point asterisk would start 
failing (performance).  We decided the point of failure was quality of 
audio, since it is usually the first thing to go (even though call 
control still works).

It took a while, but with the help of Leif, we found a tool to analyse 
audio streams (using MOS score[1]).  Basically, you take the original 
audio file, play it across the network, then record the other side. 
Then, comparing the two files via Aqua, you get your MOS score.

If the score was less then x, you knew asterisk was hitting a 
performance limit.  Track that over time and concurrent calls, you have 
your metrics.

[1] http://www.sevana.fi/aqua.php

&lt;/pre&gt;</description>
    <dc:creator>Paul Belanger</dc:creator>
    <dc:date>2013-05-22T15:25:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275870">
    <title>Re: Auto dialer scripts and software</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275870</link>
    <description>&lt;pre&gt;

To be an 'atomic' operation, doesn't the 'temporary' directory need to be 
on the same file system as the 'outgoing' directory?

&lt;/pre&gt;</description>
    <dc:creator>Steve Edwards</dc:creator>
    <dc:date>2013-05-22T15:14:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275869">
    <title>Error 488 Not Acceptable Here</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275869</link>
    <description>&lt;pre&gt;Hi guys,

Any idea why I am getting this error when someone tries to send me a T38 
Fax?

--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Andrew Colin</dc:creator>
    <dc:date>2013-05-22T14:39:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275868">
    <title>Re: Fw:  Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275868</link>
    <description>&lt;pre&gt;I believe there are options for rtp / audio..

Look at pcap play and rtp echo...

Transcoding would be another beast - if you are allowing it

Sent from my iPhone 5

On May 22, 2013, at 10:02 AM, Tommy Cooper &amp;lt;tomcooper83&amp;lt; at &amp;gt;yahoo.com&amp;gt; wrote:

--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Robert-GMAIL</dc:creator>
    <dc:date>2013-05-22T14:27:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275867">
    <title>Fw:  Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275867</link>
    <description>&lt;pre&gt;From the little experience I have I do not think that that is a good way of testing the quality of voice. SIP only initiates and eventually terminates the call, once that the call is connected, SIP and therefore Asterisk are no longer involved. Once the call is connected it is assigned to a trapsport layer protocol such as RTP. RTP is the actual protocol that delivers the voice call between endpoints. I  believe that the setup of your network, QoS, codecs etc... determine the voice quality of your system.

 
----- Forwarded Message -----
From: Mitul Limbani &amp;lt;mitul&amp;lt; at &amp;gt;enterux.in&amp;gt;
To: Tommy Cooper &amp;lt;tomcooper83&amp;lt; at &amp;gt;yahoo.com&amp;gt;; Asterisk Users Mailing List - Non-Commercial Discussion &amp;lt;asterisk-users&amp;lt; at &amp;gt;lists.digium.com&amp;gt; 
Sent: Wednesday, May 22, 2013 3:23 PM
Subject: Re: [asterisk-users] Stress testing Asterisk



I have a question here. 

How can we test the quality of voice upon increasing the call load?

Can we try passing a voice file using sipp and record the same in dial plan record application ? Is this reliable enough to simulate near real world scenario?

Mitul

On Wednesday, May 22, 2013, Tommy Cooper wrote:

Thank you for your help I finally solved this issue. Is it possible that my setup can achieve 212 concurrent calls, I am running Asterisk on just 1 core using 3.5 GHz, and 1Gb of RAM?

&lt;/pre&gt;</description>
    <dc:creator>Tommy Cooper</dc:creator>
    <dc:date>2013-05-22T14:02:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275866">
    <title>Changes to the community service maintenancenotifications</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275866</link>
    <description>&lt;pre&gt;You may have noticed (or maybe not) that there have been several
maintenance notifications for the asterisk.org community services this
month. We are working hard to keep up the services running smoothly,
and those notices are sent whenever we think our maintenance may
interfere with the operation of any of the services.

So far, it's been our policy that we send out a maintenance
notification whenever we do anything other than the most minor
maintenance on the services. You can usually read "may have
intermittent availability" as "it should be available unless things go
horribly wrong".

We now realize that most of these notifications are just spam for most
of the community. It is also cumbersome for us to send out the
notifications every time we touch the services. Especially considering
that the services are typically unavailable for at most a few minutes,
if at all.

In an effort to reduce spam and make service availability more
predictable, we're changing the policy about when we send
notifications about community service availability.

Starting on Monday, May 27th, we will have a regular maintenance
window every Monday for one hour starting at 9:00 PM Central Time
(that's 02:00 UTC during daylight saving time in the summer, and 03:00
UTC during standard time). We will try to restrict the service
impacting maintenance to that weekly window.

For the times where there might be a service interruption outside of
that window (either when it needs to be coordinated with our colo
provider, or if the maintenance will take longer than one hour), we
will send notice of the impending service interruption to just the
asterisk-announce mailing list[1].

This will help us in planning service upgrades and maintenance, and
reduce the amount of unnecessary email for the community.

 [1]: http://lists.digium.com/mailman/listinfo/asterisk-announce

 -- Digium's Asterisk Development Team


--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Asterisk Development Team</dc:creator>
    <dc:date>2013-05-22T13:56:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275865">
    <title>Re: Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275865</link>
    <description>&lt;pre&gt;I have a question here.

How can we test the quality of voice upon increasing the call load?

Can we try passing a voice file using sipp and record the same in dial plan
record application ? Is this reliable enough to simulate near real world
scenario?

Mitul

On Wednesday, May 22, 2013, Tommy Cooper wrote:


&lt;/pre&gt;</description>
    <dc:creator>Mitul Limbani</dc:creator>
    <dc:date>2013-05-22T13:23:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275864">
    <title>Fw:  Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275864</link>
    <description>&lt;pre&gt;Thank you for your help I finally solved this issue. Is it possible that my setup can achieve 212 concurrent calls, I am running Asterisk on just 1 core using 3.5 GHz, and 1Gb of RAM?


----- Forwarded Message -----
From: Marie Fischer &amp;lt;marie&amp;lt; at &amp;gt;vtl.ee&amp;gt;
To: Asterisk Users Mailing List - Non-Commercial Discussion &amp;lt;asterisk-users&amp;lt; at &amp;gt;lists.digium.com&amp;gt; 
Sent: Wednesday, May 22, 2013 1:16 PM
Subject: Re: [asterisk-users] Stress testing Asterisk



On 21.05.2013, at 0:05, Tommy Cooper &amp;lt;tomcooper83&amp;lt; at &amp;gt;yahoo.com&amp;gt; wrote:


Do you have a peer and extension configured for SIPP in your Asterisk configuration? You also needat least the -s &amp;lt;extension_to_dial&amp;gt; option on your sipp command line.
http://hasnainali.wordpress.com/2009/03/12/using-sipp-for-stress-testing-asterisk/has some simple instructions which should get you started.
If the calls still fail, Asterisk console output would be helpful.



--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Tommy Cooper</dc:creator>
    <dc:date>2013-05-22T13:18:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275863">
    <title>Re: Auto dialer scripts and software</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275863</link>
    <description>&lt;pre&gt;Calls on behalf of political candidates are generally legal--even to people
on the "do not call" lists. It doesn't seem to be possible to pass
legislation preventing them.

--Don

 


-----Original Message-----
From: asterisk-users-bounces&amp;lt; at &amp;gt;lists.digium.com
[mailto:asterisk-users-bounces&amp;lt; at &amp;gt;lists.digium.com] On Behalf Of Chris Bagnall
Sent: Wednesday, May 22, 2013 6:48 AM
To: asterisk-users&amp;lt; at &amp;gt;lists.digium.com
Subject: Re: [asterisk-users] Auto dialer scripts and software

On 22/5/13 10:54 am, A J Stiles wrote:
right?

And it's worth adding that even if it is legal in your country, you're
almost guaranteed to offend/annoy your target audience. Recorded calls
always do.

Kind regards,

Chris
--
This email is made from 100% recycled electrons

--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Don Kelly</dc:creator>
    <dc:date>2013-05-22T12:54:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275862">
    <title>Re: Auto dialer scripts and software</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275862</link>
    <description>&lt;pre&gt;
And it's worth adding that even if it is legal in your country, you're 
almost guaranteed to offend/annoy your target audience. Recorded calls 
always do.

Kind regards,

Chris
&lt;/pre&gt;</description>
    <dc:creator>Chris Bagnall</dc:creator>
    <dc:date>2013-05-22T11:47:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275861">
    <title>Re: Stress testing Asterisk</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275861</link>
    <description>&lt;pre&gt;
On 21.05.2013, at 0:05, Tommy Cooper &amp;lt;tomcooper83&amp;lt; at &amp;gt;yahoo.com&amp;gt; wrote:


Do you have a peer and extension configured for SIPP in your Asterisk configuration? You also needat least the -s &amp;lt;extension_to_dial&amp;gt; option on your sipp command line.
http://hasnainali.wordpress.com/2009/03/12/using-sipp-for-stress-testing-asterisk/ has some simple instructions which should get you started.
If the calls still fail, Asterisk console output would be helpful.



--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Marie Fischer</dc:creator>
    <dc:date>2013-05-22T11:16:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275860">
    <title>Re: Auto dialer scripts and software</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275860</link>
    <description>&lt;pre&gt;
You do know that sort of thing is against the law -- or at least requires a 
permit from the authorities -- in most civilised countries, right?  You can 
get into a *lot* of trouble if you are not careful.

If you are quite sure it's legal in your jurisdiction, and you have written 
permission if required, then it's a simple enough matter just to create a call 
file that will connect some real-world number with a local extension which just 
waits for the call to be bridged, then plays a sound file.  Easy enough in your 
favourite scripting language.


If the call file is definitely smaller than one block  (the size of which 
depends on your file system),  it should be OK to write in situ.  Otherwise, 
write it under /tmp or somewhere and then use the system command "mv" to move 
it to /var/spool/asterisk/outgoing/ after closing it.

&lt;/pre&gt;</description>
    <dc:creator>A J Stiles</dc:creator>
    <dc:date>2013-05-22T09:54:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275859">
    <title>Automatic Speech Recognition and Text To Speechusing iSpeech</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275859</link>
    <description>&lt;pre&gt;Hi,

a set of AGI scripts that provide ASR and TTS for asterisk using the
iSpeech API (http://www.ispeech.org/) are available on this page:

http://zaf.github.io/asterisk-ispeech/

This is the first public release, updates will soon follow.
Feel free to test and report.

Regards,

Lefteris Zafiris
--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Lefteris Zafiris</dc:creator>
    <dc:date>2013-05-22T00:11:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275858">
    <title>Re: Asterisk Log rotate not working</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275858</link>
    <description>&lt;pre&gt;
Ahmed,

Proper log rotation depends on a couple things working together 
correctly to get the job done.  First, you need to make sure you have 
the space to rotate the logs.  If you have compression enabled, 
logrotate creates a copy of the file(s) as it compresses them.  You 
could be running out of space???

Next you need to verify that everything is in place, follow these steps 
to do so.  Keep in mind that I have CentOS 6.4.  So the packages might 
differ a little in the name and surely in the version numbering.

  1) Verify logrotate is installed to your system.
     # yum install logrotate

     if it asks you to install it, do so.

  2) Verify that crond is installed and running.
     Below is the output I get when searching yum to see if crond is 
installed.  If your query returns nothing then crond is not installed.

   [root&amp;lt; at &amp;gt;jim etc]# yum list all | grep ^cron | grep "&amp;lt; at &amp;gt;"
   cronie.x86_64                             1.4.4-7.el6 
    &amp;lt; at &amp;gt;anaconda-CentOS-201303020151.x86_64/6.4
   cronie-anacron.x86_64                     1.4.4-7.el6 
    &amp;lt; at &amp;gt;anaconda-CentOS-201303020151.x86_64/6.4
   crontabs.noarch                           1.10-33.el6 
    &amp;lt; at &amp;gt;anaconda-CentOS-201303020151.x86_64/6.4

     If crond is not installed, then you will need to install it.  Once 
you have it installed, move on to the next step.

  3) Make sure crond is setup to start at boot time.

   chkconfig crond on

  4) Verify that logrotate is in one of the cron include folders.  Mine 
is located in the cron.daily folder.

   [root&amp;lt; at &amp;gt;jim etc]# find /etc/*/logrotate
   /etc/cron.daily/logrotate

   If you don't find that the above file exists, you might need to 
re-install logrotate.

Next I would've had you verify that you have a config file in 
/etc/logrotate.d/ for the asterisk log files.  But it seems you already 
to.  After all this, if it still isn't working, double check all the 
steps above.

Let us know if this does or doesn't help.

--
Jim Lucas

--
_____________________________________________________________________
&lt;/pre&gt;</description>
    <dc:creator>Jim Lucas</dc:creator>
    <dc:date>2013-05-21T19:28:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275857">
    <title>Re: Asterisk Log rotate not working</title>
    <link>http://permalink.gmane.org/gmane.comp.telephony.pbx.asterisk.user/275857</link>
    <description>&lt;pre&gt;Checked in /var/logs/ directory, all logs are not rotating by logrotate.
Please advise how can I overcome this issue as I'm using CentoOS 5




From: Chris Bagnall &amp;lt;asterisk&amp;lt; at &amp;gt;lists.minotaur.cc&amp;gt;


&lt;/pre&gt;</description>
    <dc:creator>Ahmed Munir</dc:creator>
    <dc:date>2013-05-21T18:54:04</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.telephony.pbx.asterisk.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.telephony.pbx.asterisk.user</link>
  </textinput>
</rdf:RDF>
