[Allstar Digital] Playback
Robert Newberry
N1XBM at amsat.org
Sat Dec 26 17:04:21 EST 2015
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 at 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 at 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 at 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 at msgstor.com>
>>> szingman at msgstor.com> wrote:
>>>
>>>> It's in dmrlink.cfg
>>>>
>>>>
>>>>
>>>> Sent via smoke signal (AT&T 4G LTE)
>>>>
>>>>
>>>> -------- Original message --------
>>>> From: Robert Newberry < <N1XBM at amsat.org>N1XBM at amsat.org>
>>>> Date: 12/24/2015 3:14 PM (GMT-05:00)
>>>> To: Digital linking using Asterisk and app_rpt <
>>>> allstar-digital at 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 at lists.keekles.org
>>>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>>>
>>>>
>>
>> _______________________________________________
>> Allstar-Digital mailing listAllstar-Digital at 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 at lists.keekles.org
>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>>
>>
>
>
> _______________________________________________
> Allstar-Digital mailing listAllstar-Digital at 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 at lists.keekles.org
> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/allstar-digital/attachments/20151226/1ec33a9e/attachment.html>
More information about the Allstar-Digital
mailing list