Scannex ip.buffer User manual

ip.buffer Manual
3rd March 2021
Firmware Version 3.01
ip.buffer Manual
3rd March 2021
Firmware Version 3.01

ip.buffer Manual
Date Author Release
2007-06-21 MP For version 1.00
...
2014-05-14 MP For version 2.90
2014-10-23 MP For version 2.91
2015-10-07 MP For version 2.92
2016-04-26 MP For version 2.93
2018-03-29 MP For version 2.95
2019-07-16 MP For version 2.97 (SFTP)
2021-03-03 MP For version 3.01
Copyright © UK 2007-2021 Scannex Electronics Limited. All rights reserved worldwide.
Scannex Electronics Ltd, UK
t: [phone]
f: [phone]
http://www.scannex.co.uk
[e-mail]
Scannex LLC, USA
t: 1-866-4BUFFER
(1-866-428-3337)
http://www.scannex.com
[e-mail]
ip.buffer Manual
Date Author Release
2007-06-21 MP For version 1.00
...
2014-05-14 MP For version 2.90
2014-10-23 MP For version 2.91
2015-10-07 MP For version 2.92
2016-04-26 MP For version 2.93
2018-03-29 MP For version 2.95
2019-07-16 MP For version 2.97 (SFTP)
2021-03-03 MP For version 3.01
Copyright © UK 2007-2021 Scannex Electronics Limited. All rights reserved worldwide.
Scannex Electronics Ltd, UK
t: [phone]
f: [phone]
http://www.scannex.co.uk
[email protected]
Scannex LLC, USA
t: 1-866-4BUFFER
(1-866-428-3337)
http://www.scannex.com
[email protected]

Table of Contents
1.Introduction...............................................1
1.1.The Range............................................1
1.2.Features..............................................1
1.3.Block Diagrams......................................3
1.3.1.System Overview..............................3
1.3.2.Source...........................................4
1.3.3.Destination.....................................5
1.4.Firmware.............................................6
2.GPRS (Cellular) Modem..................................7
2.1.GPRS Safety Precautions...........................7
2.1.1.GPRS Radiation Exposure Statements......7
2.2.Installing a SIM card................................8
2.3.Installing the antenna..............................8
3.Fitting Batteries..........................................9
3.1.1.Battery Precautions...........................9
3.1.2.Installing in an ip.1..........................10
3.1.3.Installing in an ip.4..........................11
4.Physical Mounting.......................................12
4.1.ip.1 – plastic box..................................12
4.1.1.DIN Rail Mounting............................12
4.1.2.Wall mounting................................12
4.2.ip.4 – metal case..................................12
5.Installation...............................................13
5.1.Connections........................................13
5.2.Getting Started....................................14
5.3.Forgotten passwords & factory defaults.......15
6.Front Panel...............................................16
7.Status Web page.........................................18
7.1.Channel: Source...................................18
7.2.Channel: Storage..................................18
7.3.Channel: Destination.............................19
7.4.Modem..............................................19
7.5.System..............................................19
8.SETUP.....................................................20
8.1.Web Interface......................................20
8.2.Global: Settings....................................21
8.2.1.Network.......................................21
8.2.2.Time...........................................26
8.2.3.Power..........................................27
8.2.4.Modem.........................................28
8.2.5.Modem Out...................................30
8.2.6.SMTP Email Servers..........................34
8.2.7.Alerts..........................................36
8.2.8.Alert List......................................40
8.2.9.RADIUS.........................................41
8.2.10.Certificates for SSL/TLS and SSH........45
8.2.11.Advanced Security Options...............48
8.2.12.Ciphers override strings...................49
8.2.13.Signature Hashes override strings.......50
8.2.14.FTP...........................................51
8.2.15.Web...........................................53
8.2.16.Cloud Server................................55
8.3.Date and Time Synchronize......................57
9.Channels..................................................58
10.Sources..................................................60
10.1.COM Serial........................................60
10.1.1.Settings......................................60
10.1.2.Connection to a PC serial port...........63
10.1.3.When using a Y-lead.......................64
10.2.TCP.................................................65
10.2.1.Match, Send & Heartbeat special
characters............................................66
10.3.UDP.................................................67
10.3.1.Syslog Collection...........................67
10.3.2.SNMP Trap Collection......................67
10.3.3.RADIUS Accounting Collection............69
10.4.FTP Server.........................................70
10.4.1.FTP Server Notes...........................71
10.5.Cloud Server......................................72
10.6.None...............................................72
10.7.Common Modules................................73
10.7.1.Protocol......................................73
10.7.2.Protocol: ASCII Lines.......................75
10.7.3.Protocol: Alcatel TCP/IP [port 2533]....76
10.7.4.Protocol: Avaya RSP TCP/IP..............77
10.7.5.Protocol: Binary (full 8-bit)...............77
10.7.6.Protocol: Generic Records................78
10.7.7.Protocol: Inter-Tel/Mitel Axxess & 5000
TCP/IP [port 4000]..................................80
10.7.8.Protocol: iSDX binary......................81
10.7.9.Protocol: NEC (STX/ETX) Serial..........81
10.7.10.Protocol: NEC NEAX TCP/IP.............82
10.7.11.Protocol: Nortel BCM Live TCP/IP......83
10.7.12.Protocol: Nortel Meridian & Norstar...84
10.7.13.Protocol: Panasonic KX-TD TCP/IP [port
2300]..................................................85
10.7.14.Protocol: Philips FDCR TCP/IP [port
2599]..................................................85
10.7.15.Time Stamping............................86
10.7.16.Extra tokens for delivery filenames....88
10.7.17.Pass-through...............................89
10.7.18.Notification................................92
11.Destinations............................................93
11.1.Email push (SMTP client).......................93
11.2.HTTP POST to Cloud Server....................94
11.3.FTP Server.........................................95
11.3.1.Supported FTP server commands........96
11.4.FTP Push (client).................................97
11.4.1.Overwrite and Append...................100
11.4.2.Tmp File & Rename mode16............100
11.5.TCP Server (passive)...........................101
11.6.TCP Push (active/client)......................102
11.7.COM port serial.................................104
11.8.Legacy Emulation (TCP Server)...............105
11.9.None..............................................106
11.10.Destination Common Modules...............107
11.10.1.Data Markers.............................107
11.10.2.Data Security.............................107
11.10.3.Push Triggers.............................108
12.Storage.................................................110
13.Tools....................................................111
13.1.General...........................................111
13.1.1.Live Record View..........................111
Table of Contents
1.Introduction...............................................1
1.1.The Range............................................1
1.2.Features..............................................1
1.3.Block Diagrams......................................3
1.3.1.System Overview..............................3
1.3.2.Source...........................................4
1.3.3.Destination.....................................5
1.4.Firmware.............................................6
2.GPRS (Cellular) Modem..................................7
2.1.GPRS Safety Precautions...........................7
2.1.1.GPRS Radiation Exposure Statements......7
2.2.Installing a SIM card................................8
2.3.Installing the antenna..............................8
3.Fitting Batteries..........................................9
3.1.1.Battery Precautions...........................9
3.1.2.Installing in an ip.1..........................10
3.1.3.Installing in an ip.4..........................11
4.Physical Mounting.......................................12
4.1.ip.1 – plastic box..................................12
4.1.1.DIN Rail Mounting............................12
4.1.2.Wall mounting................................12
4.2.ip.4 – metal case..................................12
5.Installation...............................................13
5.1.Connections........................................13
5.2.Getting Started....................................14
5.3.Forgotten passwords & factory defaults.......15
6.Front Panel...............................................16
7.Status Web page.........................................18
7.1.Channel: Source...................................18
7.2.Channel: Storage..................................18
7.3.Channel: Destination.............................19
7.4.Modem..............................................19
7.5.System..............................................19
8.SETUP.....................................................20
8.1.Web Interface......................................20
8.2.Global: Settings....................................21
8.2.1.Network.......................................21
8.2.2.Time...........................................26
8.2.3.Power..........................................27
8.2.4.Modem.........................................28
8.2.5.Modem Out...................................30
8.2.6.SMTP Email Servers..........................34
8.2.7.Alerts..........................................36
8.2.8.Alert List......................................40
8.2.9.RADIUS.........................................41
8.2.10.Certificates for SSL/TLS and SSH........45
8.2.11.Advanced Security Options...............48
8.2.12.Ciphers override strings...................49
8.2.13.Signature Hashes override strings.......50
8.2.14.FTP...........................................51
8.2.15.Web...........................................53
8.2.16.Cloud Server................................55
8.3.Date and Time Synchronize......................57
9.Channels..................................................58
10.Sources..................................................60
10.1.COM Serial........................................60
10.1.1.Settings......................................60
10.1.2.Connection to a PC serial port...........63
10.1.3.When using a Y-lead.......................64
10.2.TCP.................................................65
10.2.1.Match, Send & Heartbeat special
characters............................................66
10.3.UDP.................................................67
10.3.1.Syslog Collection...........................67
10.3.2.SNMP Trap Collection......................67
10.3.3.RADIUS Accounting Collection............69
10.4.FTP Server.........................................70
10.4.1.FTP Server Notes...........................71
10.5.Cloud Server......................................72
10.6.None...............................................72
10.7.Common Modules................................73
10.7.1.Protocol......................................73
10.7.2.Protocol: ASCII Lines.......................75
10.7.3.Protocol: Alcatel TCP/IP [port 2533]....76
10.7.4.Protocol: Avaya RSP TCP/IP..............77
10.7.5.Protocol: Binary (full 8-bit)...............77
10.7.6.Protocol: Generic Records................78
10.7.7.Protocol: Inter-Tel/Mitel Axxess & 5000
TCP/IP [port 4000]..................................80
10.7.8.Protocol: iSDX binary......................81
10.7.9.Protocol: NEC (STX/ETX) Serial..........81
10.7.10.Protocol: NEC NEAX TCP/IP.............82
10.7.11.Protocol: Nortel BCM Live TCP/IP......83
10.7.12.Protocol: Nortel Meridian & Norstar...84
10.7.13.Protocol: Panasonic KX-TD TCP/IP [port
2300]..................................................85
10.7.14.Protocol: Philips FDCR TCP/IP [port
2599]..................................................85
10.7.15.Time Stamping............................86
10.7.16.Extra tokens for delivery filenames....88
10.7.17.Pass-through...............................89
10.7.18.Notification................................92
11.Destinations............................................93
11.1.Email push (SMTP client).......................93
11.2.HTTP POST to Cloud Server....................94
11.3.FTP Server.........................................95
11.3.1.Supported FTP server commands........96
11.4.FTP Push (client).................................97
11.4.1.Overwrite and Append...................100
11.4.2.Tmp File & Rename mode16............100
11.5.TCP Server (passive)...........................101
11.6.TCP Push (active/client)......................102
11.7.COM port serial.................................104
11.8.Legacy Emulation (TCP Server)...............105
11.9.None..............................................106
11.10.Destination Common Modules...............107
11.10.1.Data Markers.............................107
11.10.2.Data Security.............................107
11.10.3.Push Triggers.............................108
12.Storage.................................................110
13.Tools....................................................111
13.1.General...........................................111
13.1.1.Live Record View..........................111

13.1.2.Pass-Through Access......................112
13.1.3.Storage Counters..........................113
13.1.4.Reboot Lua.................................113
13.1.5.Reboot ip.buffer (cold boot)............113
13.1.6.Battery off (shutdown)...................113
13.2.Modem...........................................114
13.2.1.Clear timers...............................114
13.2.2.Hangup & Reset / Hangup & Power cycle
.......................................................114
13.3.Source, Pass-through, and Destination......114
13.4.Network..........................................115
13.4.1.Ping a device..............................115
13.4.2.Listening Ports.............................115
13.4.3.Network Tables............................115
13.5.Log................................................115
13.5.1.View Log....................................115
13.5.2.Send Log to Cloud Server................115
13.6.System............................................116
13.6.1.Upgrade Firmware........................116
13.6.2.Check for Updates........................117
13.6.3.System Memory...........................117
13.6.4.Diagnostics Dump.........................117
14.Advanced Setup......................................118
14.1.Configuration (Advanced).....................118
14.1.1.Edit..........................................118
14.1.2.Ad hoc change.............................119
14.1.3.Download...................................119
14.1.4.Upload......................................119
14.2.Script.............................................120
14.2.1.Edit..........................................120
14.2.2.Download...................................120
14.2.3.Upload......................................120
14.3.Server Certificate..............................121
14.3.1.Generate...................................121
14.3.2.Upload......................................123
14.3.3.Download server certificate............123
14.3.4.Download SSH publickey.................123
15.Advanced Topics......................................124
15.1.Replication of settings.........................124
15.2.Lua extensions..................................124
15.2.1.Alert System...............................124
15.2.2.Delivery Trigger System..................125
15.2.3.Comments within Lua code.............125
15.2.4.Sending data to the channel source...125
15.3.Example scripts.................................126
15.3.1.Simple prefix..............................126
15.3.2.Duplicating data..........................127
15.3.3.Discarding data............................127
15.3.4.Masking telephone digits................128
15.4.Upgrading Firmware – the Last Resort......129
16.SNMP Traps............................................130
16.1.Trap List..........................................130
16.2.Variable Bindings...............................131
17.SNMP Agent OID List.................................132
18.Cloud Server HTTP Implementation...............133
19.SFTP Cryptographic Elements......................134
20.Licenses................................................135
20.1.Lua License......................................135
20.2.zlib License......................................135
20.3.X509 certificate generation license.........136
20.4.SNMP Trap Decoding............................137
21.Specifications.........................................138
22.Optional 48V Power Supply.........................139
22.1.Two-pin connector..............................139
22.2.Schematic........................................139
23.PSTN Modem Country Codes and Approvals......140
24.Safety Warnings.......................................142
24.1.Optional AA Battery Caution..................142
24.2.Real Time Clock Battery Caution.............142
24.3.Ethernet Ports Caution........................142
24.4.Power Supply Caution..........................143
24.4.1.Scannex Approved PSUs..................143
24.5.General Warnings...............................143
24.6.Modem Caution (if fitted).....................143
24.7.A note about Power Connection, Surge
Protectors, and lightning............................143
24.8.South Africa.....................................143
25. Approvals.............................................144
25.1.EMC...............................................144
25.2.Safety.............................................144
25.3.Environmental...................................144
25.4.PSTN Modem.....................................144
25.5.GPRS Modem....................................144
25.6.3G/4G Modem...................................145
25.7.Export Control..................................145
25.8.European Union (EU) Statement.............146
25.8.1.EMC, Safety, and R&TTE Directive
Compliance.........................................146
25.8.2.Network Compatibility Declaration....146
25.9.Deutsch..........................................146
25.10.USA..............................................147
25.10.1.FCC Registration Information..........147
25.10.2.Repair Information......................147
25.10.3.FCC Rules Part 15 - Computing Devices
.......................................................148
25.10.4.GPRS Modem.............................148
25.11.Canada..........................................149
25.11.1.Industry Canada Information..........149
25.11.2.GPRS Modem.............................149
25.11.3.Industry Canada Regulatory Compliance
Information for Class B Equipment.............150
26.European Union Waste Electrical and Electronic
Equipment (WEEE) Statement..........................151
26.1.UK Users.........................................151
26.2.European Users (outside the UK).............151
26.3.Manufacturer/Responsible Party.............151
13.1.2.Pass-Through Access......................112
13.1.3.Storage Counters..........................113
13.1.4.Reboot Lua.................................113
13.1.5.Reboot ip.buffer (cold boot)............113
13.1.6.Battery off (shutdown)...................113
13.2.Modem...........................................114
13.2.1.Clear timers...............................114
13.2.2.Hangup & Reset / Hangup & Power cycle
.......................................................114
13.3.Source, Pass-through, and Destination......114
13.4.Network..........................................115
13.4.1.Ping a device..............................115
13.4.2.Listening Ports.............................115
13.4.3.Network Tables............................115
13.5.Log................................................115
13.5.1.View Log....................................115
13.5.2.Send Log to Cloud Server................115
13.6.System............................................116
13.6.1.Upgrade Firmware........................116
13.6.2.Check for Updates........................117
13.6.3.System Memory...........................117
13.6.4.Diagnostics Dump.........................117
14.Advanced Setup......................................118
14.1.Configuration (Advanced).....................118
14.1.1.Edit..........................................118
14.1.2.Ad hoc change.............................119
14.1.3.Download...................................119
14.1.4.Upload......................................119
14.2.Script.............................................120
14.2.1.Edit..........................................120
14.2.2.Download...................................120
14.2.3.Upload......................................120
14.3.Server Certificate..............................121
14.3.1.Generate...................................121
14.3.2.Upload......................................123
14.3.3.Download server certificate............123
14.3.4.Download SSH publickey.................123
15.Advanced Topics......................................124
15.1.Replication of settings.........................124
15.2.Lua extensions..................................124
15.2.1.Alert System...............................124
15.2.2.Delivery Trigger System..................125
15.2.3.Comments within Lua code.............125
15.2.4.Sending data to the channel source...125
15.3.Example scripts.................................126
15.3.1.Simple prefix..............................126
15.3.2.Duplicating data..........................127
15.3.3.Discarding data............................127
15.3.4.Masking telephone digits................128
15.4.Upgrading Firmware – the Last Resort......129
16.SNMP Traps............................................130
16.1.Trap List..........................................130
16.2.Variable Bindings...............................131
17.SNMP Agent OID List.................................132
18.Cloud Server HTTP Implementation...............133
19.SFTP Cryptographic Elements......................134
20.Licenses................................................135
20.1.Lua License......................................135
20.2.zlib License......................................135
20.3.X509 certificate generation license.........136
20.4.SNMP Trap Decoding............................137
21.Specifications.........................................138
22.Optional 48V Power Supply.........................139
22.1.Two-pin connector..............................139
22.2.Schematic........................................139
23.PSTN Modem Country Codes and Approvals......140
24.Safety Warnings.......................................142
24.1.Optional AA Battery Caution..................142
24.2.Real Time Clock Battery Caution.............142
24.3.Ethernet Ports Caution........................142
24.4.Power Supply Caution..........................143
24.4.1.Scannex Approved PSUs..................143
24.5.General Warnings...............................143
24.6.Modem Caution (if fitted).....................143
24.7.A note about Power Connection, Surge
Protectors, and lightning............................143
24.8.South Africa.....................................143
25. Approvals.............................................144
25.1.EMC...............................................144
25.2.Safety.............................................144
25.3.Environmental...................................144
25.4.PSTN Modem.....................................144
25.5.GPRS Modem....................................144
25.6.3G/4G Modem...................................145
25.7.Export Control..................................145
25.8.European Union (EU) Statement.............146
25.8.1.EMC, Safety, and R&TTE Directive
Compliance.........................................146
25.8.2.Network Compatibility Declaration....146
25.9.Deutsch..........................................146
25.10.USA..............................................147
25.10.1.FCC Registration Information..........147
25.10.2.Repair Information......................147
25.10.3.FCC Rules Part 15 - Computing Devices
.......................................................148
25.10.4.GPRS Modem.............................148
25.11.Canada..........................................149
25.11.1.Industry Canada Information..........149
25.11.2.GPRS Modem.............................149
25.11.3.Industry Canada Regulatory Compliance
Information for Class B Equipment.............150
26.European Union Waste Electrical and Electronic
Equipment (WEEE) Statement..........................151
26.1.UK Users.........................................151
26.2.European Users (outside the UK).............151
26.3.Manufacturer/Responsible Party.............151

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1 . In tro d u c tio n
1.1. The Range
The ip.buffer is designed to collect and store information from such devices as telephone
PBXs – for CDR/SMDR collection, for alarm and traffic management, and to allow pass-
through access for moves and changes.
The product range includes three main devices:
ip-4 = 128Mbyte memory with 4 serial ports
ip-1 = 32Mbyte memory with 1 serial port
The ip-4 device includes internal temperature monitoring, built in global or GPRS modem,
plus the SEbus expansion connector. They also have an option for 48VDC power (see
Section 22). They are both built inside a metal box that can be rack mounted in a 1U high
bay.
The ip-1 device has an optional global PSTN or GPRS modem and is housed in a plastic
casing with facilities for wall mounting, tie-wrapping, and DIN rail mounting.
All three devices allow battery backup using 3 standard AA NiMH batteries. With fully
charged cells the unit can continue to operate for approximately 2 hours.
1.2. Features
All devices have proprietary Scannex features and advanced facilities:
Collection
oAuto pin detection on the serial ports1
oAuto baud rate and protocol detection on the serial ports
oCollection from serial and TCP/IP enabled devices2
oCollection from devices that perform FTP push
oCollection of UDP data including syslog information, SNMP Traps (with trap
decoding and SNMP get queries on connected devices), and
RADIUS Accounting
oCollection from a web server running Scannex C# or PHP scripts.
oSupport for ASCII, Binary and iSDX data sources
oAutomatic partitioning of NAND flash memory with optional settings for
limiting memory sizes of each channel
Various delivery options including:
oHTTP/HTTPS post to web Cloud Server
1The detection is performed using voltage sensing, so the ip.buffer can detect whether the data
source is DCE or DTE wired even with no data
2Each ip.buffer can collect data from as many TCP/IP devices as there are serial ports. Each
channel can be assigned to either the serial port or a TCP/IP or UDP/IP collection.
Page 1
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1 . In tro d u c tio n
1.1. The Range
The ip.buffer is designed to collect and store information from such devices as telephone
PBXs – for CDR/SMDR collection, for alarm and traffic management, and to allow pass-
through access for moves and changes.
The product range includes three main devices:
ip-4 = 128Mbyte memory with 4 serial ports
ip-1 = 32Mbyte memory with 1 serial port
The ip-4 device includes internal temperature monitoring, built in global or GPRS modem,
plus the SEbus expansion connector. They also have an option for 48VDC power (see
Section 22). They are both built inside a metal box that can be rack mounted in a 1U high
bay.
The ip-1 device has an optional global PSTN or GPRS modem and is housed in a plastic
casing with facilities for wall mounting, tie-wrapping, and DIN rail mounting.
All three devices allow battery backup using 3 standard AA NiMH batteries. With fully
charged cells the unit can continue to operate for approximately 2 hours.
1.2. Features
All devices have proprietary Scannex features and advanced facilities:
Collection
oAuto pin detection on the serial ports1
oAuto baud rate and protocol detection on the serial ports
oCollection from serial and TCP/IP enabled devices2
oCollection from devices that perform FTP push
oCollection of UDP data including syslog information, SNMP Traps (with trap
decoding and SNMP get queries on connected devices), and
RADIUS Accounting
oCollection from a web server running Scannex C# or PHP scripts.
oSupport for ASCII, Binary and iSDX data sources
oAutomatic partitioning of NAND flash memory with optional settings for
limiting memory sizes of each channel
Various delivery options including:
oHTTP/HTTPS post to web Cloud Server
1The detection is performed using voltage sensing, so the ip.buffer can detect whether the data
source is DCE or DTE wired even with no data
2Each ip.buffer can collect data from as many TCP/IP devices as there are serial ports. Each
channel can be assigned to either the serial port or a TCP/IP or UDP/IP collection.
Page 1

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
oFTP/SFTP push
oFTP server
oEmail/SMTP push
oTCP/IP push
oTCP/IP server
oCOM port serial
LAN and management features
oFully web-based setup and status information
o“Reflective Routing” on the LAN to allow easy access from different subnets3
oEmail, HTTP POST, and SNMP alert mechanisms to enable a pro-active
system
oExtremely powerful Lua4scripting engine
oSNTP (Simple Network Time Protocol) time synchronisation with daylight
saving option
oSettings can be quickly replicated across multiple ip.buffers for bulk
installations
oAll changes to the settings occur immediately – no need for reboot5
oFully fail-safe firmware upgrades. The power can fail at any point in the
upgrade process and the ip.buffer will recover with the old version (or the
new version if successfully uploaded).
oSimple SNMP v1/v2c agent to provide inventory information to SNMP clients
oCentralised updates via standard web-server (See section 8.2.16)
oSupports Proxy servers running HTTP, SOCKS 5 and SOCKS 4a protocols.
Security features
oOption to authenticate to one or two RADIUS servers
ohttps (SSL) access for web pages (optional) (See section 8.2.15)
oSSL/TLS link encryption for HTTP post, FTP, email, and TCP connections
(optional) (See section 11)
oSFTP/SSH encryption for SFTP push (See section 11.4)
3In practise it means you do not have to have a gateway address, or the correct gateway,
programmed in the ip.buffer when connecting into it for web services and the like.
4See www.lua.org However, several extensions have been applied to the Lua base.
5Even Lua script changes can occur while the ip.buffer is still running
Page 2
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
oFTP/SFTP push
oFTP server
oEmail/SMTP push
oTCP/IP push
oTCP/IP server
oCOM port serial
LAN and management features
oFully web-based setup and status information
o“Reflective Routing” on the LAN to allow easy access from different subnets3
oEmail, HTTP POST, and SNMP alert mechanisms to enable a pro-active
system
oExtremely powerful Lua4scripting engine
oSNTP (Simple Network Time Protocol) time synchronisation with daylight
saving option
oSettings can be quickly replicated across multiple ip.buffers for bulk
installations
oAll changes to the settings occur immediately – no need for reboot5
oFully fail-safe firmware upgrades. The power can fail at any point in the
upgrade process and the ip.buffer will recover with the old version (or the
new version if successfully uploaded).
oSimple SNMP v1/v2c agent to provide inventory information to SNMP clients
oCentralised updates via standard web-server (See section 8.2.16)
oSupports Proxy servers running HTTP, SOCKS 5 and SOCKS 4a protocols.
Security features
oOption to authenticate to one or two RADIUS servers
ohttps (SSL) access for web pages (optional) (See section 8.2.15)
oSSL/TLS link encryption for HTTP post, FTP, email, and TCP connections
(optional) (See section 11)
oSFTP/SSH encryption for SFTP push (See section 11.4)
3In practise it means you do not have to have a gateway address, or the correct gateway,
programmed in the ip.buffer when connecting into it for web services and the like.
4See www.lua.org However, several extensions have been applied to the Lua base.
5Even Lua script changes can occur while the ip.buffer is still running
Page 2

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.3. Block Diagrams
1.3.1. System Overview
Conceptual view of the ip.buffer (ip.4-128m):
The ip.buffer is “channel based” with each channel allowing separate collection and
delivery methods.
Page 3
Alerts
SNMP Agent
SNMP Trap
Sender
Modem
Manager
Web Server
SNTP Client
(Time Sync)
SMTP Client
(Email)
HTTP Client
(Web post)
RADIUS
Client
Lua Core – configuration, scripts, notifications
System
Health
Monitoring
Log Files
Secret Store
Channel #4
Source StorageLua Script Destination
Pass-
through Protocol
Channel #2
Source StorageLua Script Destination
Pass-
through Protocol
Channel #3
Source StorageLua Script Destination
Pass-
through Protocol
Channel #1
Source StorageLua Script Destination
Pass-
through Protocol
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.3. Block Diagrams
1.3.1. System Overview
Conceptual view of the ip.buffer (ip.4-128m):
The ip.buffer is “channel based” with each channel allowing separate collection and
delivery methods.
Page 3
Alerts
SNMP Agent
SNMP Trap
Sender
Modem
Manager
Web Server
SNTP Client
(Time Sync)
SMTP Client
(Email)
HTTP Client
(Web post)
RADIUS
Client
Lua Core – configuration, scripts, notifications
System
Health
Monitoring
Log Files
Secret Store
Channel #4
Source StorageLua Script Destination
Pass-
through Protocol
Channel #2
Source StorageLua Script Destination
Pass-
through Protocol
Channel #3
Source StorageLua Script Destination
Pass-
through Protocol
Channel #1
Source StorageLua Script Destination
Pass-
through Protocol

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.3.2. Source
The four source collection modules run independently. Each source can collect from a
different source device, and the ip.buffer allows any mix of serial, TCP, UDP or FTP across
the four channels.
Although the ip.buffer is “channel based” with custom Lua scripting it is possible to send
data across to other channels. For example, one physical data source (e.g. COM port) may
contain a mixture of CDR, and Alarms information – custom Lua scripting can split this
information into two channel storage areas.
Page 4
Source x 4
Serial
TCP/IP
Client
Server
FTP Server
UDP/IP
RAW
SNMP Trap
Radius
Accounting
Syslog
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.3.2. Source
The four source collection modules run independently. Each source can collect from a
different source device, and the ip.buffer allows any mix of serial, TCP, UDP or FTP across
the four channels.
Although the ip.buffer is “channel based” with custom Lua scripting it is possible to send
data across to other channels. For example, one physical data source (e.g. COM port) may
contain a mixture of CDR, and Alarms information – custom Lua scripting can split this
information into two channel storage areas.
Page 4
Source x 4
Serial
TCP/IP
Client
Server
FTP Server
UDP/IP
RAW
SNMP Trap
Radius
Accounting
Syslog

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.3.3. Destination
The four destination delivery modules also run independently. Each destination can deliver
using a different method. Or, they can use the same method (e.g. FTP Push) but deliver to
a different central server. Each channel can be configured to use any combination of
LAN/WAN/DSL or Modem interfaces.
Page 5
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.3.3. Destination
The four destination delivery modules also run independently. Each destination can deliver
using a different method. Or, they can use the same method (e.g. FTP Push) but deliver to
a different central server. Each channel can be configured to use any combination of
LAN/WAN/DSL or Modem interfaces.
Page 5

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.4. Firmware
Firmware 2.90 and above is shipped as a single .BLF firmware file6in the form
“IPBx.xx.xxx.blf” where x.xx.xxx is the version number.
If cryptography is not permitted in your region Scannex can ship a special build of the
hardware that cannot run cryptography. The firmware file is identical, but the hardware
will prevent crypto code from running.
The web pages of the ip.buffer indicate whether cryptography is enabled:
•IPBSSLx.xx.xxx indicates that SSL/TLS/SSH cryptography is enabled.
•IPBCFx.xx.xxx indicates that cryptography is disabled.
Scannex have full export approval. See section 25.7
The cryptographic routines cannot be modified or updated by an end user.
6Firmware 2.82 and earlier was shipped in two firmware files – an SSL and a CF version. However,
the ability to load SSL enabled firmware in the field still meant the hardware was “crypto capable”
from an import-restriction viewpoint.
Page 6
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.4. Firmware
Firmware 2.90 and above is shipped as a single .BLF firmware file6in the form
“IPBx.xx.xxx.blf” where x.xx.xxx is the version number.
If cryptography is not permitted in your region Scannex can ship a special build of the
hardware that cannot run cryptography. The firmware file is identical, but the hardware
will prevent crypto code from running.
The web pages of the ip.buffer indicate whether cryptography is enabled:
•IPBSSLx.xx.xxx indicates that SSL/TLS/SSH cryptography is enabled.
•IPBCFx.xx.xxx indicates that cryptography is disabled.
Scannex have full export approval. See section 25.7
The cryptographic routines cannot be modified or updated by an end user.
6Firmware 2.82 and earlier was shipped in two firmware files – an SSL and a CF version. However,
the ability to load SSL enabled firmware in the field still meant the hardware was “crypto capable”
from an import-restriction viewpoint.
Page 6

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
2 . G P R S (C e llu la r ) M o d e m
Some models of the ip.buffer come fitted with a GPRS modem allowing for delivery of data
and remote access over the cellular/mobile network.
They are shipped without a SIM card and without an antenna and so require an appropriate
data-enabled SIM card for the country of installation1and a suitable GPRS antenna prior to
use.
2.1. GPRS Safety Precautions
If the ip.buffer is fitted with a GPRS Radio Module (RF) transmitter the
following operating conditions and restrictions must be observed at all times.
•Be sure the use of this product is allowed in the country and in the environment
required. The use of this product may be dangerous and has to be avoided in the
following areas:
◦Where it can interfere with other electronic devices in environments such as
hospitals, airports, aircrafts, etc.
◦Where there is risk of explosion such as gasoline stations, oil refineries, etc
•It is responsibility of the user to enforce the country regulation and the specific
environment regulation
2.1.1. GPRS Radiation Exposure Statements
Failure to meet these requirements may mean the maximum permissible
exposure (MPE) limit is exceeded!
•This transmitter must not be collocated or operated in conjunction with any other
antenna or transmitter.
•The device is designed for and intended to be used in fixed and mobile
applications.
◦"Fixed" means that the device is physically secured at one location and is not
able to be easily moved to another location. The antenna for a fixed device is
mounted on an outdoor permanent structure with a minimum separation
distance of 2 meters (79 inches)
◦"Mobile" means that the device is designed to be used in other than fixed
locations and generally in such a way that a separation distance of at least 20
cm is maintained between the transmitter's antenna and the body of the user or
nearby persons.
•The antenna gain must not exceed 2 dBi2in mobile applications and 7dBi in Fixed
1SIM 1.8/3V Mini-Subscriber Identity Module (SIM)
2Antenna gain in dB relative to an isotropic radiator
Page 7
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
2 . G P R S (C e llu la r ) M o d e m
Some models of the ip.buffer come fitted with a GPRS modem allowing for delivery of data
and remote access over the cellular/mobile network.
They are shipped without a SIM card and without an antenna and so require an appropriate
data-enabled SIM card for the country of installation1and a suitable GPRS antenna prior to
use.
2.1. GPRS Safety Precautions
If the ip.buffer is fitted with a GPRS Radio Module (RF) transmitter the
following operating conditions and restrictions must be observed at all times.
•Be sure the use of this product is allowed in the country and in the environment
required. The use of this product may be dangerous and has to be avoided in the
following areas:
◦Where it can interfere with other electronic devices in environments such as
hospitals, airports, aircrafts, etc.
◦Where there is risk of explosion such as gasoline stations, oil refineries, etc
•It is responsibility of the user to enforce the country regulation and the specific
environment regulation
2.1.1. GPRS Radiation Exposure Statements
Failure to meet these requirements may mean the maximum permissible
exposure (MPE) limit is exceeded!
•This transmitter must not be collocated or operated in conjunction with any other
antenna or transmitter.
•The device is designed for and intended to be used in fixed and mobile
applications.
◦"Fixed" means that the device is physically secured at one location and is not
able to be easily moved to another location. The antenna for a fixed device is
mounted on an outdoor permanent structure with a minimum separation
distance of 2 meters (79 inches)
◦"Mobile" means that the device is designed to be used in other than fixed
locations and generally in such a way that a separation distance of at least 20
cm is maintained between the transmitter's antenna and the body of the user or
nearby persons.
•The antenna gain must not exceed 2 dBi2in mobile applications and 7dBi in Fixed
1SIM 1.8/3V Mini-Subscriber Identity Module (SIM)
2Antenna gain in dB relative to an isotropic radiator
Page 7

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
2.2. Installing a SIM card
The GPRS module uses a SIM 1.8/3V Mini-Subscriber Identity Module (SIM).
To insert the SIM card proceed as follows:
•Make sure that the ip.buffer is disconnected from the supply voltage and any
batteries are removed.
•The ip.buffer must be opened to insert the SIM card.
◦For an ip1 device the housing is fastened by four screws in the base
◦For an ip2/ip4 device the housing is fastened by 2 screws in the case sides
•The SIM card holder is visible on the GPRS modem motherboard.
•Slide the SIM card under the flap of the SIM card holder, with the gold-coloured
microchip facing down.
◦The SIM card holder has a groove to accept the SIM card.
◦The notched corner of the SIM matches the notch in the card holder.
◦Slide the SIM card into the holder as far as possible.
2.3. Installing the antenna
•Disconnect the ip.buffer from the power supply
•Connect an appropriate fixed or portable (e.g. 'stub') aerial of suitable gain to the
antenna connector SMA socket
◦The SMA socket is situated on the rear of the ip.buffer next to the power
connector.
◦The antenna can be a broadband type covering the 800-1900MHz range of the
module, or one that is specific for the country of operation.
Page 8
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
2.2. Installing a SIM card
The GPRS module uses a SIM 1.8/3V Mini-Subscriber Identity Module (SIM).
To insert the SIM card proceed as follows:
•Make sure that the ip.buffer is disconnected from the supply voltage and any
batteries are removed.
•The ip.buffer must be opened to insert the SIM card.
◦For an ip1 device the housing is fastened by four screws in the base
◦For an ip2/ip4 device the housing is fastened by 2 screws in the case sides
•The SIM card holder is visible on the GPRS modem motherboard.
•Slide the SIM card under the flap of the SIM card holder, with the gold-coloured
microchip facing down.
◦The SIM card holder has a groove to accept the SIM card.
◦The notched corner of the SIM matches the notch in the card holder.
◦Slide the SIM card into the holder as far as possible.
2.3. Installing the antenna
•Disconnect the ip.buffer from the power supply
•Connect an appropriate fixed or portable (e.g. 'stub') aerial of suitable gain to the
antenna connector SMA socket
◦The SMA socket is situated on the rear of the ip.buffer next to the power
connector.
◦The antenna can be a broadband type covering the 800-1900MHz range of the
module, or one that is specific for the country of operation.
Page 8

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
3 . F ittin g B a tte rie s
The ip.buffer can run from 3 x standard AA-size Ni-MH batteries when the mains power
fails (supplied without batteries). With fully charged batteries the ip.buffer should run for
at least 2 hours (although this run time can be limited using the configuration options).1
3.1.1. Battery Precautions
Use only AA sized rechargeable Ni-MH batteries with a
capacity of at least 2000mAH.
Batteries should all be of the same capacity, manufacturer, and type.
RISK OF EXPLOSION IF BATTERIES OF INCORRECT TYPE ARE FITTED.
Never use non-rechargeable batteries.
Do not burn or puncture the batteries. The cells may explode.
Check with local requirements for possible special disposal instructions.
When replacing batteries all batteries should be replaced at the same time.
Remove the batteries from the product if the product will not be used for some
time (several months or more).
Check with local requirements for shipping restrictions before shipping with
batteries fitted. Some authorities strongly recommend shipping without batteries
fitted!
1Batteries not supplied.
Page 9
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
3 . F ittin g B a tte rie s
The ip.buffer can run from 3 x standard AA-size Ni-MH batteries when the mains power
fails (supplied without batteries). With fully charged batteries the ip.buffer should run for
at least 2 hours (although this run time can be limited using the configuration options).1
3.1.1. Battery Precautions
Use only AA sized rechargeable Ni-MH batteries with a
capacity of at least 2000mAH.
Batteries should all be of the same capacity, manufacturer, and type.
RISK OF EXPLOSION IF BATTERIES OF INCORRECT TYPE ARE FITTED.
Never use non-rechargeable batteries.
Do not burn or puncture the batteries. The cells may explode.
Check with local requirements for possible special disposal instructions.
When replacing batteries all batteries should be replaced at the same time.
Remove the batteries from the product if the product will not be used for some
time (several months or more).
Check with local requirements for shipping restrictions before shipping with
batteries fitted. Some authorities strongly recommend shipping without batteries
fitted!
1Batteries not supplied.
Page 9

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
3.1.2. Installing in an ip.1
The battery compartment for the ip.1, which has a plastic case, is accessible beneath the
cover in the lid. Undo the retaining screw and insert the batteries over the ribbon,
observing polarity. The ribbon will help in the battery removal.
Remove the power supply and all other connectors from the unit before
opening the case!
Page 10
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
3.1.2. Installing in an ip.1
The battery compartment for the ip.1, which has a plastic case, is accessible beneath the
cover in the lid. Undo the retaining screw and insert the batteries over the ribbon,
observing polarity. The ribbon will help in the battery removal.
Remove the power supply and all other connectors from the unit before
opening the case!
Page 10

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
3.1.3. Installing in an ip.4
The ip.4 has a metal case. The case has to be opened by removing the screws on either
side, and then sliding the top case section off. Inside, the battery compartment lid is fixed
by one screw. Observe polarity when inserting the batteries. Take care not to damage or
touch the rest of the circuit board.
Remove the power supply and all other connectors from the unit before
opening the case!
Page 11
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
3.1.3. Installing in an ip.4
The ip.4 has a metal case. The case has to be opened by removing the screws on either
side, and then sliding the top case section off. Inside, the battery compartment lid is fixed
by one screw. Observe polarity when inserting the batteries. Take care not to damage or
touch the rest of the circuit board.
Remove the power supply and all other connectors from the unit before
opening the case!
Page 11

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
4 . P h y s ic a l M o u n tin g
4.1. ip.1 – plastic box
4.1.1. DIN Rail Mounting
Fits “top-hat” DIN rail, as per DIN E0022, 35x15 or 35x7.5mm.
To fit:
●Hang the ip.buffer onto the top lip of the DIN rail
●Push the bottom of the box down onto the rail until it clicks into place
To remove:
●Push box up and unhook from the top of the DIN rail lip.
4.1.2. Wall mounting
●Mount two flat-headed screws (not supplied) that are 90mm apart in a vertical line
○The stem should be no more than 4.5mm diameter
○The screw head should be between 6mm and 11mm
●Leave the heads proud of the wall
○The head should be no more than 6mm from the wall
●Slot the box onto the screws.
4.2. ip.4 – metal case
19” rack mounting:
●Screw the two ears onto the sides of the casing, using the 6 screws provided.
●Mount in a 1U rack position.
Page 12
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
4 . P h y s ic a l M o u n tin g
4.1. ip.1 – plastic box
4.1.1. DIN Rail Mounting
Fits “top-hat” DIN rail, as per DIN E0022, 35x15 or 35x7.5mm.
To fit:
●Hang the ip.buffer onto the top lip of the DIN rail
●Push the bottom of the box down onto the rail until it clicks into place
To remove:
●Push box up and unhook from the top of the DIN rail lip.
4.1.2. Wall mounting
●Mount two flat-headed screws (not supplied) that are 90mm apart in a vertical line
○The stem should be no more than 4.5mm diameter
○The screw head should be between 6mm and 11mm
●Leave the heads proud of the wall
○The head should be no more than 6mm from the wall
●Slot the box onto the screws.
4.2. ip.4 – metal case
19” rack mounting:
●Screw the two ears onto the sides of the casing, using the 6 screws provided.
●Mount in a 1U rack position.
Page 12

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
5 . In s ta lla tio n
5.1. Connections
Plug the plug-top Power Supply Unit (PSU) into an AC 100-240V mains outlet
situated near the unit.
Connect the cord from the PSU into the DC power input of the ip.buffer.
oThe green Status (S) LED should flash once a second, indicating the unit is
functioning correctly.
oThe power cable can be retained:
!Slot the cable into the recessed cable-restraint on the underside of
the ip.1, or,
!Use a cable-tie on the ip.4
Connect the ip.buffer to a network hub or switch. Make sure you connect the
“LAN” port, and not the “SEbus” connector!
oThe yellow Link (L) LED should light and flash in time with network traffic.
If required, and fitted in the ip.buffer, connect the modem port to the
telephone with an appropriate adapter if needed.
Page 13
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
5 . In s ta lla tio n
5.1. Connections
Plug the plug-top Power Supply Unit (PSU) into an AC 100-240V mains outlet
situated near the unit.
Connect the cord from the PSU into the DC power input of the ip.buffer.
oThe green Status (S) LED should flash once a second, indicating the unit is
functioning correctly.
oThe power cable can be retained:
!Slot the cable into the recessed cable-restraint on the underside of
the ip.1, or,
!Use a cable-tie on the ip.4
Connect the ip.buffer to a network hub or switch. Make sure you connect the
“LAN” port, and not the “SEbus” connector!
oThe yellow Link (L) LED should light and flash in time with network traffic.
If required, and fitted in the ip.buffer, connect the modem port to the
telephone with an appropriate adapter if needed.
Page 13

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
5.2. Getting Started
On your PC, run the SEDiscover1application, and press the F5 key (or the
magnifying glass). This will locate all ip.buffers (and NetBuffers) on the LAN.
oSEDiscover will only show ip.buffers that are physically connected to the
same network segment. It will not show ip.buffers that are separated by a
router/gateway/firewall.
oIf you have problems locating the ip.buffer:
!Disconnect the PC from the main network.
!Connect a CAT5 cable directly between the PC and the ip.buffer.
!Make sure the PC has a fixed IP address (e.g. 192.168.0.111)
!Retry SEDiscover
The default IP address of the ip.buffer will be 192.168.0.235
You can highlight the entry in SEDiscover and press the world icon to go straight
to the web page of the ip.buffer2
You should see the ip.buffer’s main status page.
The default username and password for the Setup & Tools pages are:
oUsername = “admin”
oPassword = “secret”
You can change the ip.buffer's IP address, subnet & gateway details:
oThrough the web-page at any time (assuming you have the correct username
and password!)
oWith SEDiscover if the ip.buffer has been powered up for less than 5
minutes3.
1You can download this from our website at www.scannex.com. SEDiscover uses a more acceptable
protocol when compared with the older NBDiscover application.
2Even if the ip.buffer is on a different subnet, the SEDiscover tool (v2.2+) inserts a temporary static
route into your PC’s routing table. The added routes are removed when you close SEDiscover. In
addition, if you have multiple ip.buffers with the same IP address, the SEDiscover tool inserts a
static ARP entry to allow direct access. Note that these facilities are not readily available when not
using the SEDiscover tool.
3If the ip.buffer has been powered up for more than 5 minutes, you can hold the front recessed
button for 2 seconds only to enable updating through SEDiscover.
Page 14
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
5.2. Getting Started
On your PC, run the SEDiscover1application, and press the F5 key (or the
magnifying glass). This will locate all ip.buffers (and NetBuffers) on the LAN.
oSEDiscover will only show ip.buffers that are physically connected to the
same network segment. It will not show ip.buffers that are separated by a
router/gateway/firewall.
oIf you have problems locating the ip.buffer:
!Disconnect the PC from the main network.
!Connect a CAT5 cable directly between the PC and the ip.buffer.
!Make sure the PC has a fixed IP address (e.g. 192.168.0.111)
!Retry SEDiscover
The default IP address of the ip.buffer will be 192.168.0.235
You can highlight the entry in SEDiscover and press the world icon to go straight
to the web page of the ip.buffer2
You should see the ip.buffer’s main status page.
The default username and password for the Setup & Tools pages are:
oUsername = “admin”
oPassword = “secret”
You can change the ip.buffer's IP address, subnet & gateway details:
oThrough the web-page at any time (assuming you have the correct username
and password!)
oWith SEDiscover if the ip.buffer has been powered up for less than 5
minutes3.
1You can download this from our website at www.scannex.com. SEDiscover uses a more acceptable
protocol when compared with the older NBDiscover application.
2Even if the ip.buffer is on a different subnet, the SEDiscover tool (v2.2+) inserts a temporary static
route into your PC’s routing table. The added routes are removed when you close SEDiscover. In
addition, if you have multiple ip.buffers with the same IP address, the SEDiscover tool inserts a
static ARP entry to allow direct access. Note that these facilities are not readily available when not
using the SEDiscover tool.
3If the ip.buffer has been powered up for more than 5 minutes, you can hold the front recessed
button for 2 seconds only to enable updating through SEDiscover.
Page 14

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
5.3. Forgotten passwords & factory defaults
If the password is forgotten, there is one sure way to gain access to the ip.buffer:
Once you have performed this action there is no way to recover any of the
data or settings. Everything will be completely and utterly erased! Use this as
a last resort only.
With the ip.buffer running its normal firmware...
Press and hold the button on the front of the ip.buffer for more than 10 seconds
oThe red LED will blink every second until you have held it down for 10
seconds
oThen the red LED will blink rapidly
Now release the button
The ip.buffer will erase all parameters and data and reboot.
When the reboot process completes the ip.buffer will be reset to factory
settings.
There is a programmable option which allows for a 5-minute access after
power-up – without requiring a username and password. If this option is not
enabled (it is off by default) then you have to resort to the wipe-everything
method above.
Page 15
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
5.3. Forgotten passwords & factory defaults
If the password is forgotten, there is one sure way to gain access to the ip.buffer:
Once you have performed this action there is no way to recover any of the
data or settings. Everything will be completely and utterly erased! Use this as
a last resort only.
With the ip.buffer running its normal firmware...
Press and hold the button on the front of the ip.buffer for more than 10 seconds
oThe red LED will blink every second until you have held it down for 10
seconds
oThen the red LED will blink rapidly
Now release the button
The ip.buffer will erase all parameters and data and reboot.
When the reboot process completes the ip.buffer will be reset to factory
settings.
There is a programmable option which allows for a 5-minute access after
power-up – without requiring a username and password. If this option is not
enabled (it is off by default) then you have to resort to the wipe-everything
method above.
Page 15

Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
6 . F ro n t P a n e l
The LEDs on the front panel show the following information:
●Channel 1..4
Off Source not connected
On Source Connected
Flashing Data Arriving
●L: LAN
Off No Ethernet Connection
On Ethernet Connected
Flashing Ethernet Activity
●M: Modem
Off Modem Off-Line
Slow Flash Answering or Dialling
Fast Flash Negotiating PPP1
On Modem On-Line
●S: Status Blinks every second to indicate the ip.buffer is
functioning normally
●E: Error Blinks when booting. Normally off
Firmware 2.76 and above: The “S” green LED will blink at least every second
to show the ip.buffer is running. When any data arrives, the “S” green LED
will blink more rapidly2.
Firmware 2.75 and below: All LEDs (except the “L” LAN) will flash on, then off
every 8 seconds to show that the operating system kernel is functioning. The
LAN LED is controlled directly by the Ethernet circuitry.
1When the ip.buffer boots up, the Modem LED will flash if there is a modem present. If no modem
is installed, the Modem LED will not light (except for the regular 8 second flash)
2This 'quieter' LED display was introduced because there was some confusion over the 8-second
flash and end users thought the red “E” LED was indicating something!
Page 16
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
6 . F ro n t P a n e l
The LEDs on the front panel show the following information:
●Channel 1..4
Off Source not connected
On Source Connected
Flashing Data Arriving
●L: LAN
Off No Ethernet Connection
On Ethernet Connected
Flashing Ethernet Activity
●M: Modem
Off Modem Off-Line
Slow Flash Answering or Dialling
Fast Flash Negotiating PPP1
On Modem On-Line
●S: Status Blinks every second to indicate the ip.buffer is
functioning normally
●E: Error Blinks when booting. Normally off
Firmware 2.76 and above: The “S” green LED will blink at least every second
to show the ip.buffer is running. When any data arrives, the “S” green LED
will blink more rapidly2.
Firmware 2.75 and below: All LEDs (except the “L” LAN) will flash on, then off
every 8 seconds to show that the operating system kernel is functioning. The
LAN LED is controlled directly by the Ethernet circuitry.
1When the ip.buffer boots up, the Modem LED will flash if there is a modem present. If no modem
is installed, the Modem LED will not light (except for the regular 8 second flash)
2This 'quieter' LED display was introduced because there was some confusion over the 8-second
flash and end users thought the red “E” LED was indicating something!
Page 16