[App_rpt-users] Allstar documentation

Bote Man bote_radio at botecomm.com
Sun Nov 6 16:11:14 UTC 2011


I wouldn't mind helping where I can, but I signed up for the wiki months
ago and never got the confirmation e-mail to complete the process, so it
either got lost in the ether or was rejected. Is that the place?

 

I'm saving key e-mails found here in the hopes of compiling them for
documentation purposes, but where to post the compilation?

 

I've already found a number of typos, incorrect help entries, and
sentences and concepts that could be better phrased in the existing
knowledge base, so that could use some attention as well. In some cases
the only person who could possibly document certain features is some guy
named Jim Duuuuuuude so there's that. 

 

I've got until Spring Training :-) 

 

Lemme know.

 

Bote

W4NUD

 

 

From: app_rpt-users-bounces at ohnosec.org
[mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Jim Duuuude
Sent: Sunday, 06 November, 2011 10:20
To: kk4ecd at gmail.com; app_rpt mailing list
Subject: Re: [App_rpt-users] Echolink channel driver

 

Well, for "extensive" documentation, I would look where one might find
Sana Claus, the Easter Bunny, Elvis, Jimmy Hoffa's body (maybe), all the
left socks missing from the laundry, and competent, reliable drummers.
:-)

In other words, it doesn't exist. It would be nice if someone who was so
inclined
and able would contribute such a thing to our project. Unfortunately, no
one
has done so to date. 

JIM WB6NIL

  _____  

From: kk4ecd at gmail.com
To: app_rpt-users at ohnosec.org
Date: Sun, 6 Nov 2011 10:13:37 -0500
Subject: Re: [App_rpt-users] Echolink channel driver

OK, ok. Don’t throw a gasket, Jim. I’ll leave it alone.

 

Can you point me in a good direction for extensive documentation on
AllStar?

 

Mike K4NUK / VA3PS

 

From: Jim Duuuude [mailto:telesistant at hotmail.com] 
Sent: Sunday, November 06, 2011 10:05 AM
To: kk4ecd at gmail.com; app_rpt mailing list
Subject: RE: [App_rpt-users] Echolink channel driver

 

How why in the heck would you set confmode to yes? Dont touch it.
It doesnt to ANYTHING the slighetest bit useful or desirable. You dont
want it.
Dont do it. ALL echolink instances that run under app_rpt are
"conferences"
ALWAYS. That parameter was put there to placate the original person that
was
helping develop the protocol code for the driver. It isnt what you want.

Im tired of running into people just randomly setting this, and
wondering why
its broken. Im removing it!

JIM WB6NIL

  _____  

From: kk4ecd at gmail.com
To: app_rpt-users at ohnosec.org
Date: Sun, 6 Nov 2011 08:25:38 -0500
Subject: [App_rpt-users] Echolink channel driver

Hi all,

 

Been experimenting with echolink.conf, and have conference *EKOSTAR*
running based on that configuration file. 

 

Only one problem… as soon as I set confmode to =yes, it throws
segmentation faults. So presently I’m running it under confmode=no. Any
bright ideas?

 

Included below is the error it throws.

 

Many thanks in advance for any help you can provide.

 

Best,

Mike K4NUK

 

sealink1*CLI>

Disconnected from Asterisk server

/usr/sbin/safe_asterisk: line 125:  3687 Segmentation fault      (core
dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS}
${ASTARGS} >&/dev/${TTY} < /dev/${TTY}

Asterisk ended with exit status 139

[root at sealink1 asterisk]# Asterisk exited on signal 11.

Automatically restarting Asterisk.

mpg123: no process killed

/usr/sbin/safe_asterisk: line 125:  3794 Segmentation fault      (core
dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS}
${ASTARGS} >&/dev/${TTY} < /dev/${TTY}

Asterisk ended with exit status 139

Asterisk exited on signal 11.

Automatically restarting Asterisk.

 

[root at sealink1 asterisk]# vi echolinmpg123: no process killed

k.conf

[root at sealink1 asterisk]# service /usr/sbin/safe_asterisk: line 125:
3906 Segmentation fault      (core dumped) nice -n $PRIORITY
${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS} >&/dev/${TTY} <
/dev/${TTY}

Asterisk ended with exit status 139

Asterisk exited on signal 11.

Automatically restarting Asterisk.

asterisk mpg123: no process killed


_______________________________________________ App_rpt-users mailing
list App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


_______________________________________________ App_rpt-users mailing
list App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20111106/ce5d7319/attachment.html>


More information about the App_rpt-users mailing list