[App_rpt-users] New install does not ask for network settings

Bob Pyke k6ecm1 at gmail.com
Fri Sep 2 00:23:04 UTC 2016


Why not use DIAL. It is far better than ACID. The old server location now has DIAL; download from allstarlink.org. If you kept your /etc/asterisk folder with your old .config files, you are a step ahead.

Thanks,
Bob
k6ecm
73

Sent from iPad


> On Sep 1, 2016, at 4:49 PM, Steve Denbow <Kd8biw at hotmail.com> wrote:
> 
> All,
> 
> Reinstalling after a HDD crash, ACID (centos5) downloaded off the website (burnt to DVD). The original install went without a hitch about a year ago, however now it is not asking me for the network settings. As a result, I cannot download the phase2.sh script. I'm a noob to Linux, your help is appreciated. Thanks!
> 
> On Aug 31, 2016 6:29 AM, <app_rpt-users-request at ohnosec.org> wrote:
> Send App_rpt-users mailing list submissions to
>         app_rpt-users at ohnosec.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> or, via email, send a message with subject or body 'help' to
>         app_rpt-users-request at ohnosec.org
> 
> You can reach the person managing the list at
>         app_rpt-users-owner at ohnosec.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of App_rpt-users digest..."
> 
> 
> Today's Topics:
> 
>    1. Fw: cop command 2 and 3 disable enable (petem001 at gmail.com)
>    2. Server IP target address (H Hugh Flint)
>    3. Re: Server IP target address (Bob Pyke)
>    4. Problems surrounding Dial with service asterisk stop and
>       start along with restart (Loren Tedford)
>    5. Re: Problems surrounding Dial with service asterisk stop and
>       start along with restart (Steve Zingman)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 30 Aug 2016 15:03:25 -0400
> From: <petem001 at gmail.com>
> To: "APP RPT" <app_rpt-users at ohnosec.org>
> Subject: [App_rpt-users] Fw: cop command 2 and 3 disable enable
> Message-ID: <FDFAAE59BBC9400A96C9F248BF16FCF8 at PierreMartel>
> Content-Type: text/plain; charset="utf-8"
> 
> Sent this on Sunday. No answer yet.. Is it that complex?
> 
> From: Pierre Martel
> Sent: Sunday, August 28, 2016 7:13 AM
> To: APP RPT
> Subject: cop command 2 and 3 disable enable
> 
> Hi I am working on a project to interface an allstar node on a multimode digital repeater based on the MMDVM
> 
> This would woould create a multimode fm,dtsar,fusion and dmr repeater system.
> 
> I know some people dont like that. but on a remote site where energy and antenna deployement difficult and for place where installing multiple repeater is price prohibitive, this is a nice solution. No mode is left aside. but only one can be used at once.
> 
> So in order to make this work I need to know how the cop 2 and 3 command works.
> 
> I want to use the event manager to send those 2 command when one input from my URI is switching state. this will be connected to the MMDVM and it will prevent the tx or false rx when the DVMDM is taking control of the repeater.
> 
> WHat happen to any audio received by the network when in disable mode?  IS it still present at the URI? Does the link that are present stay connected or they disconnect?
> 
> I need this so that I can figure out if it is more effective to use a pair of small relay to cut the audio lines and ptt lines when the MMDVM is active or doing it by software.
> 
> thanks
> 
> Pierre
> VE2PF
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160830/497b9d82/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 30 Aug 2016 18:50:45 -0700
> From: H Hugh Flint <hflint at centurylink.net>
> To: app_rpt-users at ohnosec.org
> Subject: [App_rpt-users] Server IP target address
> Message-ID: <57be9b99-a7a2-68d3-5a3b-1eda383e4484 at centurylink.net>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> I am currently working on an medium scale network. Trying to get Allstar
> Link
> ported through it.  I need the VOIP server IP target address to perform
> the testing.
> 
> Thanks for your help,
> 
> H Hugh Flint, KF7LN
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 30 Aug 2016 22:06:48 -0700
> From: Bob Pyke <k6ecm1 at gmail.com>
> To: H Hugh Flint <hflint at centurylink.net>
> Cc: app_rpt-users at ohnosec.org
> Subject: Re: [App_rpt-users] Server IP target address
> Message-ID: <6FA9FAB7-7E31-4D92-9F43-509EF47778A3 at gmail.com>
> Content-Type: text/plain;       charset=us-ascii
> 
> I'm not sure what you mean by "the VOIP server." It seems to me the only VOIP servers are those built by folks to host their allstatlink nodes, which is based on app_rpt. Node linking is performed peer to peer, and not via a central server. The allstarlink registration server keeps track of the registered nodes' IP addresses and ports, which it sends out as a list to each node, which is used by the individual nodes to connect to each other. In DIAL, the node list is stored on each server in var/lib/asterisk/rpt_extnodes.
> 
> Thanks,
> Bob
> k6ecm
> 73
> 
> Sent from iPad
> 
> 
> > On Aug 30, 2016, at 6:50 PM, H Hugh Flint <hflint at centurylink.net> wrote:
> >
> > I am currently working on an medium scale network. Trying to get Allstar Link
> > ported through it.  I need the VOIP server IP target address to perform the testing.
> >
> > Thanks for your help,
> >
> > H Hugh Flint, KF7LN
> > _______________________________________________
> > App_rpt-users mailing list
> > App_rpt-users at ohnosec.org
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> >
> > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 31 Aug 2016 05:24:35 -0500
> From: Loren Tedford <lorentedford at gmail.com>
> To: app_rpt mailing list <app_rpt-users at ohnosec.org>
> Subject: [App_rpt-users] Problems surrounding Dial with service
>         asterisk stop and start along with restart
> Message-ID:
>         <CAK=eTyjUNYAXFFT+QJAgQZXrt3S5baxJ9xbNB5t0RpDiQ+cGYg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Greetings I have found an issue today on a pure dial install out in a Data
> Center environment where service asterisk stop and service asterisk start
> did not work.. Anyone else having these issues with Dial?
> 
> Here is some other commands i tried instead..
> root at hub:/etc/init.d# ./asterisk status
> ? asterisk.service - LSB: Asterisk PBX
>    Loaded: loaded (/etc/init.d/asterisk)
>    Active: failed (Result: exit-code) since Wed 2016-08-31 05:56:34 EDT;
> 22min ago
>   Process: 19146 ExecStop=/etc/init.d/asterisk stop (code=exited,
> status=0/SUCCESS)
>   Process: 19289 ExecStart=/etc/init.d/asterisk start (code=exited,
> status=1/FAILURE)
> 
> Aug 31 05:56:34 hub.kc9zhv.com asterisk[19289]: Asterisk is already
> running.  /etc/init.d/...w.
> Aug 31 05:56:34 hub.kc9zhv.com systemd[1]: asterisk.service: control
> process exited, code...s=1
> Aug 31 05:56:34 hub.kc9zhv.com systemd[1]: Failed to start LSB: Asterisk
> PBX.
> Aug 31 05:56:34 hub.kc9zhv.com systemd[1]: Unit asterisk.service entered
> failed state.
> Hint: Some lines were ellipsized, use -l to show in full.
> root at hub:/etc/init.d# ./asterisk forcestart
> Usage: /etc/init.d/asterisk {start|stop|restart|reload|force-reload}
> root at hub:/etc/init.d# ./asterisk force-reload
> [....] Reloading asterisk configuration (via systemctl):
> asterisk.serviceJob for asterisk.service failed. See 'systemctl status
> asterisk.service' and 'journalctl -xn' for details.
>  failed!
> root at hub:/etc/init.d# ./asterisk reload
> [....] Reloading asterisk configuration (via systemctl):
> asterisk.serviceJob for asterisk.service failed. See 'systemctl status
> asterisk.service' and 'journalctl -xn' for details.
>  failed!
> root at hub:/etc/init.d#
> 
> 
> As you see above i still received failures to stop and start asterisk using
> even this method
> 
> Any thoughts?
> 
> Anyone had any luck porting any of this to centos 7?
> 
> Considering making it part of a nethserver project i have been working on..
> 
> 
> Loren Tedford (KC9ZHV)
> Phone:
> Fax:
> Email: lorentedford at gmail.com
> Email: KC9ZHV at KC9ZHV.com
> http://www.lorentedford.com
> http://www.kc9zhv.com
> http://forum.kc9zhv.com
> http://hub.kc9zhv.com
> http://Ltcraft.net <http://ltcraft.net/>
> http://voipham.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160831/e46996a7/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 5
> Date: Wed, 31 Aug 2016 06:29:10 -0400
> From: Steve Zingman <szingman at msgstor.com>
> To: Loren Tedford <lorentedford at gmail.com>,     app_rpt mailing list
>         <app_rpt-users at ohnosec.org>
> Subject: Re: [App_rpt-users] Problems surrounding Dial with service
>         asterisk stop and start along with restart
> Message-ID: <db28a305-c7ef-83eb-ae47-c966a4ad7f27 at msgstor.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> 
> Loren,
> Yes it's a known issue. There is a problem with the init scripts. The
> next version uses systemd. If you want to convert to systemd now see
> <https://github.com/N4IRS/AllStar/tree/master/systemd>
> Careful reading of the README.md may yield  another solution.
> 
> 73, Steve N4IRS
> 
> On 08/31/2016 06:24 AM, Loren Tedford wrote:
> > Greetings I have found an issue today on a pure dial install out in a
> > Data Center environment where service asterisk stop and service
> > asterisk start did not work.. Anyone else having these issues with Dial?
> >
> > Here is some other commands i tried instead..
> > root at hub:/etc/init.d# ./asterisk status
> > ? asterisk.service - LSB: Asterisk PBX
> >    Loaded: loaded (/etc/init.d/asterisk)
> >    Active: failed (Result: exit-code) since Wed 2016-08-31 05:56:34
> > EDT; 22min ago
> >   Process: 19146 ExecStop=/etc/init.d/asterisk stop (code=exited,
> > status=0/SUCCESS)
> >   Process: 19289 ExecStart=/etc/init.d/asterisk start (code=exited,
> > status=1/FAILURE)
> >
> > Aug 31 05:56:34 hub.kc9zhv.com <http://hub.kc9zhv.com>
> > asterisk[19289]: Asterisk is already running.  /etc/init.d/...w.
> > Aug 31 05:56:34 hub.kc9zhv.com <http://hub.kc9zhv.com> systemd[1]:
> > asterisk.service: control process exited, code...s=1
> > Aug 31 05:56:34 hub.kc9zhv.com <http://hub.kc9zhv.com> systemd[1]:
> > Failed to start LSB: Asterisk PBX.
> > Aug 31 05:56:34 hub.kc9zhv.com <http://hub.kc9zhv.com> systemd[1]:
> > Unit asterisk.service entered failed state.
> > Hint: Some lines were ellipsized, use -l to show in full.
> > root at hub:/etc/init.d# ./asterisk forcestart
> > Usage: /etc/init.d/asterisk {start|stop|restart|reload|force-reload}
> > root at hub:/etc/init.d# ./asterisk force-reload
> > [....] Reloading asterisk configuration (via systemctl):
> > asterisk.serviceJob for asterisk.service failed. See 'systemctl status
> > asterisk.service' and 'journalctl -xn' for details.
> >  failed!
> > root at hub:/etc/init.d# ./asterisk reload
> > [....] Reloading asterisk configuration (via systemctl):
> > asterisk.serviceJob for asterisk.service failed. See 'systemctl status
> > asterisk.service' and 'journalctl -xn' for details.
> >  failed!
> > root at hub:/etc/init.d#
> >
> >
> > As you see above i still received failures to stop and start asterisk
> > using even this method
> >
> > Any thoughts?
> >
> > Anyone had any luck porting any of this to centos 7?
> >
> > Considering making it part of a nethserver project i have been working
> > on..
> >
> >
> > Loren Tedford (KC9ZHV)
> > Phone:
> > Fax:
> > Email: lorentedford at gmail.com <mailto:lorentedford at gmail.com>
> > Email: KC9ZHV at KC9ZHV.com <mailto:KC9ZHV at KC9ZHV.com>
> > http://www.lorentedford.com <http://www.lorentedford.com/>
> > http://www.kc9zhv.com <http://www.kc9zhv.com/>
> > http://forum.kc9zhv.com <http://forum.kc9zhv.com/>
> > http://hub.kc9zhv.com <http://hub.kc9zhv.com/>
> > http://Ltcraft.net<http://ltcraft.net/>
> > http://voipham.com
> >
> >
> > _______________________________________________
> > App_rpt-users mailing list
> > App_rpt-users at ohnosec.org
> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> >
> > To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> > You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
> 
> --
> "Anything is possible if you don't know what you are talking about."
> 1st Law of Logic
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://ohnosec.org/pipermail/app_rpt-users/attachments/20160831/a0df782e/attachment.html>
> 
> ------------------------------
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> 
> End of App_rpt-users Digest, Vol 90, Issue 25
> *********************************************
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20160901/c3208ca7/attachment.html>


More information about the App_rpt-users mailing list