[App_rpt-users] XIPAR Allstar Password where is it stored
Brian Burton
kb3ors at gmail.com
Fri Mar 7 04:44:59 UTC 2014
First of all, the secret in iax_rpt_custom.conf refers to the password used
by iax_rpt control op client to connect to your node... I recommend NOT
using your root login password or the password assigned to your node number
by allstarlink.org... this can be any password of your choosing..
Node number and password for registration of allstar on Xipar is stored in
iax_registration_custom.conf
ex:
register=nodenumber:password at register.allstarlink.org
Connection refused sounds like you do not have port forwarding set up
properly.. Check your router or firewall to be sure that you have the iax
port that you assigned on allstarlink.org forwarded to your server. 4569 is
usually the default used, however some ISP's do block that port. You may
have to switch to another port above or below.
On Thu, Mar 6, 2014 at 10:37 PM, <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. incoming allstar connections fail (Greg)
> 2. Re: incoming allstar connections fail (Doug Crompton)
> 3. Re: USB FOB options (Steve Wright)
> 4. Re: USB FOB options (Andrew Errington)
> 5. Re: USB FOB options (Kevin Custer)
> 6. XIPAR Allstar Password where is it stored? (Joe Bennett)
> 7. Re: incoming allstar connections fail (Doug Crompton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 06 Mar 2014 12:28:12 -0500
> From: Greg <kb1ncj at gmail.com>
> To: app_rpt-users at ohnosec.org
> Subject: [App_rpt-users] incoming allstar connections fail
> Message-ID: <5318B02C.5030100 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I can't figure out why.. I have port 4569 forwarded and echolink works
> fine with it's needed ports forwarded. I am trying to test using the web
> transceiver. A friend of mine can't connect to my node from his Allstar
> node either. Am I blocked from my own node using the web transceiver?
> Thanks for any help..
> Greg
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 6 Mar 2014 12:43:00 -0500
> From: Doug Crompton <doug at crompton.com>
> To: Greg <kb1ncj at gmail.com>
> Cc: "app_rpt-users at ohnosec.org" <app_rpt-users at ohnosec.org>
> Subject: Re: [App_rpt-users] incoming allstar connections fail
> Message-ID: <BLU172-W27E14E56FCFE2ECD212493BA880 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Do you have the web transceiver access enabled on your node access
> settings at allstarlink.org? Can others connect to you allstar node to
> node? What is your node number?
>
>
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
>
>
> > Date: Thu, 6 Mar 2014 12:28:12 -0500
> > From: kb1ncj at gmail.com
> > To: app_rpt-users at ohnosec.org
> > Subject: [App_rpt-users] incoming allstar connections fail
> >
> > I can't figure out why.. I have port 4569 forwarded and echolink works
> > fine with it's needed ports forwarded. I am trying to test using the web
> > transceiver. A friend of mine can't connect to my node from his Allstar
> > node either. Am I blocked from my own node using the web transceiver?
> > Thanks for any help..
> > Greg
> > _______________________________________________
> > 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://ohnosec.org/pipermail/app_rpt-users/attachments/20140306/73b44bae/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Fri, 7 Mar 2014 12:23:55 +1300
> From: Steve Wright <stevewrightnz at gmail.com>
> To: app_rpt-users at ohnosec.org
> Subject: Re: [App_rpt-users] USB FOB options
> Message-ID:
> <CABSSkBUXAntbcyEH9yvT542Whck02utT=
> VpY7L6X0Aj3mFE-oA at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Okies, so these USB FOBs have a blob of hard (epoxy?) goop on the chip so I
> can't get at the pins.
>
> BUT, the device has two LEDs and four switches that go direct to the chip.
>
> Why do we need any more I/O than that? Do I even need access to the pins?
> I should be able to take PTT off one of the LEDs, and put COR onto one of
> the switches.
>
> Why not? Soldering to pins is the hard way, and lots of devices are
> potted.
>
>
>
> Steve
>
> --
> Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
> +64 21 040 5067
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://ohnosec.org/pipermail/app_rpt-users/attachments/20140307/9fc67c91/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Fri, 7 Mar 2014 09:11:14 +0900
> From: Andrew Errington <erringtona at gmail.com>
> To: Steve Wright <stevewrightnz at gmail.com>
> Cc: app_rpt-users at ohnosec.org
> Subject: Re: [App_rpt-users] USB FOB options
> Message-ID:
> <
> CAGZkoWTgUSx5vi7kNeUzj-PFfU1hvnsGaVHbuTAV0+-A4+h6tQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> The modification for packaged chips usually puts COR onto the Volume
> Down pin, so that should be the same for the epoxy-blobbed version.
> However, PTT is wired to a GPIO pin, which is not accessible on the
> epoxy-blobbed version (so sad that it's not bonded out to a test point
> on the PCB, but I digress). Anyway, I think it would be possible to
> tie PTT to the Mute LED output and use that, since if the mic. is
> muted during Tx then it's not a problem. The software would have to
> be modified to set and clear the Mute state based on the desired PTT
> state, instead of setting and clearing the GPIO.
>
> I did some work with Thomas Sailer's soundmodem software to support
> CM108 GPIO (which I also copied to hamlib), but I never looked into
> how to set or clear the Mute state. If the software could be modified
> in this way it might pave the way to using blobbed chips, which are
> much more common than packaged parts.
>
> 73,
>
> Andrew
> ZL3AME
>
> On 07/03/2014, Steve Wright <stevewrightnz at gmail.com> wrote:
> > Okies, so these USB FOBs have a blob of hard (epoxy?) goop on the chip
> so I
> > can't get at the pins.
> >
> > BUT, the device has two LEDs and four switches that go direct to the
> chip.
> >
> > Why do we need any more I/O than that? Do I even need access to the
> pins?
> > I should be able to take PTT off one of the LEDs, and put COR onto one
> of
> > the switches.
> >
> > Why not? Soldering to pins is the hard way, and lots of devices are
> > potted.
> >
> >
> >
> > Steve
> >
> > --
> > Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers
> > +64 21 040 5067
> >
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 06 Mar 2014 19:12:56 -0500
> From: Kevin Custer <kuggie at kuggie.com>
> To: Steve Wright <stevewrightnz at gmail.com>,
> "App_rpt-users at ohnosec.org" <App_rpt-users at ohnosec.org>
> Subject: Re: [App_rpt-users] USB FOB options
> Message-ID: <53190F08.9010509 at kuggie.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 3/6/2014 6:23 PM, Steve Wright wrote:
> > Okies, so these USB FOBs have a blob of hard (epoxy?) goop on the chip
> > so I can't get at the pins.
> >
> > BUT, the device has two LEDs and four switches that go direct to the
> chip.
> >
> > Why do we need any more I/O than that? Do I even need access to the
> > pins? I should be able to take PTT off one of the LEDs, and put COR
> > onto one of the switches.
> >
> > Why not? Soldering to pins is the hard way, and lots of devices are
> > potted.
>
>
> Pin 13 of the CM108 - CM119 is GPIO3, a pin that likely doesn't have a
> connection to the outside world in a standard BLOB FOB. Same goes with
> Pin 12.
>
> Kevin
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 6 Mar 2014 21:23:32 -0600
> From: Joe Bennett <aprs at ka3nam.com>
> To: app_rpt-users at ohnosec.org
> Subject: [App_rpt-users] XIPAR Allstar Password where is it stored?
> Message-ID:
> <CAD+1-4_XdDxVr52vF9dM33DjCR9hsppwt8Uwkakn=
> 2C_Wgtpkg at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Keep getting connection refused for our node... Looked in
> iax_rpt_custom.conf and set 'secret' to our password... Then did an
> amportal restart... What else needs to be done?
>
>
>
>
> -Joe
> KA3NAM
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 6 Mar 2014 22:37:40 -0500
> From: Doug Crompton <doug at crompton.com>
> To: Greg <kb1ncj at gmail.com>
> Cc: "app_rpt-users at ohnosec.org" <app_rpt-users at ohnosec.org>
> Subject: Re: [App_rpt-users] incoming allstar connections fail
> Message-ID: <BLU172-W4F66A660D7D1549B2EF4BBA8B0 at phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I tried connecting to you on web transceiver here and it connects but I
> cannot key. I can disconnect and connect but thats about it.
>
> I am not a big fan of web transceiver. I use iaxrpt. If you have a server
> that is the way to go. You can set it up in windows and access your nodes
> from anywhere. If you need help setting it up let me know.
>
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
>
>
> Date: Thu, 6 Mar 2014 21:25:12 -0500
> From: kb1ncj at gmail.com
> To: doug at crompton.com
> Subject: Re: [App_rpt-users] incoming allstar connections fail
>
>
>
>
>
>
> Oh and telephone portal connects are
> working.. so it is puzzling.
>
>
>
> On 03/06/2014 12:43 PM, Doug Crompton wrote:
>
>
>
>
>
> Do you have the web
> transceiver access enabled on your node access settings at
> allstarlink.org? Can others connect to you allstar node to
> node? What is your node number?
>
>
>
>
>
>
> 73 Doug
>
> WA3DSP
>
> http://www.crompton.com/hamradio
>
>
>
>
>
> > Date: Thu, 6 Mar 2014 12:28:12 -0500
>
> > From: kb1ncj at gmail.com
>
> > To: app_rpt-users at ohnosec.org
>
> > Subject: [App_rpt-users] incoming allstar connections
> fail
>
> >
>
> > I can't figure out why.. I have port 4569 forwarded and
> echolink works
>
> > fine with it's needed ports forwarded. I am trying to
> test using the web
>
> > transceiver. A friend of mine can't connect to my node
> from his Allstar
>
> > node either. Am I blocked from my own node using the web
> transceiver?
>
> > Thanks for any help..
>
> > Greg
>
> > _______________________________________________
>
> > 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://ohnosec.org/pipermail/app_rpt-users/attachments/20140306/ae5749e0/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 61, Issue 17
> *********************************************
>
--
Brian
KB3ORS
Trustee W3WAN
WAN-RS Tech Support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140306/db495aa0/attachment.html>
More information about the App_rpt-users
mailing list