Echolink channel driver

Mike - KK4ECD

6 Nov 2011 6 Nov '11

1:25 p.m.

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}

...

Asterisk ended with exit status 139 [root@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}

...

Attachments:

attachment.html (text/html — 4.1 KB)

Show replies by date

Jim Duuuude

6 Nov 6 Nov

3:04 p.m.

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@gmail.com To: app_rpt-users@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@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 139Asterisk exited on signal 11.Automatically restarting Asterisk. [root@sealink1 asterisk]# vi echolinmpg123: no process killedk.conf[root@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 139Asterisk exited on signal 11.Automatically restarting Asterisk.asterisk mpg123: no process killed _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Mike - KK4ECD

3:13 p.m.

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@hotmail.com] Sent: Sunday, November 06, 2011 10:05 AM To: kk4ecd@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@gmail.com To: app_rpt-users@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}

...

...

Asterisk ended with exit status 139 Asterisk exited on signal 11. Automatically restarting Asterisk. [root@sealink1 asterisk]# vi echolinmpg123: no process killed k.conf [root@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Jim Duuuude

3:19 p.m.

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@gmail.com To: app_rpt-users@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@hotmail.com] Sent: Sunday, November 06, 2011 10:05 AM To: kk4ecd@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@gmail.com To: app_rpt-users@ohnosec.org Date: Sun, 6 Nov 2011 08:25:38 -0500 Subject: [App_rpt-users] Echolink channel driverHi 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@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 139Asterisk exited on signal 11.Automatically restarting Asterisk. [root@sealink1 asterisk]# vi echolinmpg123: no process killedk.conf[root@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 139Asterisk exited on signal 11.Automatically restarting Asterisk.asterisk mpg123: no process killed _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Shaun Rudling

3:51 p.m.

Hahah Tehehe, you guys make me laugh. This was just what I needed to break the tension in my radio shack. Listen, I have been attempting to get my first allstar server with one node up and running, and after 1 month, i am still trying to do a successful netinstall. Tried VMware off Windows7 64bit, but it does not see the URI. Tried a clean install on my new I3, nothing. Get all sorts of errors like: "Could not allocate requested partitions: not enough free space on disks. Press OK to excit the installer." (WTF! it is a 500GB SeaGate.) That is with XIPER. I was stupid enough to mention my ambitious goals to the club members, now they keep asking for a progress report. I aslo tried ACID with no luck. Even tried a fresh install on my ASUS NETBOOK. Nothing. I sent out a few weak email help requests, but got nothing back. I need a *sh1t, shower & shave* but yet I still want to carry on until I drop dead. Viva app_rpt, Viva! BTW! we do need more documentation, BUT programmers don't write books, they program with there own language. You need a different Ham volunteer to be able to document this concept. Does a baker ever try change his brake fluid? He he did, he would make a mess. Mike, Leave the programmer alone to squeeze out all the bugs. Their human communication skills are not always the best. Jim, keep up the good work you are doing in your department, and do not "Im removing it! , JIM WB6NIL" I gues programmers are a special breed, requiring one to have thick skin to throw off all the bickering flung at them. Shaun zr5s On 06/11/11 17:19, Jim Duuuude wrote:

...

Mike - KK4ECD

4 p.m.

Oops. http://www.sunsetpointe.net/allstar Still VERY much under construction. Louie KC1AR and I are working on it. Will pull in from multiple sources as well. I do have extensive experience with Asterisk in the production PBX environment but am still wrapping my head around the AllStar idiosyncrasies. FWIW, M Sent from my iPhone. On Nov 6, 2011, at 10:19, Jim Duuuude <telesistant@hotmail.com> wrote:

...

Jim Duuuude

4:38 p.m.

I will repeat myself, once again on this issue. We ALREADY HAVE a documentation site which we would LOVE people to contribute to. All you have to do is request a login and Steve, WA6ZFT will get you one. There is not need nor desire to have *ANY* external sites for this purpose, and doing so would do nothing other then generate confusion and most likely spread mis-information (kind of the old addage regarding having one watch, you may have good reason to think you know what time it is; having 2 or more watches merely causes to know for a fact that you dont). JIM WB6NIL CC: app_rpt-users@ohnosec.org From: kk4ecd@gmail.com Subject: Re: [App_rpt-users] Echolink channel driver Date: Sun, 6 Nov 2011 11:00:25 -0500 To: telesistant@hotmail.com Oops. http://www.sunsetpointe.net/allstar Still VERY much under construction. Louie KC1AR and I are working on it. Will pull in from multiple sources as well. I do have extensive experience with Asterisk in the production PBX environment but am still wrapping my head around the AllStar idiosyncrasies. FWIW,M Sent from my iPhone. On Nov 6, 2011, at 10:19, Jim Duuuude <telesistant@hotmail.com> wrote: 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@gmail.com To: app_rpt-users@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@hotmail.com] Sent: Sunday, November 06, 2011 10:05 AM To: kk4ecd@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@gmail.com To: app_rpt-users@ohnosec.org Date: Sun, 6 Nov 2011 08:25:38 -0500 Subject: [App_rpt-users] Echolink channel driverHi 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@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 139Asterisk exited on signal 11.Automatically restarting Asterisk. [root@sealink1 asterisk]# vi echolinmpg123: no process killedk.conf[root@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 139Asterisk exited on signal 11.Automatically restarting Asterisk.asterisk mpg123: no process killed _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Mike - KK4ECD

5:14 p.m.

Great! So.. Where is it? From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Sunday, November 06, 2011 11:39 AM To: kk4ecd@gmail.com Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink channel driver I will repeat myself, once again on this issue. We ALREADY HAVE a documentation site which we would LOVE people to contribute to. All you have to do is request a login and Steve, WA6ZFT will get you one. There is not need nor desire to have *ANY* external sites for this purpose, and doing so would do nothing other then generate confusion and most likely spread mis-information (kind of the old addage regarding having one watch, you may have good reason to think you know what time it is; having 2 or more watches merely causes to know for a fact that you dont). JIM WB6NIL _____ CC: app_rpt-users@ohnosec.org From: kk4ecd@gmail.com Subject: Re: [App_rpt-users] Echolink channel driver Date: Sun, 6 Nov 2011 11:00:25 -0500 To: telesistant@hotmail.com Oops. http://www.sunsetpointe.net/allstar Still VERY much under construction. Louie KC1AR and I are working on it. Will pull in from multiple sources as well. I do have extensive experience with Asterisk in the production PBX environment but am still wrapping my head around the AllStar idiosyncrasies. FWIW, M Sent from my iPhone. On Nov 6, 2011, at 10:19, Jim Duuuude <telesistant@hotmail.com> wrote: 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@gmail.com To: app_rpt-users@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@hotmail.com] Sent: Sunday, November 06, 2011 10:05 AM To: kk4ecd@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@gmail.com To: app_rpt-users@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}

...

...

Jim Duuuude

5:17 p.m.

http://ohnosec.org/drupal From: kk4ecd@gmail.com To: telesistant@hotmail.com CC: app_rpt-users@ohnosec.org Subject: RE: [App_rpt-users] Echolink channel driver Date: Sun, 6 Nov 2011 12:14:59 -0500 Great! So…. Where is it? From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Sunday, November 06, 2011 11:39 AM To: kk4ecd@gmail.com Cc: app_rpt mailing list Subject: RE: [App_rpt-users] Echolink channel driver I will repeat myself, once again on this issue. We ALREADY HAVE a documentation site which we would LOVE people to contribute to. All you have to do is request a login and Steve, WA6ZFT will get you one. There is not need nor desire to have *ANY* external sites for this purpose, and doing so would do nothing other then generate confusion and most likely spread mis-information (kind of the old addage regarding having one watch, you may have good reason to think you know what time it is; having 2 or more watches merely causes to know for a fact that you dont). JIM WB6NILCC: app_rpt-users@ohnosec.org From: kk4ecd@gmail.com Subject: Re: [App_rpt-users] Echolink channel driver Date: Sun, 6 Nov 2011 11:00:25 -0500 To: telesistant@hotmail.comOops. http://www.sunsetpointe.net/allstar Still VERY much under construction. Louie KC1AR and I are working on it. Will pull in from multiple sources as well. I do have extensive experience with Asterisk in the production PBX environment but am still wrapping my head around the AllStar idiosyncrasies. FWIW,M Sent from my iPhone. On Nov 6, 2011, at 10:19, Jim Duuuude <telesistant@hotmail.com> wrote: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 WB6NILFrom: kk4ecd@gmail.com To: app_rpt-users@ohnosec.org Date: Sun, 6 Nov 2011 10:13:37 -0500 Subject: Re: [App_rpt-users] Echolink channel driverOK, 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@hotmail.com] Sent: Sunday, November 06, 2011 10:05 AM To: kk4ecd@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 WB6NILFrom: kk4ecd@gmail.com To: app_rpt-users@ohnosec.org Date: Sun, 6 Nov 2011 08:25:38 -0500 Subject: [App_rpt-users] Echolink channel driverHi 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@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 139Asterisk exited on signal 11.Automatically restarting Asterisk. [root@sealink1 asterisk]# vi echolinmpg123: no process killedk.conf[root@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 139Asterisk exited on signal 11.Automatically restarting Asterisk.asterisk mpg123: no process killed _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Bote Man

4:11 p.m.

New subject: Allstar documentation

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@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jim Duuuude Sent: Sunday, 06 November, 2011 10:20 To: kk4ecd@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@gmail.com To: app_rpt-users@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@hotmail.com] Sent: Sunday, November 06, 2011 10:05 AM To: kk4ecd@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@gmail.com To: app_rpt-users@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@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@sealink1 asterisk]# vi echolinmpg123: no process killed k.conf [root@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@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Jim Duuuude

4:34 p.m.

New subject: Allstar documentation

I have sent a private email to Steve, WA6ZFT asking him to look into your attempt to sign up for write access to the drupal documentation site. This is not something that I do directly myself. He is very particular with details and extremely reliable, and will respond as soon as he can. JIM From: bote_radio@botecomm.com To: app_rpt-users@ohnosec.org Date: Sun, 6 Nov 2011 11:11:14 -0500 Subject: [App_rpt-users] Allstar documentation 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. BoteW4NUD From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Jim Duuuude Sent: Sunday, 06 November, 2011 10:20 To: kk4ecd@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 WB6NILFrom: kk4ecd@gmail.com To: app_rpt-users@ohnosec.org Date: Sun, 6 Nov 2011 10:13:37 -0500 Subject: Re: [App_rpt-users] Echolink channel driverOK, 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@hotmail.com] Sent: Sunday, November 06, 2011 10:05 AM To: kk4ecd@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 WB6NILFrom: kk4ecd@gmail.com To: app_rpt-users@ohnosec.org Date: Sun, 6 Nov 2011 08:25:38 -0500 Subject: [App_rpt-users] Echolink channel driverHi 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@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 139Asterisk exited on signal 11.Automatically restarting Asterisk. [root@sealink1 asterisk]# vi echolinmpg123: no process killedk.conf[root@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 139Asterisk exited on signal 11.Automatically restarting Asterisk.asterisk mpg123: no process killed _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users _______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Stephen Rodgers

7 Nov 7 Nov

1:32 a.m.

New subject: Allstar documentation

On 11/06/2011 08:11 AM, Bote Man wrote:

...

It use to be that anyone could get a Drupal account. Unfortunately, that had to end because of the Bots signing up for accounts. A user name is NOT required for read access. You have to request write access. Send a message to staff@allstarlink.org with a few good reasons why you think we should grant you write access and we'll decide if its a good thing to do. Steve WA6ZFT

Lu Vencl

10:54 a.m.

New subject: Allstar documentation

I can say this that Bote would be a great asset in getting write access. He has done extensive work and is very knowledgeable in Linux and VOIP. Furthermore, as some might not know, he has been very involved in many of the different platforms. In fact, he is source of all the professional voice prompts we hear on IRLP and EL. So for what it is worth, I hope that when he applies, that whomever reads this will give him consideration as he and I have been discussing this very issue for months now. Lu KA4EPS -----Original Message----- From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Stephen Rodgers Sent: Sunday, November 06, 2011 8:33 PM To: app_rpt-users@ohnosec.org Subject: Re: [App_rpt-users] Allstar documentation On 11/06/2011 08:11 AM, Bote Man wrote:

...

5414

Age (days ago)

5415

Last active (days ago)

List overview

Download

12 comments

6 participants

participants (6)

Bote Man
Jim Duuuude
Lu Vencl
Mike - KK4ECD
Shaun Rudling
Stephen Rodgers