[App_rpt-users] DTMF By-Direction Propagate

[Jesse Lloyd]

No I'm not, what does it do?

I did manage to figure it out, after the link is up I can do a rpt fun 90 A480 and it'll put the other node in command mode. Interestingly you can't do that in the startup macro for node 90 as the link isn't established at the time it runs the command and it fails. It you just do init.d/asterisk start && sleep 10 && asterisk -rx "rpt fun 90 A480 " it works great. 

Jesse


> On Sep 14, 2015, at 8:53 AM, Tim Sawyer <tisawyer at gmail.com> wrote:
> 
> Are you using the mixminus parameter?
> 
>> On Sunday, September 13, 2015, Jesse Lloyd <ve7lyd at gmail.com> wrote:
>> Hello All,
>> 
>> I have a RF network built out that has various drop repeaters controlled via DTMF. We've been having issues with one of our RF links, so we decided to use 2 RTCM's and an Allstar server to link the sites together via IP instead.
>> 
>> This worked great, however I'm having difficulties getting DTMF to pass. On the network we use * and # to control the drop repeaters, so I changed the function characters to: funcchar = A endchar = D, since A and D aren't used on our network. The link is permanently connected so I just wrote a startup macro for node 80: startup_macro = A390DA40 which connects node 80 to 90 and puts 90 into control mode so DTMF passes.
>> 
>> The problem is DTMF doesn't pass the other direction.  I can't put startup_macro = A380DA40 into node 90's stanza, asterisk complains that the nodes are currently connected.
>> 
>> Any ideas how I can do this? Really there is only a handful of commands that need to propagate over the IP link, I read on one of the archived mailing list emails that you can write a COP for every command needed to propagate over the IP link, but I can't figure out how to do that.
>> 
>> Any help would be great,
>> 
>> Thx,
>> 
>> Jesse
> 
> 
> -- 
> --
> Tim
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150914/6b32b5a2/attachment.html>