[Allstar Digital] Playback
Steve Zingman
szingman at msgstor.com
Sat Dec 26 17:49:39 EST 2015
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 at msgstor.com
> <mailto:szingman at 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 at msgstor.com <mailto:szingman at 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 at msgstor.com <mailto:szingman at 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 at lists.keekles.org
>>> <mailto:Allstar-Digital at lists.keekles.org>
>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Allstar-Digital mailing list
>>> Allstar-Digital at lists.keekles.org
>>> <mailto:Allstar-Digital at 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 at lists.keekles.org
>> <mailto:Allstar-Digital at lists.keekles.org>
>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>
>>
>>
>>
>> _______________________________________________
>> Allstar-Digital mailing list
>> Allstar-Digital at lists.keekles.org
>> <mailto:Allstar-Digital at 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 at lists.keekles.org
> <mailto:Allstar-Digital at lists.keekles.org>
> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>
>
>
>
> _______________________________________________
> Allstar-Digital mailing list
> Allstar-Digital at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/allstar-digital/attachments/20151226/7182d816/attachment.html>
More information about the Allstar-Digital
mailing list