Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1 5 . A d v a n c e d To p ic s
15.1. Replication of settings
If you have a large number of ip.buffers to configure, you can quickly replicate their
settings. Follow this procedure:
Program up a target ip.buffer
Use the Configuration / Download to save to a file.
Edit the file and remove the following lines
o
c.network.name
o
c.network.ip
o
Remove any other settings that are different between each unit
Now connect each ip.buffer in turn:
o
Use SEDiscover to locate and web-browse the buffer
o
Use the Configuration / Upload to send the modified file
If you have chosen to hide passwords then you cannot replicate the passwords!
They should either be manually edited into the config file or set manually via
the web pages.
15.2. Lua extensions
These extensions are available for the scripting. See section 14.2
The full list of Lua extensions and variables is available in the Scannex document
“
ip.buffer_oemlua_manual
”.
15.2.1. Alert System
alert.register_oneshot(id, msg)
Registers a “one shot” alert. As soon as the alarm is triggered for the id, the
alert is sent. If the “msg” is not blank, then this sets the default text that
accompanies the alert (which can be overridden in the call to alert.alarm)
e.g. alert.register_oneshot(“Test”, “Default message”)
alert.register_holdoff(id, msg, time, repeat)
Registers a “hold off” style alert. The alert will be sent on the first alarm
occurrence, but will have to wait for “time” minutes before it is considered
reset. If the alert does not reset the alert is repeated every “repeat”
minutes. A value of zero implies no repeat.
e.g. alert.register_holdoff(“PBXFailure”, “”, 10, 0)
alert.register_counter(id, msg, limit, period, repeat)
Registers a counting alarm. If more than “limit” alarms occur within the
“period” minutes the alert will be triggered. While triggered the alert will
be resent every “repeat” minutes.
e.g. alert.register_counter(“PBXFailure”, “”, 10, 60, 120)
1
c.network.name because each box should have a unique name in the whole system, and
c.network.ip as each probably has a separate IP address – unless they are being installed in DHCP
enabled situations or in separate physical sites.
Page 121
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1 5 . A d v a n c e d To p ic s
15.1. Replication of settings
If you have a large number of ip.buffers to configure, you can quickly replicate their
settings. Follow this procedure:
Program up a target ip.buffer
Use the Configuration / Download to save to a file.
Edit the file and remove the following lines
o
c.network.name
o
c.network.ip
o
Remove any other settings that are different between each unit
Now connect each ip.buffer in turn:
o
Use SEDiscover to locate and web-browse the buffer
o
Use the Configuration / Upload to send the modified file
If you have chosen to hide passwords then you cannot replicate the passwords!
They should either be manually edited into the config file or set manually via
the web pages.
15.2. Lua extensions
These extensions are available for the scripting. See section 14.2
The full list of Lua extensions and variables is available in the Scannex document
“
ip.buffer_oemlua_manual
”.
15.2.1. Alert System
alert.register_oneshot(id, msg)
Registers a “one shot” alert. As soon as the alarm is triggered for the id, the
alert is sent. If the “msg” is not blank, then this sets the default text that
accompanies the alert (which can be overridden in the call to alert.alarm)
e.g. alert.register_oneshot(“Test”, “Default message”)
alert.register_holdoff(id, msg, time, repeat)
Registers a “hold off” style alert. The alert will be sent on the first alarm
occurrence, but will have to wait for “time” minutes before it is considered
reset. If the alert does not reset the alert is repeated every “repeat”
minutes. A value of zero implies no repeat.
e.g. alert.register_holdoff(“PBXFailure”, “”, 10, 0)
alert.register_counter(id, msg, limit, period, repeat)
Registers a counting alarm. If more than “limit” alarms occur within the
“period” minutes the alert will be triggered. While triggered the alert will
be resent every “repeat” minutes.
e.g. alert.register_counter(“PBXFailure”, “”, 10, 60, 120)
1
c.network.name because each box should have a unique name in the whole system, and
c.network.ip as each probably has a separate IP address – unless they are being installed in DHCP
enabled situations or in separate physical sites.
Page 121
