NODE 29451
does not accept inbound Allstar connections
Router configured correctly to forward 4569 UDP to Allstar box internal IP
Router is working with Echolink and DSTAR and working Echolink (both ways)
through 29451
No port conflicts
This is my second Allstar node; other is on a tower at a remote sight, so
this problem is local only
Wonder if this may be one of the cases described here:
http://ohnosec.org/drupal/node/66
Befuddled
KB1RXA 29477, 28451
If the two nodes are on the same network you should put the address of the other in each nodes stanza of rpt.conf. Like so
node 29477:
[nodes]
29477 = radio(a)127.0.0.1/29477,NONE
29451 = radio@192.168.1.10:4568/29451,NONE
node 29451:
[nodes]
29451 = radio@127.0.0.1:4568/29451,NONE
29477 = radio(a)192.168.1.9/29477,NONE
If your nodes are on different public ip address you can code in the address as above but it shouldn’t be necessary as that’s the whole point of the Allstar directory services.
If on public IP’s check /var/lib/asterisk/rpt_extnodes on both systems for both nodes numbers with the correct IP and port.
--
Tim
:wq
On Dec 8, 2013, at 11:10 AM, Chris Day <kb1rxa(a)gmail.com> wrote:
> Nope will not work 29477 to 29451 ...strange
>
>
> On Sun, Dec 8, 2013 at 2:09 PM, Chris Day <kb1rxa(a)gmail.com> wrote:
> Hi Tim,
>
> I am dialing in from 29477 my remote node... I did see you connect and called.. hold on let me try again
>
> Chris
>
>
> On Sun, Dec 8, 2013 at 2:00 PM, Tim Sawyer <tim.sawyer(a)mac.com> wrote:
> I just connected to you fine. How are you testing it?
> --
> Tim
> :wq
>
> On Dec 8, 2013, at 10:43 AM, Chris Day <kb1rxa(a)gmail.com> wrote:
>
>> Correction to my signature earlier - nodes are 29477 and 29451
>> ---------------------------------------------------------------------------------------------------------------
>> NODE 29451
>>
>> does not accept inbound Allstar connections
>>
>> Router configured correctly to forward 4569 UDP to Allstar box internal IP
>>
>> Router is working with Echolink and DSTAR and working Echolink (both ways) through 29451
>>
>> No port conflicts
>>
>> This is my second Allstar node; other is on a tower at a remote sight, so this problem is local only
>>
>> Wonder if this may be one of the cases described here: http://ohnosec.org/drupal/node/66
>>
>> Befuddled
>>
>> KB1RXA 29477, 29451
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users(a)ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>
>
Correction to my signature earlier - nodes are 29477 and 29451
---------------------------------------------------------------------------------------------------------------
NODE 29451
does not accept inbound Allstar connections
Router configured correctly to forward 4569 UDP to Allstar box internal IP
Router is working with Echolink and DSTAR and working Echolink (both ways)
through 29451
No port conflicts
This is my second Allstar node; other is on a tower at a remote sight, so
this problem is local only
Wonder if this may be one of the cases described here:
http://ohnosec.org/drupal/node/66
Befuddled
KB1RXA 29477, 29451
I have a server defined at allstarlink. I also have three nodes assigned to that server. I am trying to figure out how to identify a non-radio node such as a hub with text rather than a frequency ID. This would be the field labeled <none> when no frequency is defined. I notice in the cloud and node list displays others have text in this field but the frequency field appears to only allows numerics.
On another note - the lat/long location of the server is defined but not the individual nodes. If one has a node located with a radio remotely from the server such as through an RTCM how can the actual location be identified?
73 Doug
WA3DSP
http://www.crompton.com/hamradio
Users:
I am using windows xp.
I performed the following sequence
Allstarlink.org -> Getting Started -> Setup Wizard -> Create New Server
->
Click here to select Longitude & Latitude from map
In the location field, entered street address -> Search
The map showed the correct area and street
DOUBLE CLICK on the map for my QTH.
The map expanded and 'undefined' was automatically entered into the Latitude
and Longitude fields.
I know my latitude and longitude using Google maps in windows.
The Allstar software is not working for automatic latitude & longitude.
Can not manually type in the latitude & longitude fields.
Attempted 'DOUBLE CLICK on the map on a location' a second, third, fourth
time
The Latitude & Longitude fields remained 'undefined' and the map expanded
each time.
What can I do next to obtain a server node number?
Thank You
Roger Berchtold
WB6HMW
562-691-3084
Greetings fellow Allstarlink members,
Since this subject kind of came up regarding one of the 4 allstarlink.org
registration servers being down I thought it would be a good time to remind
everyone that all of this technology we enjoy as Allstarlink node owners
does not just happen without cost. As John pointed out in his previous email
there are over 3000 Allstarlink nodes now registered.
This is certainly a milestone accomplishment and a testament to Jims
dedication to this project.
Once again I am reposting this email which is very similar to last year with
the hopes that we as the amateur community can step forward and support our
hobby, mainly the app_rpt and Allstarlink.org technology that we all enjoy
today.
As many of you that are new to app_rpt you might NOT know. The creator of
app_rpt and the Allstarlink network has never charged or asked for financial
support to keep the system going for the use in amateur radio.
He has never charged users money to be a part of app_rpt or for use of the
network, nor has he ever made any profit off of specific hardware sales for
the Allstarlink network. Through the years he has put in a great deal of
time and dedication along with his exceptional talents to make app_rpt and
the Allstarlink network the great VOIP technology that it has become today.
No other VOIP technology in the amateur radio community can even compare to
the technology, features and capability that is offered for free to anyone
wishing to setup a node.
Another understated fact is that there are monthly costs associated with
keeping things running smoothly for the system. These costs are for server
collocation, domain certifications and so on, amounting to roughly $200 per
month. Jim has been paying these monthly fees from donations, but mostly
out of his own pocket. Wouldn't it be nice if we could all pitch in and
help him to at the least cover these monthly costs for this coming year?
I am proposing that we all donate to this cause via PayPal at the following
URL.
https://allstarlink.org/
At the top of this webpage just slightly down there is a PayPal donate
button.
In the spirit and season of giving, lets all try and help out with the
financial side, so we can continue to use and enjoy this great technology
that we have all come to know and love!
I would also like to thank Jim, WB6NIL for all the many hours of work and
support that he and others have donated to this hobby so that the amateur
community at large can benefit and enjoy the use of his technology on a
daily basis for free.
73
Marshall - ke6pcv
Node 2065, 2066, 29147, 29148, 29149, 29947, 29948, 29949
My nodes 27365 and 27751 both on same server is showing on the status page
but not showing in the rpt_extnodes on other nodes im using standard port
4569.
we have been seeing this with several nodes in our group over past month or
so of coarse if we define in the rpt file we can connect but would be nice
if it was registering.
sometimes it may show up in a few hours or a day generally a reboot and its
gone again
Thanks for any help in advance
73
Randy KB3HJC
Doug,
As far as I can tell -5db has caused no problems and I think it is less
objectionable than the level I hear from the other two servers typically
connected to my machine.
I've implemented gaindown on only one server so far. I found -10db too low
and -5db was not quite as much as I would like. I have stuck with -5db on
that machine. The YL has a nice voice, but way too loud.
I have adjusted controls on CWID and delt with courtesy tones to make those
less bothersome when multiple nodes are connected. The tools seem to be
there. But I have been unable to teach the YL to be more polite and stop
screaming connection messages over active traffic on the repeaters. I was
thinking of a delay that would hold off the connection or disconnection AND
the associated voice messages until the radios are unkeyed. This is
probably a significant 'feature request'.
Until I cranked up a few Allstar servers a few months ago, I had not run a
LINUX or UNIX box here since 2005 and I've not done any programming in at
least 12 years. I am a little rusty to say the least. So at this point I
have to be carefull that I don't break anything I can't fix, hi hi. Still I
am very interested in the connect/disconnect message threads. I'll see
what I can do with your script. I appreciate your work on this.
All considered, I say this system works very well.
73,
Ken
W4NOC
----- Original Message -----
From: <app_rpt-users-request(a)ohnosec.org>
To: <app_rpt-users(a)ohnosec.org>
Sent: Thursday, December 05, 2013 4:13 PM
Subject: App_rpt-users Digest, Vol 58, Issue 18
> Send App_rpt-users mailing list submissions to
> app_rpt-users(a)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(a)ohnosec.org
>
> You can reach the person managing the list at
> app_rpt-users-owner(a)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. Re: Adjusting telemetry levels (Doug Crompton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 5 Dec 2013 16:13:20 -0500
> From: Doug Crompton <doug(a)crompton.com>
> To: Ken W4NOC <kenh(a)tsg-us.com>
> Cc: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org>
> Subject: Re: [App_rpt-users] Adjusting telemetry levels
> Message-ID: <BLU172-W3528BB0510C011C29E391BAD70(a)phx.gbl>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Ken,
>
> Thanks, yes, that is exactly what I mentioned in my message. The problem
> (or maybe not problem) is that this lowers the volume for these files even
> when they are not used for connect/disconnect messages.
>
> Has this been an issue?
> 73 Doug
> WA3DSP
> http://www.crompton.com/hamradio
>
>
>> From: kenh(a)tsg-us.com
>> To: app_rpt-users(a)ohnosec.org
>> Date: Thu, 5 Dec 2013 12:31:14 -0500
>> Subject: Re: [App_rpt-users] Adjusting telemetry levels
>>
>> Doug,
>> You may wish to try the 'gaindown' script. This will lower the volume of
>> the connect/disconnect messages. It works well.
>> http://www.allstarnode.com/viewtopic.php?f=6&t=26
>> 73,
>> Ken
>> W4NOC
>>
>>
>> ----- Original Message -----
>> From: <app_rpt-users-request(a)ohnosec.org>
>> To: <app_rpt-users(a)ohnosec.org>
>> Sent: Thursday, December 05, 2013 1:09 AM
>> Subject: App_rpt-users Digest, Vol 58, Issue 14
>>
>>
>> > Send App_rpt-users mailing list submissions to
>> > app_rpt-users(a)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(a)ohnosec.org
>> >
>> > You can reach the person managing the list at
>> > app_rpt-users-owner(a)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. Adjusting telemetry levels (Doug Crompton)
>> > 2. Re: Turn off dis/connect messages but not other telemetry?
>> > (corrected) (Doug Crompton)
>> > 3. Re: Turn off dis/connect messages but not other telemetry?
>> > (corrected) (Tim Sawyer)
>> >
>> >
>> > ----------------------------------------------------------------------
>> >
>> > Message: 1
>> > Date: Wed, 4 Dec 2013 23:40:32 -0500
>> > From: Doug Crompton <doug(a)crompton.com>
>> > To: "app_rpt-users(a)ohnosec.org" <app_rpt-users(a)ohnosec.org>
>> > Subject: [App_rpt-users] Adjusting telemetry levels
>> > Message-ID: <BLU172-W32F6A2BE101C94ACFF8941BAD70(a)phx.gbl>
>> > Content-Type: text/plain; charset="iso-8859-1"
>> >
>> > I have been trying to think of creative ways to adjust (down) the voice
>> > telemetry levels. The connected, disconnected, etc. messages are
>> > created
>> > from the Asterisk sounds directory. What I did for my voice ID and
>> > other
>> > short messages was create a batch file to combine the sound files and
>> > then
>> > run the combined file through sox to lower the volume.
>> >
>> > In other cases it becomes a little more difficult. I like on the hour
>> > time
>> > messages. The app_rpt time messages are created using the Asterisk say
>> > commands and code in app_rpt. It is not possible without modifying the
>> > app_rpt source to change the way it says it or more importantly the
>> > volume. I like the volume of messages to be somewhat lower than the
>> > normal
>> > QSO audio. So I created a Perl program to emulate the built-in time
>> > function and then on the fly I adjust the volume and play it.
>> >
>> > So far I have most everything under control but the connect/disconnect
>> > messages which are very annoying. I wish they could be made lower in
>> > volume also. This could be accomplished by running all the audio files
>> > they would call through sox to reduce the volume. Then when app_rpt
>> > called
>> > the files they would play at reduced volume. Kind of a crude way to do
>> > it
>> > but it would work. Of course whenever you called the modified files for
>> > other uses they would be at a reduced volume also.
>> >
>> > Interested in what others have done in this regard?
>> >
>> > I am attaching my Perl script to replace the app_rpt built-in time in
>> > case
>> > anyone else would like to use it. Instructions for its use are in
>> > comments
>> > in the script.
>> >
>> >
>> > 73 Doug
>> > WA3DSP
>> > http://www.crompton.com/hamradio
>> >
>> >
