For the life of me I cannot understand this action. Surely, Dave C is not saying bin the thing, he is pointing out the RF to RF requirement of IRLP and the difficulties of maintaining the IRLP system. Politics aside, the IRLP rules are clear and should be respected. This is something which I believe EchoIRLP has done since its inception and which, to an extent the IRLP system designer, has recognised in the modification of the troubleshoot script. Many have invested a lot of time setting up AllStar, educating users etc so why quit without at least trying to come up with an amicable solution to the updating or whatever other problem exists. The fact that AllStar nodes can provide a link into IRLP is a means of promoting the use of both systems, the traffic on which is not exactly heavy. The removal of chan_irlp is probably going to cause node owners a lot of hassle. Now, is it not possible for those responsible to put their heads together and come up with a solution similar to TBD, TheBridge rather than just dump the facility? Put it back and negotiate or design an acceptable solution as I think Tony, VK3JED is advocating. Regards, Doug - MM0BJA On 23/10/2010 12:20 PM, Stephen - K1LNX wrote:

I checked out the latest SVN update this morning and when issuing make menuselect and selecting channel drivers, chan_irlp is still present and enabled by default.

This may just be cosmetic, but thought I would point it out.

Everything else appears to be working fine.

On Fri, Oct 22, 2010 at 10:23 PM, Jim Duuuude <telesistant@hotmail.com <mailto:telesistant@hotmail.com>> wrote:

The new SVN version (sans IRLP) is now available from the SVN. I would appreciate it if at least a few people would download it and try it out to make sure I didnt break anything while 'gutting'.

Thanks.

JIM WB6NIL

_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com <mailto:App_rpt-users@qrvc.com> http://qrvc.com/mailman/listinfo/app_rpt-users

-- **************************************** Stephen Brown - ARS K1LNX Johnson City, TN EM86 http://www.k1lnx.net PSTN: 423-665-9367 SIP: k1lnx@k1lnx.net <mailto:k1lnx@k1lnx.net> ****************************************

_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users

This is very sad, I was hoping that Asterisk and IRLP could play nicely together, but I guess that is no longer the case... I guess it's time to consider pulling my support for IRLP (it's off my asterisk node already), I finally got things condensed down to a single machine and don't feel like going through the hassle of setting up another machine to run my IRLP node. Thanks to the Allstar folks for everything they do! Jim, K6JWN On Oct 23, 2010, at 5:44 AM, Jim Duuuude wrote:

Surely, that's EXACTLY what he requested that I do, and I did. As I stated very clearly before, I removed the support directly per his explicit request to do so. I am and always have been working in full cooperation with him and those are his wishes, and I followed them.

JIM WB6NIL

Date: Sat, 23 Oct 2010 13:34:00 +0100 From: specialq.que@ntlworld.com To: app_rpt-users@qrvc.com Subject: Re: [App_rpt-users] new SVN version _Removal of IRLP

For the life of me I cannot understand this action.

Surely, Dave C is not saying bin the thing, he is pointing out the RF to RF requirement of IRLP and the difficulties of maintaining the IRLP system. Politics aside, the IRLP rules are clear and should be respected.

This is something which I believe EchoIRLP has done since its inception and which, to an extent the IRLP system designer, has recognised in the modification of the troubleshoot script.

Many have invested a lot of time setting up AllStar, educating users etc so why quit without at least trying to come up with an amicable solution to the updating or whatever other problem exists. The fact that AllStar nodes can provide a link into IRLP is a means of promoting the use of both systems, the traffic on which is not exactly heavy.

The removal of chan_irlp is probably going to cause node owners a lot of hassle.

Now, is it not possible for those responsible to put their heads together and come up with a solution similar to TBD, TheBridge rather than just dump the facility?

Put it back and negotiate or design an acceptable solution as I think Tony, VK3JED is advocating.

Regards, Doug - MM0BJA

On 23/10/2010 12:20 PM, Stephen - K1LNX wrote: I checked out the latest SVN update this morning and when issuing make menuselect and selecting channel drivers, chan_irlp is still present and enabled by default.

This may just be cosmetic, but thought I would point it out.

Everything else appears to be working fine.

On Fri, Oct 22, 2010 at 10:23 PM, Jim Duuuude <telesistant@hotmail.com> wrote: The new SVN version (sans IRLP) is now available from the SVN. I would appreciate it if at least a few people would download it and try it out to make sure I didnt break anything while 'gutting'.

Thanks.

JIM WB6NIL

_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users

-- **************************************** Stephen Brown - ARS K1LNX Johnson City, TN EM86 http://www.k1lnx.net PSTN: 423-665-9367 SIP: k1lnx@k1lnx.net ****************************************

_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users

_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users______________________________... App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users