1=ilink,1 ; Disconnect Link xxx
2=ilink,2 ; Con Link xxx RX-Only (mon)
3=ilink,3 ; Con Link xxx TX
4=ilink,4 ; Enter Command Mode on XXX
5=macro ; Run a macro ##
So
x=ilink,8
Choose the value of x carefully so you don’t conflict with any other commands.
If you are already using three digit DTMF codes in 831-839 then you can’t use just 8 for a different command. Otherwise 831-839 will be detected as the “8” command and “3n” is part of the parameter for the command.
If you look at rpt.conf there’s already pre-created function macros in the 81 series:
811 = ilink,11 ; Disconnect a previously permanently connected link
812 = ilink,12 ; Permanently connect specified link -- monitor only
813 = ilink,13 ; Permanently connect specified link -- tranceive
; 815 = ilink,15 ; Full system status (all nodes)
816 = ilink,16 ; Reconnect links disconnected with "disconnect all links"
Uncomment those, if necessary, and then set:
startup_macro = *81362499
Also make sure that your startup_macro is inside the correct node template stanza. For example from one of my systems:
Yea, I misspoke anyway not looking at the command correctly and using a bad memory.
It was ilink,13
Your friends node does not matter here. Just yours if you are initiating the connection.
But it sounds like a conflict with other commands, which we can not see.
For a test, try to assign it 69 unless you have commands that start with a 6 or 69
Save your edit and reload/restart asterisk before testing.
If it works, you will need to scrub through your file looking for the conflict of using 8.
Just a skinny…
If you have a 2/3 digit command that starts with an 9,
you can not then have a command that is an 9 as the longer commands will never execute.
Asterisk is a ‘first match system’. It will execute the first command it recognizes.
Not positive what would happen with 2 of exact match, but likely the one it looks at first wins.
Just something to think about as you look it over.