272
edits
Changes
Jump to navigation
Jump to search
Line 9:
Line 9: − − Line 33:
Line 31: − + Line 117:
Line 115: − + − − − − − − − − − −
no edit summary
The actions to be taken, and methods and steps required for doing so are specified in the rpt.conf
The actions to be taken, and methods and steps required for doing so are specified in the rpt.conf
file under the [events] section (or other named section, settable with events=sectionname under the
file under the [events] section (or other named section, settable with events=sectionname under the
node number section also in rpt.conf).
node number section also in rpt.conf).
keying status, as follows:
keying status, as follows:
<NUMALINKS>,<NODEMUM><MODE><RXKEYED>[,<NODEMUM><MODE><RXKEYED>...]
<NUMALINKS>,<NODEMUM><MODE><RXKEYED>[,<NODEMUM><MODE><RXKEYED>...]
For example: 2,2000TU,2001RK would indicate that there are 2 adjacent nodes linked currently,
For example: 2,2000TU,2001RK would indicate that there are 2 adjacent nodes linked currently,
*CLI> rpt showvars <nodenum>
*CLI> rpt showvars <nodenum>
Also, a channel variable for a node may be set from the Asterisk Dialplan as follows:
Also, a channel variable for a node may be set from the Asterisk Dialplan as follows:
rpt(<nodenum>,V,<name=value>)
rpt(<nodenum>,V,<name=value>)
For example, for extension 1234 priority 5, set variable 'MYVAR' to '0' for node 2000:
For example, for extension 1234 priority 5, set variable 'MYVAR' to '0' for node 2000:
exten => 1234,5,rpt(2000,V,MYVAR=0)
exten => 1234,5,rpt(2000,V,MYVAR=0)
Granted, there may very well be some things (such as interesting information that can be expressed
Granted, there may very well be some things (such as interesting information that can be expressed
within this subsystem) that has been overlooked, and any suggestions and/or comments regarding this
within this subsystem) that has been overlooked, and any suggestions and/or comments regarding this
whole thing would be much appreciated.
whole thing would be much appreciated.
This also opens a completely new avenue of customization and individual creativity for each system
This also opens a completely new avenue of customization and individual creativity for each system
implementer. There are many innovative things that can be done with this. Also there are many just plain
implementer. There are many innovative things that can be done with this. Also there are many just plain
silly ones, such as connecting your doorbell to one the input pins on the URI, and having the system
silly ones, such as connecting your doorbell to one the input pins on the URI, and having the system
connect to your favorite Echolink node or something when someone rings the doorbell.
connect to your favorite Echolink node or something when someone rings the doorbell.
At some point there should be a contest to see who can come up with the most utterly ludicrous
At some point there should be a contest to see who can come up with the most utterly ludicrous
appication of this subsystem. There are many possibilities to explore in this area. Hint: you will
appication of this subsystem. There are many possibilities to explore in this area. Hint: you will
get '''major''' extra bonus points if it involves the script re-writing itself (self-modifying
get '''major''' extra bonus points if it involves the script re-writing itself (self-modifying
code, that exhibits at least plausibility of long-term stability (going to poo-poo in less then
code, that exhibits at least plausibility of long-term stability (going to poo-poo in less then
1000 iterations is ''just'' not acceptible)).
1000 iterations is ''just'' not acceptible)).
In any case, please contribute whatever wonderful configurations you come up with so that all users
In any case, please contribute whatever wonderful configurations you come up with so that all users
may have the benefits of all the wonderful ideas everyone comes up with.
may have the benefits of all the wonderful ideas everyone comes up with.