search for: amcrory

...4.LSE.i386.rpm perl-mime-construct-1.9-1.RHEL4.LSE.i386.rpm perl-Net-Telnet-3.03-1.RHEL4.LSE.i386.rpm perl-Proc-WaitStat-1.00-1.RHEL4.LSE.i386.rpm As you should expect theses packages come with no warranty whatsoever but I would like some feedback so please feel free to contact me via email - amcrory<aT>linuxsys<Dot>com. Best Regards, Andrew McRory - President / CTO Linux Systems Engineers, Inc. Located in beautiful Tallahassee, Florida (850) 224-5737 x2005

Available in the usual place. ftp://ftp.linuxsys.com/pub/releases/CentOS-4.0 This release includes minor spec changes, spandsp 0.0.2pre23, a new Sangoma wanpipe RPM for use with the LSE kernel rpm and an AMP installation document. Best Regards, -- Andrew McRory - President/CTO Linux Systems Engineers, Inc. - http://www.linuxsys.com Located in beautiful Tallahassee, Florida Office

On Thu, 5 Aug 2004 asterisk-users-request@lists.digium.com wrote: > Date: Thu, 5 Aug 2004 14:56:06 -0400 (EDT) > From: Andrew McRory <amcrory@linuxsys.com> > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] PRI Errors... Ouch > Reply-To: asterisk-users@lists.digium.com > > > Today is the first time I've had any show stopping errors with asterisk > since I started using it over 8 months ago......

..."me" error and that Digium can squash this bug (or new hardware fixes it). Either way, when this is over, perhaps I can provide some troubleshooting documentation for these errors. ---------- Forwarded message ---------- Date: Mon, 3 Jan 2005 09:36:51 -0500 (EST) From: Andrew McRory <amcrory@linuxsys.com> To: support@digium.com Subject: PRI Errors (HDLC Abort (6) on Primary D-channel) Hello, I called last week and got a ticket number (13329) but have not yet received a call back. My T400P card that I use to serve my phone system and take incoming V.90 callers is dropping all chan...

System is built on a SuperMicro motherboard with Serverworks chipset, IRQ is not shared. Have a dialplan that worked for 8 months without errors, tried reverting to older release then upgraded to 1.0.3 stable release, currently running on fedora core 1 kernel 2.4.22-nptl.2199 (have tried plain jayne), telco says "it's not us", HDLC abort seems to occur when when a Zap channel hangs

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 2848 bytes Desc: image001.jpg Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20050111/b2d08439/attachment.jpeg -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

Greetings folks, I have updated our asterisk RPM repository with CVS builds for RH 7.3, 9 and FC1. The zaptel package is compiled against the supplied kerenel rpm and SRPMS are supplied for those wishing to rebuild. Other than the CVS update no other changes are made from previous releases... Features ======== Security: runs as user asterisk not root Convienance: Console automatically runs

Today is the first time I've had any show stopping errors with asterisk since I started using it over 8 months ago... While I wait on the telco to check the circuit I thought I would post this here. Not sure yet but I thinks my 4-port PRI card is gone!!! I made a call and right when the person answered - BOOM. This is only a little better than it not working at all.

Hi folks, Anyone want to check out the subject packages will find them here: ftp://www.linuxsys.com/pub/testing/asterisk The asterisk RPMS now include builds of asterisk, addons, astcc, btp, gastman, iaxproxy, libpri and zaptel from 10.04.04 CVS. zaptel is compiled and working with kernel-2.4.22-0.FC1.LSE.p3.i686.rpm available with ALSA modules and supporting packages here:

So it was working for several days without error then tonight while I'm watching users login to the modem pool - BOOM! The sync changes when it happens (which makes sense). Zaptel: Master changed to Tor2/0/2 Zaptel: Master changed to Tor2/0/1 Zaptel: Master changed to Tor2/0/2 Zaptel: Master changed to Tor2/0/1 Interrupts should not be a factor THIS time: [root@phone asterisk]# cat

safe_asterisk used to work fine but with v1.0.3 I am getting all kinds of permission errors, intermittant failures, etc. Even with file permissions relaxed and ownership set to asterisk it craps out. Seems to work fine when run as root. Comments??? -- Andrew McRory - President/CTO Linux Systems Engineers, Inc. - http://www.linuxsys.com Located in beautiful Tallahassee, Florida Office

I created a tarball for redhat 7.3 with kernel 2.4.28, asterisk v1.0.3-CVS-01.04.05 and alsa-1.0.6a... see the README / download it here: ftp://ftp.linuxsys.com/pub/packages/rh73/asterisk/ -- Andrew McRory - President/CTO Linux Systems Engineers, Inc. - http://www.linuxsys.com Located in beautiful Tallahassee, Florida Office 850-224-5737 Office 850-575-7213 Mobile 850-294-7567

Hello, I've uploaded current builds to ftp://ftp.linuxsys.com/pub/releases/FC2/asterisk-CVS ftp://ftp.linuxsys.com/pub/releases/FC2/asterisk-1.0 Regards, -- Andrew McRory - President and Chief Techincal Officer Linux Systems Engineers, Inc. - http://www.linuxsys.com Located in beautiful Tallahassee, Florida Office 850-224-5737 Office 850-575-7213 Mobile 850-294-7567

mkumar@mantragroup.com wrote: > Hi All, > > I am a newbie and trying to install Asterisk from instructions given > in http://www.voip-info.org/tiki-index.php?page=Asterisk+RPM. We have > Centos 3.3 so > I downloaded rpm's from > ftp://ftp.linuxsys.com/pub/LSE/packages/CentOS-3.4/asterisk-1.0.9/ and > tried installing one by one but I get the following errors

Well I am about to reserve a small padded room so I can bounce off the walls without inflicting tooo much damage... Nothing is making sense at this point. I tried several releases last night before settling on the latest CVS (seemed to work the best). Asterisk was running GREAT for the first few hours. Now since around 10AM EST SIP can't register and incoming calls are rejected with "all

UPDATE. The circuit has run clean since the 7th. It seems the telco found a problem after all but they can't tell me what they did... cause they think it was fixed as part of another case. Grrr. Well, I never doubted the T400P too much but I went ahead and bought a different card just in case. Haven't had to use it so far. One of the biggest reasons I did not think the Wildcard was at