Polycom 7000 Video Game Sound System User Manual


 
System Management and Maintenance
Polycom, Inc. 373
Alert 5001
<Model> ITP system attempting to register with ID <H.323 ID or SIP URI> is improperly
configured.
A device that identifies itself as an ITP (Immersive Telepresence) system has registered with the Call Server,
but the H.323 ID or SIP URI of the device doesn't specify its endpoint number or the number of endpoints
in the ITP system, as it should.
The H.323 ID or SIP URI must be updated on the endpoints of the ITP system. See Naming ITP Systems
Properly for Recognition by the Polycom RealPresence DMA System.
See also:
Alerts
Alert 5002
One or more endpoints are sending too much <signaling_type> signaling traffic. They
have been temporarily blacklisted and may have been quarantined.
At least one device, in violation of protocol standards, is sending too much of the specified type of signaling
traffic (H.323 or SIP) to the RealPresence DMA system.
If there are many such ill-behaved devices, it could affect the RealPresence DMA system’s ability to provide
service, so the system temporarily blacklists any such device (ignoring all signaling from it until it stops
sending messages more frequently than the specification permits). If the device is or was registered, it’s also
quarantined, and it remains so until manually removed from quarantine.
Click the link to go to the Network > Endpoints page, where you can search for endpoints with
Registration status of Quarantined or Quarantined (Inactive).
See also:
Alerts
Alert 5003
The <device model> device identified by [<device identifier>] is no longer registered to the
call server.
The specified device has unregistered or its registration has expired. This informational alert appears only
if it’s been enabled for this endpoint or MCU (see Edit Device Dialog, Edit Devices Dialog, or Edit MCU
Dialog). This alert is automatically cleared after two minutes.
Click the link to go to the Endpoints page.
See also:
Alerts
Alert 5004
<sigtype> call from <originator> to <dial string> was dropped due to routing loop.
As the system tried to route the H.323 or SIP call from its source to the destination, a dialing loop in the site
topology was detected, and the call was dropped.