Very interesting.. I will try that and report back..
The odd thing is that Asterisk will eventually start, but it takes about 5 minutes or so to settle down.
KA4EPS
From: Don Hackler [mailto:donh@sigma.net]
Sent: Saturday, October 06, 2012 3:00 AM
To: app_rpt-users@ohnosec.org
Cc: Lu Vencl; Scott Weis; Steve Agee
Subject: Re: [App_rpt-users] mpg123: no process killed - Asterisk endedwith exit status 1
When I had this problem, I tried to install a few times and kept coming up with this error. I had to download a fresh copy of the install CD to
correct the problem. There was a subtle problem in the downloaded bits on the first CD.
On Oct 5, 2012, at 10:44 PM, Steve Agee <n5zua@earthlink.net> wrote:
I'm having this issue as well on a fresh install. The machine is 64 bit:
[Oct 5 22:42:47] ERROR[23279] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
3. If you need Zaptel services, you must correctly configure Zaptel.
mpg123: no process killed
Asterisk ended with exit status 1
Asterisk died with code 1.
Automatically restarting Asterisk.
N5ZUA