Polycom 7000 manual Conference Room Dialog, 486BUSY Here

System Reports

Field	Description
userDataA	The value from the User pass-through to CDR field of the user associated
	with the endpoint (see Edit User Dialog). For point-to-point calls, this is the
	user associated with the endpoint that started this call.
userDataB	For VMR calls, the value from the Conference room pass-through to CDR
	field of the conference room (VMR) to which the call connected (see Edit
	Conference Room Dialog).
	For point-to-point calls, the value from the User pass-through to CDR field of
	the user associated with the endpoint that received this call.
userDataC	For VMR calls, the dial-out participant pass-through value provided via the
	API, if any.
	For point-to-point calls, not currently used.
userDataD	Not currently used.
userDataE	Not currently used.
failureSignalingCode	For SIP calls, the SIP code and reason, separated by a colon, that the call
	was disconnected. For instance:
	486:BUSY HERE
origModel	The hardware model of the originating device, if available from the device’s
	registration or other signaling.
origVersion	The software version of the originating device, if available from the device’s
	registration or other signaling.
destModel	The hardware model of the destination device, if available from the device’s
	registration or other signaling.
destVersion	The software version of the destination device, if available from the device’s
	registration or other signaling.
displays	For an immersive telepresence room, the number of screens the room has.
	For a Polycom SIP ITP call, this is determined from the system name; for a
	Polycom or Cisco TIP call, it’s the x-cisco-multiple-screenparameter
	value.
	For all other calls, the value is 1.
	Note: If a Polycom ITP room doesn’t follow the ITP naming convention (see
	Naming ITP Systems Properly for Recognition by the Polycom RealPresence
	DMA System), this field may contain inaccurate information.
minVideoResolution	The minimum vertical resolution used on the video channel, followed by the
	minimum frame rate while at the minimum resolution, as reported by the MCU
	at the end of the call. For instance:
	480p15
	Zero (0) if the call was audio only.
	Available only for AVC calls using SIP or TIP signaling to a version 8.1 or
	newer hardware-based Polycom MCU with MPMx cards. Otherwise, blank.

Polycom, Inc. 414