Chapter A-Disconnection Causes

 

 

 

 

 

 

Table A-1Call Disconnection Causes (Continued)

 

 

 

 

 

 

Disconnection Cause

Description

 

 

 

 

 

 

H323 call closed. Remote sent bad

There was a problem in the capabilities sent by the

 

 

capability

endpoint.

 

 

 

 

 

 

H323 call closed. Local capability wasn't

The endpoint did not accept the capabilities sent by the

 

 

accepted by remote

gatekeeper.

 

 

 

 

 

 

H323 failure

Internal error occurred.

 

 

 

 

 

 

H323 call closed. Remote stop

The endpoint stopped responding.

 

 

responding

 

 

 

 

 

 

 

H323 call closed. Master slave problem

A People + Content cascading failure occurred.

 

 

 

 

 

 

SIP bad name

The conference name is incompatible with SIP

 

 

 

standards.

 

 

 

 

 

 

SIP bad status

A general IP card error occurred.

 

 

 

 

 

 

SIP busy everywhere

The participant's endpoints were contacted successfully,

 

 

 

but the participant is busy and does not wish to take the

 

 

 

call at this time.

 

 

 

 

 

 

SIP busy here

The participant's endpoint was contacted successfully,

 

 

 

but the participant is currently not willing or able to take

 

 

 

additional calls.

 

 

 

 

 

 

SIP capabilities don't match

The remote device capabilities are not compatible with

 

 

 

the conference settings.

 

 

 

 

 

 

SIP card rejected channels

The IP card could not open the media channels.

 

 

 

 

 

 

SIP client error 400

The endpoint sent a SIP Client Error 400 (Bad Request)

 

 

 

response.

 

 

 

The request could not be understood due to malformed

 

 

 

syntax.

 

 

 

 

 

 

SIP client error 402

The endpoint sent a SIP Client Error 402 (Payment

 

 

 

Required) response.

 

 

 

 

 

 

SIP client error 405

The endpoint sent a SIP Client Error 405 (Method Not

 

 

 

Allowed) response.

 

 

 

The method specified in the Request-Line is understood,

 

 

 

but not allowed for the address identified by the

 

 

 

Request-URI.

 

 

 

 

 

 

SIP client error 406

The endpoint sent a SIP Client Error 406 (Not

 

 

 

Acceptable) resources.

 

 

 

The remote endpoint cannot accept the call because it

 

 

 

does not have the necessary responses. The resource

 

 

 

identified by the request is only capable of generating

 

 

 

response entities that have content characteristics not

 

 

 

acceptable according to the Accept header field sent in

 

 

 

the request.

 

 

 

 

 

Polycom, Inc.

A-3

Page 780 Page 782
Page 781
Image 781
Polycom DOC2702A, RMX 1500 manual Disconnection Cause Description
Page 780 Page 782

DOC2702A, RMX 1500 specifications

The Polycom RMX 1500, also known by its model number DOC2702A, is a significant player in the realm of video conferencing technology. Designed to enhance collaboration across various platforms, this versatile solution caters to the communication needs of medium to large enterprises, providing high-quality video, voice, and content sharing experiences.

One of the primary features of the RMX 1500 is its unparalleled scalability. The system supports up to 150 simultaneous video endpoints, allowing organizations to expand their video conferencing capabilities as needed. This flexibility makes it an ideal solution for growing businesses that require robust communication tools. The RMX 1500 can also handle a variety of video resolutions, from standard definition to HD, ensuring that users can enjoy clear and crisp visuals during their meetings.

The Polycom RMX 1500 utilizes advanced technologies such as the Polycom RealPresence technology, which significantly enhances video quality and reliability. This technology incorporates features like Adaptive Bandwidth Management, which optimizes video streams based on available bandwidth, thus ensuring a seamless experience even in less-than-ideal network conditions. This ensures that users can engage in meetings without interruptions or quality degradation, regardless of their location.

Another notable characteristic of the RMX 1500 is its robust interoperability with a wide range of video conferencing systems and protocols. This means that businesses can easily connect with partners, clients, and colleagues using different systems, reducing the barriers to effective communication. The RMX 1500 supports various codecs and standards, including H.323 and SIP, making it a versatile choice for organizations that work with multiple platforms.

Furthermore, the RMX 1500 is equipped with tools for content sharing, allowing participants to share presentations, documents, and other materials during meetings. This promotes interactive discussions and enhances collaboration among team members. In addition, the system features an intuitive user interface, making it easy for users to schedule meetings, manage participants, and control audio and video settings.

The product also places a strong emphasis on security, providing encryption options for video and audio streams to protect sensitive information shared during conferences. This commitment to security is essential for organizations that need to meet compliance standards and safeguard intellectual property.

In summary, the Polycom RMX 1500 (DOC2702A) is a powerful video conferencing solution that combines flexibility, scalability, and high-quality performance. With its advanced technologies, interoperability, content sharing capabilities, and emphasis on security, it serves as an invaluable tool for enhancing communication and collaboration in today’s fast-paced business environment.
Top Page Image Contents