Business VoIP Phone System

System | System Alarms

Simple Network Management Protocol (SNMP) allows SNMP clients and servers to exchange information. SNMP clients are built into devices such as network routers, server PC's, etc. SNMP servers are typically PC application which receive and/or request SNMP information.

The IP Office SNMP client allows the IP Office system to respond to SNMP polling and to send alarm information to SNMP servers. In order for an SNMP server application to interact with an IP Office, the IP Office MIB files, provided on the IP Office Admin CD, must be compiled into the SNMP server's applications database. For full details refer to the IP Office Installation Manual.

The IP Office can also send alarms to an SMTP email server. This allows users to receive alarms without needing to configure an SNMP server. Using SMTP requires details of a valid SMTP email account user name and password and server address.

Alarm traps can be created specifying which alarms to include and where to send the alarms. Up to 2 traps can be configured for the sending of alarms to an SNMP server. Up to 3 traps can be configured for the sending of alarms to SMTP email.

Enabling System Alarms

1. Select  System.

2. Select the System Alarms tab.

3. Tick SNMP Enabled.

4. If planning to use SNMP, complete the information in the SNMP Info section by entering the SNMP port and community details to match those expected by your SNMP server. Details of installing the MIB files required for SNMP are included in the IP Office Installation manual.

5. If planning to use SMTP, complete the information in the SMTP Server Configuration section. Enter the details of the SMTP email server and the email account.

6. Click OK.

Editing Alarm Traps (Events)
The Events section of the System Alarms tab displays the currently created alarm traps. It shows the trap destination and the types of alarms that will trigger the trap. Up to 2 traps can be configured for the sending of alarms to an SNMP server. Up to 3 traps can be configured for the sending of alarms to SMTP email.

1. Select the Alarms sub-tab.

2. Use the Add, Remove and Edit controls to alter the traps.

3. Click Add or select the alarm to alter and then click Edit.

4. For a new alarm, set the Destination to either Trap (SNMP) or Email (SMTP). Note that once a trap has been saved it cannot be changed to the other sending mode.

5. The remaining details will indicate the required destination information and allow selection of the alarm events to include.

6. When completed, click OK.

7. Click OK again.

Configuration Sub-Tab Settings

• SNMP Info

  Action	Operator Rights View			Mergeable			System		Level
  	Administrator	Manager	Operator				SOE		2.1
  View				Pre-3.2	3.2		IP403		3.0DT
  Edit							IP406 V1		3.0
  New							IP406 V2		3.1
  Delete							IP412		3.2

• • SNMP Enabled: Default = Off
    Enables support for SNMP alarms and traps by the IP Office control unit. This option must be selected even if only SMTP is being used to email the alarms.

  • SNMP Port: Default = 161, Range = 0 to 65534.
    The port on which the IP Office system listens for SNMP polling.

  • Community (Read-only): Default = public
    The SNMP community name to which the IP Office belongs.

  • Device ID
    This is a text field used to add additional information to alarms.  

  • Contact
    This is a text field used to add additional information to alarms.  

  • Location
    This is a text field used to add additional information to alarms.

• SMTP Server Configuration

  Action	Operator Rights View			Mergeable			System		Level
  	Administrator	Manager	Operator				SOE		2.1
  View				Pre-3.2	3.2		IP403		3.0DT
  Edit							IP406 V1		3.0
  New							IP406 V2		3.1
  Delete							IP412		3.2

• • IP Address: Default = 0.0.0.0
    This field sets the IP address of the SMTP server being used to forward SNMP alarms sent by email.

  • Port: Default = 25, Range = 0 to 65534.
    This field set the destination port on the SMTP server.

  • Email From Address: Default = Blank
    This field set the sender address to be used with mailed alarms. Depending of the authentication requirements of the SMTP server this may need to be a valid email address hosted by that server. Otherwise the SMTP email server may need to be configured to support SMTP relay.

  • Server Requires Authentication: Default = On
    This field should be selected if the SMTP server being used requires authentication to allow the sending of emails. When selected, the User Name and Password fields become available.

  • • User Name: Default = Blank
      This field sets the user name to be used for SMTP server authentication.

    • Password: Default = Blank
      This field sets the password to be used for SMTP server authentication.

    • Use Challenge Response Authentication (CRAM-MD5): Default = Off.
      This field should be selected if the SMTP uses CRAM-MD5.

Alarms Sub-Tab Settings

• Events
  This section is used to show and edit the alarm traps. .

• • Destination
    The options are Trap (SNMP) or Email (SMTP).  

  • • If Trap is selected, the details required are:

      SOE	IP403	IP406 V1	IP406 V2	IP412		2.1	3.0DT	3.0	3.1	3.2

    • • IP Address: Default = 0.0.0.0
        The IP address of the SNMP server to which trap information is sent.

      • Port: Default = 162, Range = 0 to 65534.
        The SNMP transmit port

      • Community: Default = Blank
        The SNMP community for the transmitted traps. Must be matched by the receiving SNMP server.

    • If Email is selected, the details required are:

      SOE	IP403	IP406 V1	IP406 V2	IP412		2.1	3.0DT	3.0	3.1	3.2

    • • Email:
        The destination email address.

  • Events: Default = None
    Sets which types of IP Office events should be collected and sent by the trap:

  • • Entity
      Report on link up/down changes between the IP Office control unit and various entities.  For IP Office 3.2 various sub-entities can be selected.

    • • Application

      • Compact Flash

      • Expansion Module

      • Trunk

      • VCM

    • Generic
      Report on cold starts, warm starts and SNMP authentication failure.

    • License
      Report failure to connect with the License Key Server.

    • Phone Change
      Send a trap whenever a phone is removed or moved.

    • Loopback
      Only displays for systems with a United States locale. Ticking this field enables the sending of CSU loopback events, which may then be monitored by an SNMP manager application.