Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 2

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca7f046c, userName='null'}
JIRAIDAUTHSBX-102037
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c856ed5c670156fe1faa5a0001, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86573c09001659ee32b100026, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a0c86c120d6f016c46267a38002b, userName='null'}

Type: MINOR

Object ID1.3.6.1.4.1.2879.2.10.1.1.1.0.91

Description

This alarm indicates that the specified IPv4 end-point belonging to the SIP Peer is available to receive calls.

Repetition

None

Event Codes

EVENT_PATHCHK_FQDN_PEER_IP_ENDPOINT_UP

Instance Fields

  • sonusAlarmNodeID
  • sonusAlarmLevel
  • sonusAlarmSequenceId
  • sonusAlarmTime
  • sonusAlarmDescription
  • sonusPingPeerIpAddress
  • sonusPingPeerPortNum
  • sonusPingPeerFqdn
  • sonusPingPeerZoneId
  • sonusPingPeerZoneName
  • sonusPingPeerName

Action

None

Impact

The specified IP end-point is no longer bypassed while routing SIP calls.

Clearing

Automatic; sonusSbxPathCheckFqdnPeerIpEndpointDownNotification2


Pagebreak