Hi all,
Recently I have raised up a bug (related to segmentation fault of
asterisk process) due to a core dump generated by Asterisk under the
following environment:
CentOS release 5.7 (Final)
Kernel 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:23:01 EDT 2011 i686 i686
i386 GNU/Linux
Asterisk
El 05/09/13 07:02, Rodrigo Montiel escribió:
Hi all,
Recently I have raised up a bug (related to segmentation fault of asterisk
process) due to a core dump generated by Asterisk under the following
environment:
CentOS release 5.7 (Final)
Kernel 2.6.18-238.12.1.el5 #1 SMP Tue May 31 13:23:01
I have 2 ISDN BRI boxes, each with 4 spans, where the first one is configured as CPE, the second
one as NET(so I don't need real lines for developing and testing).
Once in a while I do see the following libpri error messages simultaneously on
both boxes:
PRI Span: 1 TEI=0 MDL-ERROR (A): Got
On Thu, Sep 5, 2013 at 1:02 PM, jg webaccou...@jgoettgens.de wrote:
I have 2 ISDN BRI boxes, each with 4 spans, where the first one is
configured as CPE, the second one as NET(so I don't need real lines for
developing and testing).
Once in a while I do see the following libpri error messages
Alex thanks for your response,
Yes, it is an Elastix and the issue has been submmited few days ago:
https://issues.asterisk.org/jira/browse/ASTERISK-22353
It is causing all calls (and call center agent connections) to be
disconnected.
Below you can see the versions involved. We will give a try
Mitul Limbani писал 05.09.2013 21:43:
Something very
similar happened on our boxes and we did nothing special apart from
changing DAHDI and Asterisk versions to higher stable (2.6.1 n 1.8.14
respectively) and it went off.
Don't really know exactly why it
happens, it would be worthwhile
Q.921 just says to log the condition and carry on as if it did not happen.
I guess you mean: carry on if it happened (and don't care any more).
Sorry, English is not my mother tongue. I didn't see the 'not'.
--
_
--
Hello,
Running one asterisk server with below details.
Only SIP to SIP calls. No real time configuration, no recording, no voicemail,
no IVR, no codec translation. Average CPU load varies between 4 to 30 for 150
to 200 concurrent calls and we start getting problem in call quality like delay
Something very similar happened on our boxes and we did nothing special
apart from changing DAHDI and Asterisk versions to higher stable (2.6.1 n
1.8.14 respectively) and it went off.
Don't really know exactly why it happens, it would be worthwhile to
investigate if you see it again on CLI or
Q.921 just says to log the condition and carry on as if it did not happen.
I guess you mean: carry on if it happened (and don't care any more).
It does not say what to do
about it.
It seems that making some calls makes these error messages go away. I am going to write a test
script that
On 13-09-05 03:11 PM, Steve Edwards wrote:
On Thu, 5 Sep 2013, Kamlesh Kumar wrote:
Running one asterisk server with below details.
Only SIP to SIP calls. No real time configuration, no recording, no
voicemail, no IVR, no codec translation. Average CPU load varies
between 4 to 30 for 150 to
On Thu, 5 Sep 2013, Kamlesh Kumar wrote:
Running one asterisk server with below details.
Only SIP to SIP calls. No real time configuration, no recording, no voicemail,
no IVR, no codec translation. Average CPU load varies between 4 to 30 for 150
to 200 concurrent calls and
we start getting
12 matches
Mail list logo
