Device Management
Polycom, Inc. 90
Bandwidth Available only after the call has ended. The table at the top lists each throttle
point that the call traverses and shows its:
• Bit rate limit per call (kbps)
• Total capacity (kbps)
• Used bit rate (kbps) in each class of service
• Weight (%)
• Territory
If the throttle point is a subnet, site, or site link, a link takes you to the
corresponding site topology page with the throttle point entity selected.
Below the table, the data used in bandwidth processing is displayed (all bit
rates are kbps):
• Formal maximum bit rate limit — the maximum allowed bit rate considering
the per call bit rates of each throttle point, but not considering total capacity
or current usage
• Available bit rate capacity in each class of service and for the call’s class
• Class of service for the call
• Minimum downspeed bit rate
• Available bit rate limit (%) — the maximum percentage of remaining
bandwidth at a throttle point that will be given to any one call (configurable
on the Call Server Settings page)
• Requested bit rate
• Final bit rate
Call Events Lists each call event in the call and its attributes.
When the system is operating as a SIP proxy server, the list includes all SIP
signaling messages except 100 TRYING.
Hover over an attribute label to see a description. Click Show Message to
see the signaling message. Click Show QoS Data to see detailed quality of
service statistics.
Subscription Events For conference (VMR) calls, lists SUBSCRIBE/NOTIFY events, if any,
associated with this call.
The SIP SUBSCRIBE/NOTIFY conference notification service (as described
in RFCs 3265 and 4575), allows SIP devices (generally, conference
participants) to subscribe to a conference and receive conference rosters and
notifications of conference events. The rosters identify the participants, their
endpoints, and their video streams.
Hover over an attribute label to see a description. Click Show Message to
see the signaling message.
Note: If the system is configured to let devices subscribe to a conference
without being participants in the conference (see Security Settings on
page 50), the call history doesn’t include data for such non-participant
subscriptions. But be aware that a subscription to a conference by a
non-participant consumes a call license.
Tab/Field/Column Description