[arm-allstar] arm-allstar Digest, Vol 40, Issue 28
ku6v
ku6v at pacbell.net
Tue Sep 19 22:15:02 EST 2017
Thanks Doug
Do I do this for both nodes?
73
Don
KU6V
-----Original Message-----
From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
arm-allstar-request at hamvoip.org
Sent: Tuesday, September 19, 2017 3:49 PM
To: arm-allstar at hamvoip.org
Subject: arm-allstar Digest, Vol 40, Issue 28
Send arm-allstar mailing list submissions to
arm-allstar at hamvoip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
or, via email, send a message with subject or body 'help' to
arm-allstar-request at hamvoip.org
You can reach the person managing the list at
arm-allstar-owner at hamvoip.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of arm-allstar digest..."
Today's Topics:
1. Re: arm-allstar Digest, Vol 40, Issue 27 (ku6v)
2. Re: arm-allstar Digest, Vol 40, Issue 27 (Doug Crompton)
3. Re: arm-allstar Digest, Vol 40, Issue 27 (ku6v)
4. Re: arm-allstar Digest, Vol 40, Issue 27 (Doug Crompton)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 Sep 2017 11:08:52 -0700
From: ku6v <ku6v at pacbell.net>
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 40, Issue 27
Message-ID: <o50p6whl9s4x5n0cvmig3lvk.1505844532362 at email.android.com>
Content-Type: text/plain; charset=utf-8
The immediate issue is 46532 won't connect to or be connected to using
Zoiper or command line. I don't have radio connected yet. I forwarded 4570
and 4569.Do I need changes in extensions.conf?
Thanks?Don?
-------- Original message --------
From: arm-allstar-request at hamvoip.org
Date: 9/19/17 10:00 AM (GMT-08:00)
To: arm-allstar at hamvoip.org
Subject: arm-allstar Digest, Vol 40, Issue 27
Send arm-allstar mailing list submissions to
arm-allstar at hamvoip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
or, via email, send a message with subject or body 'help' to
arm-allstar-request at hamvoip.org
You can reach the person managing the list at
arm-allstar-owner at hamvoip.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of arm-allstar digest..."
Today's Topics:
?? 1. second node installed on same ip address (ku6v) ?? 2. Re: second node
installed on same ip address (Doug Crompton)
----------------------------------------------------------------------
Message: 1
Date: Mon, 18 Sep 2017 13:29:30 -0700
From: "ku6v" <ku6v at pacbell.net>
To: <arm-allstar at hamvoip.org>
Subject: [arm-allstar] second node installed on same ip address
Message-ID: <000c01d330bc$d643aa60$82caff20$@pacbell.net>
Content-Type: text/plain; charset="us-ascii"
I installed a second node on the same ip address with a different bind port.
I cannot get the second node to make or accept calls. It does show up as
being online and in green.
What did I do this time?? I did look at my working node 41971
extensions.conf for differences but did not see anything obvious. The second
node is 46532.
73
Don
KU6V
------------------------------
Message: 2
Date: Mon, 18 Sep 2017 18:26:37 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] second node installed on same ip address
Message-ID:
<CAMp6vsu+aGWxU3yM=HaZRqAo1=TtVsWkMrtMW9VGfpnzopF=_g at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Don,
? It looks like you did change the port at allstarlink.org for the second
node. Here is how they show up here -
41971=radio at 199.103.53.101:4569/41971,199.103.53.101
46532=radio at 199.103.53.101:4570/46532,199.103.53.101
In order to diagnose we need more info as it could be so many things. dtmf
not working? nodes not downloading? etc.
What does it do when you try to connect out to a valid node? If you go into
the client from the main menu you can see your dtmf being sent and the
response. Do you have a /tmp/rpt_extnodes file?
Remember unless your router has hairpin loopback you cannot connect the
nodes together without putting specific routing in rpt.conf to each other.
In that case see this howto at the hamvoip.org web page -
https://www.hamvoip.org/multi-server%20howto.pdf
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Mon, Sep 18, 2017 at 4:29 PM, "ku6v via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> I installed a second node on the same ip address with a different bind
> port.
> I cannot get the second node to make or accept calls. It does show up
> as being online and in green.
>
> What did I do this time?? I did look at my working node 41971
> extensions.conf for differences but did not see anything obvious. The
> second node is 46532.
>
>
>
> 73
>
> Don
>
> KU6V
>
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>
------------------------------
Subject: Digest Footer
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
------------------------------
End of arm-allstar Digest, Vol 40, Issue 27
*******************************************
------------------------------
Message: 2
Date: Tue, 19 Sep 2017 14:57:18 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 40, Issue 27
Message-ID:
<CAMp6vsvL9n4aFsysU36y7zn0rn-oX=5b+fuON1CLv7+hYLFRVQ at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Here is a rundown of what you need to do to add a second node.
The image starts out with two nodes 1998 and 1999. When you do setup node
1998 becomes your first node. If at a later date you want to add a second
node here is the procedure -
Use nano to edit and add a registration line in iax,conf for your second
node using the existing line as an example. Of course using yout new node
number and 6 digit password.
Use nano to edit rpt.conf and change all occurrences of 1999 to your new
second node number
In nano if you type CONTROL \ it puts you into search and replace mode.
Enter 1999 and then the new node number then select change ALL.
Edit the new node stanza in rpt.conf to change the rxchannel= to a
simpleusb and a real radio if you are using one. Otherwise leave it as
pseudo.
If you did change to simpleusb you need to add a second stanza in
simpleusb.conf that conforms to your new radio. In most cases just copying
the first stanza if a second one does not exist, renaming it (usb2 or
whatever), and configuring to your second radio. The rxchannel name in
rpt.conf if using simpleusb must match this new stanza name.
Use nano to edit extensions.conf and change all occurrences of 1999 to the
new second node number. Use the global method as outlined above.
Restart Asterisk or reboot and the second node should be active.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
? ?
On Tue, Sep 19, 2017 at 2:08 PM, "ku6v via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
>
>
> The immediate issue is 46532 won't connect to or be connected to using
> Zoiper or command line. I don't have radio connected yet. I forwarded
> 4570 and 4569.Do I need changes in extensions.conf?
>
>
> Thanks Don
>
> -------- Original message --------
> From: arm-allstar-request at hamvoip.org
> Date: 9/19/17 10:00 AM (GMT-08:00)
> To: arm-allstar at hamvoip.org
> Subject: arm-allstar Digest, Vol 40, Issue 27
>
> Send arm-allstar mailing list submissions to
> arm-allstar at hamvoip.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> or, via email, send a message with subject or body 'help' to
> arm-allstar-request at hamvoip.org
>
> You can reach the person managing the list at
> arm-allstar-owner at hamvoip.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of arm-allstar digest..."
>
>
> Today's Topics:
>
> 1. second node installed on same ip address (ku6v)
> 2. Re: second node installed on same ip address (Doug Crompton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 18 Sep 2017 13:29:30 -0700
> From: "ku6v" <ku6v at pacbell.net>
> To: <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] second node installed on same ip address
> Message-ID: <000c01d330bc$d643aa60$82caff20$@pacbell.net>
> Content-Type: text/plain; charset="us-ascii"
>
> I installed a second node on the same ip address with a different bind
> port.
> I cannot get the second node to make or accept calls. It does show up
> as being online and in green.
>
> What did I do this time? I did look at my working node 41971
> extensions.conf for differences but did not see anything obvious. The
> second node is 46532.
>
>
>
> 73
>
> Don
>
> KU6V
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 18 Sep 2017 18:26:37 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] second node installed on same ip address
> Message-ID:
> <CAMp6vsu+aGWxU3yM=HaZRqAo1=TtVsWkMrtMW9VGfpnzopF=_g at mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Don,
>
> It looks like you did change the port at allstarlink.org for the
> second node. Here is how they show up here -
>
> 41971=radio at 199.103.53.101:4569/41971,199.103.53.101
>
> 46532=radio at 199.103.53.101:4570/46532,199.103.53.101
>
> In order to diagnose we need more info as it could be so many things.
> dtmf not working? nodes not downloading? etc.
>
> What does it do when you try to connect out to a valid node? If you go
> into the client from the main menu you can see your dtmf being sent
> and the response. Do you have a /tmp/rpt_extnodes file?
>
> Remember unless your router has hairpin loopback you cannot connect
> the nodes together without putting specific routing in rpt.conf to each
other.
> In that case see this howto at the hamvoip.org web page -
>
> https://www.hamvoip.org/multi-server%20howto.pdf
>
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
>
>
> On Mon, Sep 18, 2017 at 4:29 PM, "ku6v via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I installed a second node on the same ip address with a different
> > bind port.
> > I cannot get the second node to make or accept calls. It does show
> > up as being online and in green.
> >
> > What did I do this time? I did look at my working node 41971
> > extensions.conf for differences but did not see anything obvious.
> > The second node is 46532.
> >
> >
> >
> > 73
> >
> > Don
> >
> > KU6V
> >
> >
> >
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> >
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
> ------------------------------
>
> End of arm-allstar Digest, Vol 40, Issue 27
> *******************************************
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
------------------------------
Message: 3
Date: Tue, 19 Sep 2017 12:25:07 -0700
From: ku6v <ku6v at pacbell.net>
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 40, Issue 27
Message-ID: <ct9r20w4mpxk1mhd1ox5m8yc.1505849107719 at email.android.com>
Content-Type: text/plain; charset=utf-8
Doug thanks for the.I didn't specify the 41971 RPi2 V1.0.46532 is V1.5
Pi3.Is that problematic?
73Thanks?Don?
-------- Original message --------
From: arm-allstar-request at hamvoip.org
Date: 9/19/17 10:00 AM (GMT-08:00)
To: arm-allstar at hamvoip.org
Subject: arm-allstar Digest, Vol 40, Issue 27
Send arm-allstar mailing list submissions to
arm-allstar at hamvoip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
or, via email, send a message with subject or body 'help' to
arm-allstar-request at hamvoip.org
You can reach the person managing the list at
arm-allstar-owner at hamvoip.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of arm-allstar digest..."
Today's Topics:
?? 1. second node installed on same ip address (ku6v) ?? 2. Re: second node
installed on same ip address (Doug Crompton)
----------------------------------------------------------------------
Message: 1
Date: Mon, 18 Sep 2017 13:29:30 -0700
From: "ku6v" <ku6v at pacbell.net>
To: <arm-allstar at hamvoip.org>
Subject: [arm-allstar] second node installed on same ip address
Message-ID: <000c01d330bc$d643aa60$82caff20$@pacbell.net>
Content-Type: text/plain; charset="us-ascii"
I installed a second node on the same ip address with a different bind port.
I cannot get the second node to make or accept calls. It does show up as
being online and in green.
What did I do this time?? I did look at my working node 41971
extensions.conf for differences but did not see anything obvious. The second
node is 46532.
73
Don
KU6V
------------------------------
Message: 2
Date: Mon, 18 Sep 2017 18:26:37 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] second node installed on same ip address
Message-ID:
<CAMp6vsu+aGWxU3yM=HaZRqAo1=TtVsWkMrtMW9VGfpnzopF=_g at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Don,
? It looks like you did change the port at allstarlink.org for the second
node. Here is how they show up here -
41971=radio at 199.103.53.101:4569/41971,199.103.53.101
46532=radio at 199.103.53.101:4570/46532,199.103.53.101
In order to diagnose we need more info as it could be so many things. dtmf
not working? nodes not downloading? etc.
What does it do when you try to connect out to a valid node? If you go into
the client from the main menu you can see your dtmf being sent and the
response. Do you have a /tmp/rpt_extnodes file?
Remember unless your router has hairpin loopback you cannot connect the
nodes together without putting specific routing in rpt.conf to each other.
In that case see this howto at the hamvoip.org web page -
https://www.hamvoip.org/multi-server%20howto.pdf
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Mon, Sep 18, 2017 at 4:29 PM, "ku6v via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> I installed a second node on the same ip address with a different bind
> port.
> I cannot get the second node to make or accept calls. It does show up
> as being online and in green.
>
> What did I do this time?? I did look at my working node 41971
> extensions.conf for differences but did not see anything obvious. The
> second node is 46532.
>
>
>
> 73
>
> Don
>
> KU6V
>
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>
------------------------------
Subject: Digest Footer
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
------------------------------
End of arm-allstar Digest, Vol 40, Issue 27
*******************************************
------------------------------
Message: 4
Date: Tue, 19 Sep 2017 18:48:43 -0400
From: Doug Crompton <wa3dsp at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] arm-allstar Digest, Vol 40, Issue 27
Message-ID:
<CAMp6vsteCQ+0RDaPV-DSMD=y3YKOg6uX-g0UoEkXsVjXdOS_og at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
I am not sure what you are saying. I want to help but please understand that
we cannot read your mind in emails. Be specific in what you say and give
good details. Exactly what is not working, what you have checked and the
results etc. When we ask for you to give back information to aid in
troubleshooting it is important so we can diagnose the problem. Just saying
something does not work is not a good answer.
I thought I sent you an email asking for additional information about
exactly what it was or was not doing.
If you have connection problems is it just not doing (saying) anything when
you try to connect somewhere? Is it giving a failure message? If it does
nothing when you try to connect it usually indicates either a lack of
Internet connection or no /tmp/rpt_extnodes file. If it gives an error it
could mean a lot of things from a failure of your node to connect to a
failure of the destination node to respond. This often happens when a node
first come online as your node information has not propagated to the distant
node yet.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Tue, Sep 19, 2017 at 3:25 PM, "ku6v via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
>
>
> Doug thanks for the.I didn't specify the 41971 RPi2 V1.0.46532 is V1.5
> Pi3.Is that problematic?
>
> 73Thanks Don
>
> -------- Original message --------
> From: arm-allstar-request at hamvoip.org
> Date: 9/19/17 10:00 AM (GMT-08:00)
> To: arm-allstar at hamvoip.org
> Subject: arm-allstar Digest, Vol 40, Issue 27
>
> Send arm-allstar mailing list submissions to
> arm-allstar at hamvoip.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> or, via email, send a message with subject or body 'help' to
> arm-allstar-request at hamvoip.org
>
> You can reach the person managing the list at
> arm-allstar-owner at hamvoip.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of arm-allstar digest..."
>
>
> Today's Topics:
>
> 1. second node installed on same ip address (ku6v)
> 2. Re: second node installed on same ip address (Doug Crompton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 18 Sep 2017 13:29:30 -0700
> From: "ku6v" <ku6v at pacbell.net>
> To: <arm-allstar at hamvoip.org>
> Subject: [arm-allstar] second node installed on same ip address
> Message-ID: <000c01d330bc$d643aa60$82caff20$@pacbell.net>
> Content-Type: text/plain; charset="us-ascii"
>
> I installed a second node on the same ip address with a different bind
> port.
> I cannot get the second node to make or accept calls. It does show up
> as being online and in green.
>
> What did I do this time? I did look at my working node 41971
> extensions.conf for differences but did not see anything obvious. The
> second node is 46532.
>
>
>
> 73
>
> Don
>
> KU6V
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 18 Sep 2017 18:26:37 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] second node installed on same ip address
> Message-ID:
> <CAMp6vsu+aGWxU3yM=HaZRqAo1=TtVsWkMrtMW9VGfpnzopF=_g at mail.
> gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Don,
>
> It looks like you did change the port at allstarlink.org for the
> second node. Here is how they show up here -
>
> 41971=radio at 199.103.53.101:4569/41971,199.103.53.101
>
> 46532=radio at 199.103.53.101:4570/46532,199.103.53.101
>
> In order to diagnose we need more info as it could be so many things.
> dtmf not working? nodes not downloading? etc.
>
> What does it do when you try to connect out to a valid node? If you go
> into the client from the main menu you can see your dtmf being sent
> and the response. Do you have a /tmp/rpt_extnodes file?
>
> Remember unless your router has hairpin loopback you cannot connect
> the nodes together without putting specific routing in rpt.conf to each
other.
> In that case see this howto at the hamvoip.org web page -
>
> https://www.hamvoip.org/multi-server%20howto.pdf
>
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
>
>
> On Mon, Sep 18, 2017 at 4:29 PM, "ku6v via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I installed a second node on the same ip address with a different
> > bind port.
> > I cannot get the second node to make or accept calls. It does show
> > up as being online and in green.
> >
> > What did I do this time? I did look at my working node 41971
> > extensions.conf for differences but did not see anything obvious.
> > The second node is 46532.
> >
> >
> >
> > 73
> >
> > Don
> >
> > KU6V
> >
> >
> >
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> >
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
>
> ------------------------------
>
> End of arm-allstar Digest, Vol 40, Issue 27
> *******************************************
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
------------------------------
Subject: Digest Footer
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
------------------------------
End of arm-allstar Digest, Vol 40, Issue 28
*******************************************
More information about the arm-allstar
mailing list