similar to: 1.4.10.[0,1] crashes when call parked

I have one system that is crashing everytime a call is parked and I have tried recompiling the asterisk, checking out the latest SVN of 1.2 and modifying the configuration. I have identified what I think is the error and have back traces but since this is occurring on only one system I want to know what might cause this. CLI: -- SIP/xlite_brr-098d1e98 is ringing -- SIP/xlite_brr-098d1e98

Hi, Try as I might, I can't get hangups detected on a Zap channel with loop start lines. So, after someone leaves a voicemail and then hangs up, Asterisk doesn't know it, exits VoicemailMain2, and loops back to the corporate greeting, tying up the line even though the outside caller has hung up. Therefore, I've added the following hideous hack - er, code - to voicemail2.c. It

In the past, there have been reports of problems with Asterisk with multiple processors and/or HyperThreading. I'm having a !@#$ of a problem with an HPDL380 with 2 3.4gHz Xeon processors, 2 gb RAM -- if I got 24 hours I'd think I had died and gone to heaven :) Am I missing something obvious like "Asterisk is single CPU, single core?" I can't access the ILO so I

I am running asterisk 1.2.27 and it dead today. The following is the backtrace of core file. Can anybody help me to identify what is the possible cause of crash? It seems the mysql connection causing problem in Thread 2. But I can not tell what exactly happened. This asterisk is using as ACD for over hundred agents. #> thread apply all bt ........ ........ Thread 6 (process 20135): #0

Hi, I'm using the following setup : Alice ---- IPPhone ------<LAN>----- Media gateway ----<PSTN> ------- Phone ---- Bob For certain calls, users complains about echo : they can ear their own voice in their handset, though media gateway echo cancel is turned on. I'm wondering how this echo cancelation engine is supposed to work. My understanding of echo is that most probably,

Full_Name: Jae Choi Version: 1.6.1 OS: linux (x86) Submission from: (NULL) (142.176.61.245) Hello, Any attempts to access the "hsv" function returns the following type of error: Error in hsv(h = seq(start, ifelse(start > end, 1, 0) + end, length = n)%%1, : color intensity 1.25, not in [0,1] (the above was generated from the demo command: > pie(rep(1, 24), col =

Hello, Anyone know why the command: > plot(x,y) where y is a 0,1 result sometimes plots the y values as 1,2 rather than 0,1? And how to prevent this? Thank you, Georgiana May [[alternative HTML version deleted]]

Funnily enough, it seems that adjustment of text in the verical direction is more flexible than in the horizontal. Horizontal adjustment parameters, seem to be set to the closest of 0 and 1 if they fall outside (0,1). Try e.g.: plot(0:1,0:1) for (a in seq(-5,5,0.5) ) text(0.5, 0.5, "Y", adj=c(0,a), cex=2, col="red" ) for (a in seq(-5,5,0.5) ) text(0.5, 0.5, "X",

Dear all, I''m working with the geometric distribution for the time being, and I''m confused. This may have more to do with statistics than R itself, but since I''m getting results from R I find counterintuitive (well, yeah, my statistical intuition has not been properly sharpened), I feel like asking. The point first: If I do > rgeom(1,prob=1) I get: [1] NaN Warning

What is the meaning of messages of this form in dmesg: [158362.148203] [drm] nouveau 0000:06:00.0: PMFB0_SUBP0: 0x037f0040 [158362.148208] [drm] nouveau 0000:06:00.0: PMFB0_SUBP1: 0x037f0000 They seem to always appear in pairs. Out of 1702 lines in dmesg, 286 of them are of the above form. I don't recall having ever seen them with Mageia 1, kernel 2.6.38.8-server-10.mga. However, there

Hi! I was trying to implement a probit model on a dichotomous outcome variable and found that the predictions were outside the (0,1) interval that one should get. I later tried it with some simulated data with a similar result. Here is a toy program I wrote and I cant figure why I should be getting such odd predictions. x1<-rnorm(1000) x2<-rnorm(1000) x3<-rnorm(1000)

Hopefully, this will do it. Includes fixes from Steven Jan Springl (Thanks Steven!) and a fix to avoid returning a response to smurfs. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

1.4.10 is available now at: http://shorewall.net/pub/shorewall/shorewall-1.4.10 ftp://shorewall.net/pub/shorewall/shorewall-1.4.10 Coming soon to a mirror near you. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Adam Jackson (6): Remove a leftover from overlay support Fix xf86ModeBandwidth check Move device ID and memory sizing much earlier in setup G200SE: Only force 16bpp on low-memory cards Fix ChangeLog generation mga 1.4.10 Alan Coopersmith (2): Remove xorgconfig & xorgcfg from See Also list in man page Add README with pointers to mailing list,

The Asterisk development team has released Asterisk versions 1.2.24 and 1.4.10. Version 1.2.24 is the final 1.2 release that contains normal bug fixes. The 1.2 branch will only be maintained with security fix releases from now until it is completely deprecated. Version 1.4.10 contains numerous bug fixes for things all over Asterisk, as well as a fix for a security issue. The security issue

The Asterisk development team has released Asterisk versions 1.2.24 and 1.4.10. Version 1.2.24 is the final 1.2 release that contains normal bug fixes. The 1.2 branch will only be maintained with security fix releases from now until it is completely deprecated. Version 1.4.10 contains numerous bug fixes for things all over Asterisk, as well as a fix for a security issue. The security issue

The Asterisk.org development team has announced the release of Zaptel versions 1.2.25 and 1.4.10. These releases contain many bug fixes as well as performance enhancements. A couple of the more major changes include: modifications to the wctdm24xxp and wcte12xp drivers to increase interrupt latency resilience, numerous bug fixes and updates to the xpp drivers, as well as some Makefile

The Asterisk.org development team has announced the release of Zaptel versions 1.2.25 and 1.4.10. These releases contain many bug fixes as well as performance enhancements. A couple of the more major changes include: modifications to the wctdm24xxp and wcte12xp drivers to increase interrupt latency resilience, numerous bug fixes and updates to the xpp drivers, as well as some Makefile

The Asterisk.org development team has announced the release of Libpri version 1.4.10. This release contains bug fixes related to handling of BRI PTMP links and how messages are handled during link state transients, as well as other fixes. Please see the Changelog for more details. The release is available as a tarball as well as a patch against the previous release. It is available for

The Asterisk.org development team has announced the release of Libpri version 1.4.10. This release contains bug fixes related to handling of BRI PTMP links and how messages are handled during link state transients, as well as other fixes. Please see the Changelog for more details. The release is available as a tarball as well as a patch against the previous release. It is available for