19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Troubleshooting<br />

Table 9 ICE Environment - <strong>RMX</strong> Active Alarms<br />

Appendix H-Setting the <strong>RMX</strong> for Integration Into Microsoft Environment<br />

Active Alarm Phase Alarm Displayed When Troubleshooting<br />

ICE failure: No<br />

response from the<br />

A/V Edge Server to<br />

the <strong>RMX</strong> Service<br />

Request<br />

ICE failure:<br />

Received Service<br />

message does not<br />

contain the<br />

Credentials.<br />

ICE failure:<br />

A/V Edge server<br />

URI cannot be<br />

resolved<br />

ICE failure: Service<br />

credential denied.<br />

A/V Edge server<br />

credentials rejected<br />

by the OCS.<br />

Service The <strong>RMX</strong> did not receive<br />

a confirmation response<br />

from the A/V Edge Server<br />

to the Service request.<br />

Service The Service message<br />

response does not<br />

contain the Credentials.<br />

Service The <strong>RMX</strong> failed to resolve<br />

The remote address of<br />

the Edge server URI.<br />

Service This alarm indicates that<br />

the OCS does not<br />

configure with the.<br />

Generated by the ICE<br />

stack.<br />

• At the end of the installation and configuration process, to test the solution and the<br />

integration with the OCS, create an ongoing conference with two participants, one dialin<br />

and one dial-out and connect them to the conference.<br />

• If the active Alarm “SIP TLS: Registration server not responding” is displayed, stop and<br />

restart the OCS Pool Service.<br />

• If the communication between the OCS and the <strong>RMX</strong> cannot be established, one of the<br />

possible causes can be that the <strong>RMX</strong> FQDN name is defined differently in the DNS,<br />

OCS and <strong>RMX</strong>. The name must be defined identically in all three devices, and defined<br />

as type A in the DNS. The definition of the <strong>RMX</strong> FQDN name in the DNS can be tested<br />

by pinging it and receiving the <strong>RMX</strong> signaling IP from the DNS in return.<br />

• The communication between the OCS and the <strong>RMX</strong> can be checked in the Logger files:<br />

— SIP 401/407 reject messages indicate that the <strong>RMX</strong> is not configured as Trusted in<br />

the OCS and must be configured accordingly.<br />

— SIP 404 reject indication indicates that the connection to the OCS was established<br />

successfully.<br />

<strong>Polycom</strong>, Inc. H-73

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!