AOR-IP Supervisor Configuration
The AOR-IP-SUP comes pre-configured, for standard subnet used in the AOR-IP-SUP, but will need the proper configuration loaded and the scripts modified for the number of stations, in order to monitor the correct Network Devices.
Accessing the Device
- Using any browser login into the device at http://192.168.1.254/setup . (figure 1.)
Default username: admin
Default password: webrelay
Figure 1. AOR-IP-SUP login
Importing Correct Configuration
- Click on System to expand the menu, and then Backup/Restore . (figure 2.)
Figure 2. Backup/Restore
- Download the appropriate configuration file for the AOR-IP-CU being installed. These are linked at the bottom of the document.
- Once the correct configuration file is downloaded, click the Browse button and locate the file that was just downloaded, then click OK.
- Click the Import button. The status will be shown in the lower left corner.
Once the upload has finished, drag the serial number for the X-12S module found on the left under EXP Modules Found on Bus , to the Right hand side, to update the configuration with the paired X-12S module. (figure 3.) Note that the Serial number on the left side will be different from the example, and match the module that is connected.
Figure 3. Drag Serial number from left side to right side to update configuration file
- Click on Control/Logic to expand the menu, then click on Scripts (figure 4.) There are 4 scripts with the IP range divided among them for a given size AOR-IP-CU. The scripts will need to be edited if the system being installed does not have the maximum number of stations installed. If the system has the maximum number of stations, you may skip to step XXXX.
Figure 4. Scripts
- Determine how many call stations the system will have, and what the final IP address will be. Using the final octet (192.168.1.XXX) determine which script the final IP address will be in. If the final IP address is the last IP in a particular script click on the edit link for the next script. If the final IP is in the range of a script, but not the last IP in the script, then click on that edit link next to the scrip containing the final IP. For example, on an AOR-IP-40-CU, the scripts are in groups of 10, so scriptA has the range 1-10, or 192.168.1.10. So if the final IP is 10 editing would start with scriptB, if it is 2-9 editing would start with scriptA. For the example the final IP will be 192.168.1.29 on an AOR-IP-CU-40. Editing will start with scriptC (figure 5).
Figure 5. scriptC iptable
- As shown in Figure 5, the ipTable contains 10 IP address 220.127.116.11-30. With the ip address of the last device being installed, 192.168.1.29, the entry for 192.168.1.30 needs to be commented out. To do so click on the begging of the line containing the iP address 192.168.1.30 and insert two dashes (--) as shown on line 30 in figure 6, for this example.
Figure 6. Comment out line 30
- Click the Update button to save.
- For this example we will also need to edit scriptD to comment all the station IP addresses that are not being used but not commenting the command Unit and Master station IP addresses. The count for the position in the table will also need to be updated. In this case changing 11 and 12 to 1 and 2 as they will be the only entries in the table for sriptD, as shown in figure 7.
Figure 7. scriptD all station IP addresses commented out
- If an additional master station or other IP device needs to be monitored it can be added to any of the scripts using the same format as other entries in the ipTable and continuing the count, for example if there is a second master station being installed, the line to be added would be "ipTable = "192.168.1.201" where 192.168.1.201 is the IP address being assigned to the second master station. When adding multiple additional devices it is best to spread them out across the scripts to help keep the processing time similar for each script and keep the total time to test all devices as short as possible.
When done with any changes to this script click on
Update to save the changes to the script. when all changes to the scripts have been completed click the
Commit Changes link that is found in the upper right to permanently save all changes to the device.
Click on the link below to down load the configuration file that is needed, then extract the file before importing to the AOR-IP-SUP.
IP Supervisor (AOR-IP-SUP) Installation
It is recommended that any load (device to be controlled) not be connected to the X12S module until after the X-600M has been configured and tested. By doing this, wiring and configuration mistakes will not cause the load device to turn on ...
AOR-IP Command Unit (CU) Configuration
This document covers the basic configuration needed for any of the AOR-IP Command units. (AOR-IP-40-CU, AOR-IP-80-CU, AOR-IP-120-CU, AOR-IP-160-CU) General Information The AOR-IP command units ship pre-configured for up to 160 call station, one ...
AOR-IP Auxiliary Master Station
Configuring the Auxiliary Master Station The Auxiliary Master station comes configured to support up to 160 call stations and configured to import the names of the call stations from the Command Unit. The IP address, sip credentials and number of ...
AOR-IP Command Unit Installation
This document covers the physical installation of the following AOR-IP Command Unit models: AOR-IP-40-CU AOR-IP-80-CU AOR-IP-120-CU AOR-IP-160-CU Fasteners The AOR-IP Command units can be surface mounted or flush mounted, as the particular ...
AOR-IP Auxiliary Command Unit (ACU) Installation
This document covers the physical installation of the following AOR-IP Auxiliary Command Unit models: AOR-IP-40-ACU AOR-IP-80-ACU AOR-IP-120-ACU AOR-IP-160-ACU Fasteners The AOR-IP Command units can be surface mounted or flush mounted, as the ...