So in dmrlink.cfg I have my RPI2 as a master. I've pointed my repeater at my RPI2. That all seems fine, where I'm confused is how does the software know how or where to echo the audio back to? N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658 On Dec 24, 2015 6:28 PM, "Steve Zingman" <szingman@msgstor.com> wrote:
It's in dmrlink.cfg
Sent via smoke signal (AT&T 4G LTE)
-------- Original message -------- From: Robert Newberry <N1XBM@amsat.org> Date: 12/24/2015 3:14 PM (GMT-05:00) To: Digital linking using Asterisk and app_rpt < allstar-digital@lists.keekles.org> Subject: [Allstar Digital] Playback
I edited /opt/dmrlink/playback/dmrlink.cfg I did the same for playback_config.py in the same directory
I ran dmrlink.py and didn't get any errors. I the hit ctrl c and then ran playback.py I didn't see any errors. Although I'm not getting any echo.
Is there any things I should be looking at to troubleshoot?
Also I want to see the log live on the console, but I can't remember how.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Setup playback as a peer. Point it at the same master as your repeater talk on the TG and TS you defined in the playback config file On 12/25/2015 01:11 PM, Robert Newberry wrote:
So in dmrlink.cfg I have my RPI2 as a master. I've pointed my repeater at my RPI2. That all seems fine, where I'm confused is how does the software know how or where to echo the audio back to?
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 24, 2015 6:28 PM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
It's in dmrlink.cfg
Sent via smoke signal (AT&T 4G LTE)
-------- Original message -------- From: Robert Newberry <N1XBM@amsat.org <mailto:N1XBM@amsat.org>> Date: 12/24/2015 3:14 PM (GMT-05:00) To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org <mailto:allstar-digital@lists.keekles.org>> Subject: [Allstar Digital] Playback
I edited /opt/dmrlink/playback/dmrlink.cfg I did the same for playback_config.py in the same directory
I ran dmrlink.py and didn't get any errors. I the hit ctrl c and then ran playback.py I didn't see any errors. Although I'm not getting any echo.
Is there any things I should be looking at to troubleshoot?
Also I want to see the log live on the console, but I can't remember how.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
Sorry I hit send a little to early. I would assume there has to be a place somewhere that would indicate where to send that back to. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658 On Dec 25, 2015 1:11 PM, "Robert Newberry" <N1XBM@amsat.org> wrote:
So in dmrlink.cfg I have my RPI2 as a master. I've pointed my repeater at my RPI2. That all seems fine, where I'm confused is how does the software know how or where to echo the audio back to?
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 24, 2015 6:28 PM, "Steve Zingman" <szingman@msgstor.com> wrote:
It's in dmrlink.cfg
Sent via smoke signal (AT&T 4G LTE)
-------- Original message -------- From: Robert Newberry <N1XBM@amsat.org> Date: 12/24/2015 3:14 PM (GMT-05:00) To: Digital linking using Asterisk and app_rpt < allstar-digital@lists.keekles.org> Subject: [Allstar Digital] Playback
I edited /opt/dmrlink/playback/dmrlink.cfg I did the same for playback_config.py in the same directory
I ran dmrlink.py and didn't get any errors. I the hit ctrl c and then ran playback.py I didn't see any errors. Although I'm not getting any echo.
Is there any things I should be looking at to troubleshoot?
Also I want to see the log live on the console, but I can't remember how.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
It sends to the same TS and TG defined in payback config On 12/25/2015 01:13 PM, Robert Newberry wrote:
Sorry I hit send a little to early.
I would assume there has to be a place somewhere that would indicate where to send that back to.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 25, 2015 1:11 PM, "Robert Newberry" <N1XBM@amsat.org <mailto:N1XBM@amsat.org>> wrote:
So in dmrlink.cfg I have my RPI2 as a master. I've pointed my repeater at my RPI2. That all seems fine, where I'm confused is how does the software know how or where to echo the audio back to?
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 24, 2015 6:28 PM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
It's in dmrlink.cfg
Sent via smoke signal (AT&T 4G LTE)
-------- Original message -------- From: Robert Newberry <N1XBM@amsat.org <mailto:N1XBM@amsat.org>> Date: 12/24/2015 3:14 PM (GMT-05:00) To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org <mailto:allstar-digital@lists.keekles.org>> Subject: [Allstar Digital] Playback
I edited /opt/dmrlink/playback/dmrlink.cfg I did the same for playback_config.py in the same directory
I ran dmrlink.py and didn't get any errors. I the hit ctrl c and then ran playback.py I didn't see any errors. Although I'm not getting any echo.
Is there any things I should be looking at to troubleshoot?
Also I want to see the log live on the console, but I can't remember how.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
So long e-mail here with questions. I should be working in /opt/dmrlink/playback The files I need to be concerned with are dmrlink.cfg and playback_config.py Now to get echo going do I just run playback.py? So I setup up playback_config.py with TG 9998 time slot 0...well one, but I think you know what I mean. I programed my radio the same way. I also programmed the repeater, That end of it seems to be OK. Now dmrlink.cfg is where I am confused. So I've pointed my repeater to 192.168.0.203 port 50002 which is the IP of my RPI2. I've confirmed my auth key is correct. Got any suggestions where I am hosed? [PLAYBACK_PEER] ENABLED: True RADIO_ID: 12345 IP: 0.0.0.0 PORT: 50002 ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER: True IPSC_MODE: DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL: False RCM: True CON_APP: True XNL_CALL: False XNL_MASTER: False DATA_CALL: True VOICE_CALL: True MASTER_PEER: False AUTH_ENABLED: True AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 MASTER_PORT: 50001 [N1XBM_MASTER] ENABLED: True RADIO_ID: 54321 IP: 0.0.0.0 PORT: 50001 ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER: True IPSC_MODE: DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL: False RCM: True CON_APP: True XNL_CALL: False XNL_MASTER: False DATA_CALL: True VOICE_CALL: True MASTER_PEER: True AUTH_ENABLED: True AUTH_KEY: A1B2C3 # Below not used for a Master # MASTER_IP: 1.2.3.4 # MASTER_PORT: 50000 On Fri, Dec 25, 2015 at 1:14 PM, Steve Zingman <szingman@msgstor.com> wrote:
It sends to the same TS and TG defined in payback config
On 12/25/2015 01:13 PM, Robert Newberry wrote:
Sorry I hit send a little to early.
I would assume there has to be a place somewhere that would indicate where to send that back to.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 25, 2015 1:11 PM, "Robert Newberry" <N1XBM@amsat.org> wrote:
So in dmrlink.cfg I have my RPI2 as a master. I've pointed my repeater at my RPI2. That all seems fine, where I'm confused is how does the software know how or where to echo the audio back to?
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 24, 2015 6:28 PM, "Steve Zingman" <szingman@msgstor.com> wrote:
It's in dmrlink.cfg
Sent via smoke signal (AT&T 4G LTE)
-------- Original message -------- From: Robert Newberry <N1XBM@amsat.org> Date: 12/24/2015 3:14 PM (GMT-05:00) To: Digital linking using Asterisk and app_rpt < <allstar-digital@lists.keekles.org>allstar-digital@lists.keekles.org> Subject: [Allstar Digital] Playback
I edited /opt/dmrlink/playback/dmrlink.cfg I did the same for playback_config.py in the same directory
I ran dmrlink.py and didn't get any errors. I the hit ctrl c and then ran playback.py I didn't see any errors. Although I'm not getting any echo.
Is there any things I should be looking at to troubleshoot?
Also I want to see the log live on the console, but I can't remember how.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
The dmrlink.cfg in playback is only for playback. Disable or remove N1XBM_MASTER Make sure it connects to the master as a peer On 12/26/2015 04:33 PM, Robert Newberry wrote:
So long e-mail here with questions.
I should be working in /opt/dmrlink/playback The files I need to be concerned with are dmrlink.cfg and playback_config.py Now to get echo going do I just run playback.py?
So I setup up playback_config.py with TG 9998 time slot 0...well one, but I think you know what I mean. I programed my radio the same way. I also programmed the repeater, That end of it seems to be OK.
Now dmrlink.cfg is where I am confused. So I've pointed my repeater to 192.168.0.203 port 50002 which is the IP of my RPI2. I've confirmed my auth key is correct. Got any suggestions where I am hosed?
[PLAYBACK_PEER] ENABLED: True RADIO_ID: 12345 IP: 0.0.0.0 PORT: 50002 ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER: True IPSC_MODE: DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL: False RCM: True CON_APP: True XNL_CALL: False XNL_MASTER: False DATA_CALL: True VOICE_CALL: True MASTER_PEER: False AUTH_ENABLED: True AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 MASTER_PORT: 50001
[N1XBM_MASTER] ENABLED: True RADIO_ID: 54321 IP: 0.0.0.0 PORT: 50001 ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER: True IPSC_MODE: DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL: False RCM: True CON_APP: True XNL_CALL: False XNL_MASTER: False DATA_CALL: True VOICE_CALL: True MASTER_PEER: True AUTH_ENABLED: True AUTH_KEY: A1B2C3 # Below not used for a Master # MASTER_IP: 1.2.3.4 # MASTER_PORT: 50000
On Fri, Dec 25, 2015 at 1:14 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
It sends to the same TS and TG defined in payback config
On 12/25/2015 01:13 PM, Robert Newberry wrote:
Sorry I hit send a little to early.
I would assume there has to be a place somewhere that would indicate where to send that back to.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 25, 2015 1:11 PM, "Robert Newberry" <N1XBM@amsat.org <mailto:N1XBM@amsat.org>> wrote:
So in dmrlink.cfg I have my RPI2 as a master. I've pointed my repeater at my RPI2. That all seems fine, where I'm confused is how does the software know how or where to echo the audio back to?
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 24, 2015 6:28 PM, "Steve Zingman" <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
It's in dmrlink.cfg
Sent via smoke signal (AT&T 4G LTE)
-------- Original message -------- From: Robert Newberry <N1XBM@amsat.org <mailto:N1XBM@amsat.org>> Date: 12/24/2015 3:14 PM (GMT-05:00) To: Digital linking using Asterisk and app_rpt <allstar-digital@lists.keekles.org <mailto:allstar-digital@lists.keekles.org>> Subject: [Allstar Digital] Playback
I edited /opt/dmrlink/playback/dmrlink.cfg I did the same for playback_config.py in the same directory
I ran dmrlink.py and didn't get any errors. I the hit ctrl c and then ran playback.py I didn't see any errors. Although I'm not getting any echo.
Is there any things I should be looking at to troubleshoot?
Also I want to see the log live on the console, but I can't remember how.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
I've confirmed my repeater is a peer and I've pointed it to my RPI2. [PLAYBACK_PEER] ENABLED: True RADIO_ID: 12345 <---Is it OK to leave this as it is? IP: 0.0.0.0 <----- Should I change this to the IP of the repeater? PORT: 50002 <-----Same here change this to port the repeater resides on? ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER: True IPSC_MODE: DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL: False RCM: True CON_APP: True XNL_CALL: False XNL_MASTER: False DATA_CALL: True VOICE_CALL: True MASTER_PEER: False AUTH_ENABLED: True AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001 On Sat, Dec 26, 2015 at 4:40 PM, Steve Zingman <szingman@msgstor.com> wrote:
The dmrlink.cfg in playback is only for playback. Disable or remove N1XBM_MASTER Make sure it connects to the master as a peer
On 12/26/2015 04:33 PM, Robert Newberry wrote:
So long e-mail here with questions.
I should be working in /opt/dmrlink/playback The files I need to be concerned with are dmrlink.cfg and playback_config.py Now to get echo going do I just run playback.py?
So I setup up playback_config.py with TG 9998 time slot 0...well one, but I think you know what I mean. I programed my radio the same way. I also programmed the repeater, That end of it seems to be OK.
Now dmrlink.cfg is where I am confused. So I've pointed my repeater to 192.168.0.203 port 50002 which is the IP of my RPI2. I've confirmed my auth key is correct. Got any suggestions where I am hosed?
[PLAYBACK_PEER] ENABLED: True RADIO_ID: 12345 IP: 0.0.0.0 PORT: 50002 ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER: True IPSC_MODE: DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL: False RCM: True CON_APP: True XNL_CALL: False XNL_MASTER: False DATA_CALL: True VOICE_CALL: True MASTER_PEER: False AUTH_ENABLED: True AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 MASTER_PORT: 50001
[N1XBM_MASTER] ENABLED: True RADIO_ID: 54321 IP: 0.0.0.0 PORT: 50001 ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER: True IPSC_MODE: DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL: False RCM: True CON_APP: True XNL_CALL: False XNL_MASTER: False DATA_CALL: True VOICE_CALL: True MASTER_PEER: True AUTH_ENABLED: True AUTH_KEY: A1B2C3 # Below not used for a Master # MASTER_IP: 1.2.3.4 # MASTER_PORT: 50000
On Fri, Dec 25, 2015 at 1:14 PM, Steve Zingman <szingman@msgstor.com> wrote:
It sends to the same TS and TG defined in payback config
On 12/25/2015 01:13 PM, Robert Newberry wrote:
Sorry I hit send a little to early.
I would assume there has to be a place somewhere that would indicate where to send that back to.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 25, 2015 1:11 PM, "Robert Newberry" <N1XBM@amsat.org> wrote:
So in dmrlink.cfg I have my RPI2 as a master. I've pointed my repeater at my RPI2. That all seems fine, where I'm confused is how does the software know how or where to echo the audio back to?
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
On Dec 24, 2015 6:28 PM, "Steve Zingman" < <szingman@msgstor.com> szingman@msgstor.com> wrote:
It's in dmrlink.cfg
Sent via smoke signal (AT&T 4G LTE)
-------- Original message -------- From: Robert Newberry < <N1XBM@amsat.org>N1XBM@amsat.org> Date: 12/24/2015 3:14 PM (GMT-05:00) To: Digital linking using Asterisk and app_rpt < allstar-digital@lists.keekles.org> Subject: [Allstar Digital] Playback
I edited /opt/dmrlink/playback/dmrlink.cfg I did the same for playback_config.py in the same directory
I ran dmrlink.py and didn't get any errors. I the hit ctrl c and then ran playback.py I didn't see any errors. Although I'm not getting any echo.
Is there any things I should be looking at to troubleshoot?
Also I want to see the log live on the console, but I can't remember how.
N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Everything at the top is OK. All 3 below should point at your master On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else? On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman <szingman@msgstor.com> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
What is your master listening on? does dmrlink.py in the playback directory connect correctly? On 12/26/2015 05:11 PM, Robert Newberry wrote:
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else?
On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
OK so in my repeater programming I've set it as a peer. I assigned the repeater an IP of 192.168.0.202 with a udp of 50002. I've also set in the programming as the master 192.168.0.203 with a upd of 50001. When I looked at the log it looks like the repeater is getting the keep-alives because I see the IP of the repeater in the log file. Also when I run playback.py I do not get any errors. You've seen whats in my dmrlink.cfg because I sent it to you. On Sat, Dec 26, 2015 at 5:12 PM, Steve Zingman <szingman@msgstor.com> wrote:
What is your master listening on? does dmrlink.py in the playback directory connect correctly?
On 12/26/2015 05:11 PM, Robert Newberry wrote:
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else?
On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman <szingman@msgstor.com> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
When you run the dmrlink.py in the playback directory does it connect correctly to your master? On 12/26/2015 05:19 PM, Robert Newberry wrote:
OK so in my repeater programming I've set it as a peer. I assigned the repeater an IP of 192.168.0.202 with a udp of 50002. I've also set in the programming as the master 192.168.0.203 with a upd of 50001. When I looked at the log it looks like the repeater is getting the keep-alives because I see the IP of the repeater in the log file. Also when I run playback.py I do not get any errors.
You've seen whats in my dmrlink.cfg because I sent it to you.
On Sat, Dec 26, 2015 at 5:12 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
What is your master listening on? does dmrlink.py in the playback directory connect correctly?
On 12/26/2015 05:11 PM, Robert Newberry wrote:
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else?
On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
herer is a copy of my log. It looks like it keeps registering over and over? INFO 2015-12-26 17:44:07,564 DMRlink 'dmrlink.py' (c) 2013 - 2015 N0MJS & the K0USY Group - SYSTEM STARTING... INFO 2015-12-26 17:44:07,565 (PLAYBACK_PEER) IPSC Instance Created: 12345, 0.0.0.0:50002 DEBUG 2015-12-26 17:44:07,567 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:07,569 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:12,573 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:12,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:17,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:17,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:22,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:22,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:27,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:27,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:32,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:32,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:37,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:37,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:42,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:42,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:47,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:47,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:52,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:52,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:57,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:57,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:45:02,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:45:02,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 On Sat, Dec 26, 2015 at 5:20 PM, Steve Zingman <szingman@msgstor.com> wrote:
When you run the dmrlink.py in the playback directory does it connect correctly to your master?
On 12/26/2015 05:19 PM, Robert Newberry wrote:
OK so in my repeater programming I've set it as a peer. I assigned the repeater an IP of 192.168.0.202 with a udp of 50002. I've also set in the programming as the master 192.168.0.203 with a upd of 50001. When I looked at the log it looks like the repeater is getting the keep-alives because I see the IP of the repeater in the log file. Also when I run playback.py I do not get any errors.
You've seen whats in my dmrlink.cfg because I sent it to you.
On Sat, Dec 26, 2015 at 5:12 PM, Steve Zingman <szingman@msgstor.com> wrote:
What is your master listening on? does dmrlink.py in the playback directory connect correctly?
On 12/26/2015 05:11 PM, Robert Newberry wrote:
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else?
On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman < <szingman@msgstor.com> szingman@msgstor.com> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
Does this data match what you have defined in your master? AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 MASTER_PORT: 50001 On 12/26/2015 05:48 PM, Robert Newberry wrote:
herer is a copy of my log. It looks like it keeps registering over and over?
INFO 2015-12-26 17:44:07,564 DMRlink 'dmrlink.py' (c) 2013 - 2015 N0MJS & the K0USY Group - SYSTEM STARTING... INFO 2015-12-26 17:44:07,565 (PLAYBACK_PEER) IPSC Instance Created: 12345, 0.0.0.0:50002 <http://0.0.0.0:50002> DEBUG 2015-12-26 17:44:07,567 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:07,569 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:12,573 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:12,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:17,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:17,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:22,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:22,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:27,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:27,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:32,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:32,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:37,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:37,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:42,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:42,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:47,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:47,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:52,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:52,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:44:57,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:57,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001> DEBUG 2015-12-26 17:45:02,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:45:02,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 <http://192.168.0.203:50001>
On Sat, Dec 26, 2015 at 5:20 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
When you run the dmrlink.py in the playback directory does it connect correctly to your master?
On 12/26/2015 05:19 PM, Robert Newberry wrote:
OK so in my repeater programming I've set it as a peer. I assigned the repeater an IP of 192.168.0.202 with a udp of 50002. I've also set in the programming as the master 192.168.0.203 with a upd of 50001. When I looked at the log it looks like the repeater is getting the keep-alives because I see the IP of the repeater in the log file. Also when I run playback.py I do not get any errors.
You've seen whats in my dmrlink.cfg because I sent it to you.
On Sat, Dec 26, 2015 at 5:12 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
What is your master listening on? does dmrlink.py in the playback directory connect correctly?
On 12/26/2015 05:11 PM, Robert Newberry wrote:
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else?
On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
So my Master is the RPI2 that I am running dmrlink on. As far as I know I only have defined that information in the peer stanza I sent you. Which is in the dmrlink.cfg. It also is the same information I have put in the repeater for where to look for a master. On Sat, Dec 26, 2015 at 5:49 PM, Steve Zingman <szingman@msgstor.com> wrote:
Does this data match what you have defined in your master? AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 MASTER_PORT: 50001
On 12/26/2015 05:48 PM, Robert Newberry wrote:
herer is a copy of my log. It looks like it keeps registering over and over?
INFO 2015-12-26 17:44:07,564 DMRlink 'dmrlink.py' (c) 2013 - 2015 N0MJS & the K0USY Group - SYSTEM STARTING... INFO 2015-12-26 17:44:07,565 (PLAYBACK_PEER) IPSC Instance Created: 12345, 0.0.0.0:50002 DEBUG 2015-12-26 17:44:07,567 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:07,569 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:12,573 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:12,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:17,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:17,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:22,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:22,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:27,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:27,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:32,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:32,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:37,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:37,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:42,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:42,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:47,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:47,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:52,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:52,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:57,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:57,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:45:02,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:45:02,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001
On Sat, Dec 26, 2015 at 5:20 PM, Steve Zingman <szingman@msgstor.com> wrote:
When you run the dmrlink.py in the playback directory does it connect correctly to your master?
On 12/26/2015 05:19 PM, Robert Newberry wrote:
OK so in my repeater programming I've set it as a peer. I assigned the repeater an IP of 192.168.0.202 with a udp of 50002. I've also set in the programming as the master 192.168.0.203 with a upd of 50001. When I looked at the log it looks like the repeater is getting the keep-alives because I see the IP of the repeater in the log file. Also when I run playback.py I do not get any errors.
You've seen whats in my dmrlink.cfg because I sent it to you.
On Sat, Dec 26, 2015 at 5:12 PM, Steve Zingman < <szingman@msgstor.com> szingman@msgstor.com> wrote:
What is your master listening on? does dmrlink.py in the playback directory connect correctly?
On 12/26/2015 05:11 PM, Robert Newberry wrote:
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else?
On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman < <szingman@msgstor.com> szingman@msgstor.com> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
The UDP ports have to match between the master and peer. On Dec 26, 2015 4:56 PM, "Robert Newberry" <N1XBM@amsat.org> wrote:
So my Master is the RPI2 that I am running dmrlink on. As far as I know I only have defined that information in the peer stanza I sent you. Which is in the dmrlink.cfg. It also is the same information I have put in the repeater for where to look for a master.
On Sat, Dec 26, 2015 at 5:49 PM, Steve Zingman <szingman@msgstor.com> wrote:
Does this data match what you have defined in your master? AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 MASTER_PORT: 50001
On 12/26/2015 05:48 PM, Robert Newberry wrote:
herer is a copy of my log. It looks like it keeps registering over and over?
INFO 2015-12-26 17:44:07,564 DMRlink 'dmrlink.py' (c) 2013 - 2015 N0MJS & the K0USY Group - SYSTEM STARTING... INFO 2015-12-26 17:44:07,565 (PLAYBACK_PEER) IPSC Instance Created: 12345, 0.0.0.0:50002 DEBUG 2015-12-26 17:44:07,567 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:07,569 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:12,573 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:12,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:17,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:17,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:22,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:22,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:27,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:27,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:32,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:32,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:37,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:37,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:42,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:42,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:47,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:47,574 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:52,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:52,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:44:57,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:44:57,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001 DEBUG 2015-12-26 17:45:02,572 (PLAYBACK_PEER) PEER Connection Maintenance Loop Started INFO 2015-12-26 17:45:02,573 (PLAYBACK_PEER) Registering with the Master: 192.168.0.203:50001
On Sat, Dec 26, 2015 at 5:20 PM, Steve Zingman <szingman@msgstor.com> wrote:
When you run the dmrlink.py in the playback directory does it connect correctly to your master?
On 12/26/2015 05:19 PM, Robert Newberry wrote:
OK so in my repeater programming I've set it as a peer. I assigned the repeater an IP of 192.168.0.202 with a udp of 50002. I've also set in the programming as the master 192.168.0.203 with a upd of 50001. When I looked at the log it looks like the repeater is getting the keep-alives because I see the IP of the repeater in the log file. Also when I run playback.py I do not get any errors.
You've seen whats in my dmrlink.cfg because I sent it to you.
On Sat, Dec 26, 2015 at 5:12 PM, Steve Zingman < <szingman@msgstor.com> szingman@msgstor.com> wrote:
What is your master listening on? does dmrlink.py in the playback directory connect correctly?
On 12/26/2015 05:11 PM, Robert Newberry wrote:
OK great, Yes and my master is the RPI2 running DMRlink. Should I maybe not be using 192.168.0.203, and rather point it to 0.0.0.0 or something like that. It still isnt working, with the config I've sent you. So I have issues somewhere else?
On Sat, Dec 26, 2015 at 5:07 PM, Steve Zingman < <szingman@msgstor.com> szingman@msgstor.com> wrote:
Everything at the top is OK. All 3 below should point at your master
On 12/26/2015 05:04 PM, Robert Newberry wrote:
AUTH_KEY: A1B2C3 MASTER_IP: 192.168.0.203 <---this is the IP of the RPI, I assume this stays the same? MASTER_PORT: 50001
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
participants (3)
-
Michael Hebert -
Robert Newberry -
Steve Zingman