Go to Section 2.2. : Section 2.4 Contents
The following features of the Big Bro will require to access the set of privileged commands:
Associated buttons remain grayed until these commands are enabled When you hit this menu item an input box will show prompting for the enabling password, which is one that has been setup at the gateway (nothing to do with the Brig Bro configuration). If the password is accepted, the menu item will be checked and the grayed buttons will turn black, meaning that they are ready to be used. Even though the GW_Relay's telnet session has access to theses privileged commands, only the GW_Monitor that supplied the password will show buttons in black. Actually only one monitor can have the privileges at the time. A second attempt from a second monitor may cause all the privileges to be canceled. A Requery, will also revoke privileges.
Also, the DS0 Group information, from this moment on, will show complete on all the monitors. The command that reads the DS0 group configuration is privileged, without this access, the DS0 Group info will only be known for those channels that have had a call since the GW_Relay have started.
To disable the privileged command, toggle the check mark on the menu item by hitting it again (the buttons will go back to gray).
Sometimes events happen so fast that is difficult to catch up with them, also sometimes things happen that you want somebody else to see at a later time. GW_Monitor displays in a graphical way the contents of the status messages packets from the GW_Relay. If this messages could be save and then read, it will look as if the same thing is actually happening.
When you
hit on this menu item, all the messages will be saved into the a
file together with the time (in milliseconds) since
the beginning of the recording at which the message occurred. The moment you hit
the command, it will display a check mark and a label saying 'Recording'
in red will start blinking. To stop recording, hit the command again, the process
will stop and the check mark will disappear and so the blinking label. This file
can then be sent elsewhere to be played back (see Play
Log File), GW_Monitor will display the same as when
recorded.
The default filename is Monitor.Log, and the default path is the same as that of GW_Monitor.exe. It is a text file that can be read and interpreted directly once you get familiar with the GW_Monitor Protocol. The Default may be change with the LOG_FILE statement in the GW_Mon.ini (See 2.6.1).
Will stop reading from the TCP socket and start reading events from the Log File at the specified moment and behave as if it was received in an IP socket packet. The command will be displayed as “checked” during playback; you may stop playing by hitting the command again.
Taking
advantage of the every day more popular e-mail feature in pagers and cellular
phones, starting with OmniMonitor V3.00, a new Watchdog concept was introduced
into the OmniBox system, Now, any instance of OmniMonitor can be a Watchdog
that, by using the underlying Internet Mail installation, can page a list of
recipients.. Sending, not only a numeric message like in the original Watchdog,
but the whole alarm message.
The
email pages can be enabled/disabled by checking/un-checking the Enable Pager
menu item. When
you enable the email paging service, you will be prompted for the recipient list
with and input box. There you can enter the recipient list separated by
semicolons, the same way you do with any email message. Any previously entered
list will be shown as default
Once enabled the e-mail paging system you may enter additional addresses or edit the existing ones with this item.
This is not really an option but it is here to test the options related to paging, it is just handy to have it here. Hitting this item, will send a request to the GW_relay to send back a #2 alarm, so that you can test if the email pages and sounds are properly generated.
For the system to be useful, it must provide a means of filtering the messages to produce a sound or to be e-mailed.
For a general description of the Big Bro Alarm system check follow this link.
Type |
Description |
|
0 |
|
|
1 |
|
|
2 |
|
|
3 |
Average gap over max specified |
|
4 |
|
|
5 |
Average Latency over max specified |
|
6 |
|
|
8 |
|
|
10 |
|
|
12 |
|
|
14 |
GW_Rrelay not responding |
|
100 |
The
system allowed to mask more than one page types by specifying its numbers in an ‘*’
separated string like:
*1*6*12*
This
new system allows for even further control. If you select an identifying
sub-string within an alarm message that you choose not to receive as a page even
if the type is not masked by number. You may enter it as a page string mask. You
may enter any number of String masks separated by semicolons. Example:
Peer ID 58418;Peer ID 58412
Page type 8 is not masked, yet, a 8 an alarm involving peer 58418 like:
10/21/03 02:30 PM ---#1-Low completion rate (10%) for Peer ID 58418
will be
masked The masking system is case sensitive and spaces are regarded as valid
characters.
You
may also select an identifying sub string within an alarm message that you choose
to receive as a page even if the type is masked by number. Syntax is the same as
with the Page String Mask. Example:
Exception;20%
For example, even though Alarms 1 and 12 are masked, alarm messages containing the word ‘Exception’ or Completion rate alarm messages containing the figure 20% will make it to a page.
There are special sounds associated to alarms ( like rescue or police car) and also there are when a chat message is received (sounds like a ring). This sounds may be enabled/disabled from the by checking/un-checking this menu item. These sounds are subject to the same string masks pages are, this way you may ban from sounding those alarms message containing specified sub strings. Also, you may prefer to ban the whole type 3 and allow sounds only for those alarm messages containing specified sub strings.
The Chat Feature (See 2.2.6) is a very handy feature that allows you to communicate with connected monitors. Sometimes though, this feature can is intensively used by Big Brothers chatting about issues you couldn't care less for. Still, you get ring sounds on every new message and the chat window poping up on top of the text you writing or the form you are filling, becoming a real nuisance. It is then when you may opt to Disable Chat. You may even, disable it by default by hitting the "Make ini File with current settings" menu item (See below Section 2.3.9)
The problem with disabling the chat is that you won't be warned of messages that you might do care to read.
Group colors allow get important status information at a glance (See 2.1.1). Not always what you want to get at a glance is the same, consither the following scenarios:
The most frequent answer favors the Peer ID's, that is why by default colors are assigned according to them, but if you happen to need colors assigned to DS0 groups you can check on menu item 2.3.8.1.2 or Options/Group Colors/For/DS0 Groups. The color change takes effect immediately. A word of warning, DS0 information is collected as calls go into each channel or all the channels at once when the privileged commands are enabled. If a relay has been recently restarted if might still not have the DSO group information for every channel. If you don't know and have the password, we suggest that you enable the privileged commands once, this way you make sure it is up to date.
Colors are generally useful, some even find it "Cool", but there are those that don't like them or that suffer from Daltonism and find to many colors confusing. Whatever the case, if you don't want colors you, can remove them by checking on this item.
Since colors are assigned by an algorithm, it can happen that your specific Peer ID (or DS0 group) values don't render the right color differentiation. When you hit this menu item, the following form pops up
.
A new set of colors takes effect every time the scroll changes. When you are satisfied with the color set, you may hit menu item 2.3.9 Make ini File with Current Settings (See below) to make it the default color set.
All these options may be included into the ini file to make them the default settings. When you hit this menu item, the ini file is updated so as to include all the right statements to make this happen. A Notepad with the current content of the ini file will open for you to see or do further changes.
Go to Section 2.2. : Section 2.4 Contents