Table of Contents
Advertisement
3) Connectivity Issues
During the initial installation of the Branch Office Extender, a number of issues may result in the Branch
unit being unable to establish a telephony connection back to the central site PBX. The purpose of this
section is to help in the prognosis of the possible causes of a connection failure.
•
Ensure that the System Checks as first described in this troubleshooting section have been
understood and met.
•
Ensure that the wiring requirements have been met between the PBX and the PBXgateway II, and
between the telephone and Remote Branch EXTender. This can be confirmed by checking the port
status within the MI and also the port LED status (See page 145)
MI Path:
Remote-Configuration-Connect-Type-RVP_Direct - Ensure that appropriate bandwidth
allocation has been reserved for the voice compression and for the number of telephones intended to
be used. For information on configuring some of the more frequently user CSU/DSU's and Terminal
Adapters, consult the service and support section of www.mck.com. If your device is not listed and
documented, contact the vendor of your terminating equipment for assistance. The sync rate and the
intended protocol to be used (RS530, V35) must also match between the terminating equipment and
Branch Extender configuration.
MI Path:
Remote-Configuration-Connect-Type-RVP_IP - Ensure that an IP address has been
assigned to the PBXgateway II and IP address assigned to the Remote Branch EXTender or 4000.
An additional IP address is then programmed into the Remote Branch EXTender or 4000 under the
Configuration-Connect-RVP_IP menu, this is the IP address of the PBXgateway II and is used
as the "connect to" address.
For RVP-Direct installations, it is possible to confirm the validity of the wiring and data ports between the
Branch EXTender and a typically used terminating device (CSU/DSU).
•
Configure the Remote CSU/DSU into local loop back and then perform the Test WAN routine. (See
the section Audio Breakup Using RVP_Direct on page 148 for details on how this utility operates). If
the WAN test is successful then this confirms that the wiring between the CSU/DSU and the Remote
Branch is valid and that the ports in use are functioning correctly. If the test fails, check your cabling,
then try the WAN2 port of the Branch and then an alternate port on the terminating device until a
successful test is achieved.
•
Perform the same test locally between the Central site CSU/DSU and the PBXgateway II. Check the
cable and alternate ports until a successful test is achieved.
•
Upon successful completion of the above two tests, try performing a test WAN with no local loopback
enabled. If the test fails then you now know the problem is network related. You may want to try the
CSU/DSU's back to back using a cross over T1 cable (see the section Audio Breakup using
RVP_Direct on page 148 for more details)
The Branch EXTenders will operate equally as well regardless as to which of the WAN ports is assigned
for usage. In the event of establishing a connection using the WAN2 port, ensure the following:
•
WAN1 is disabled
•
WAN2 is enabled,
•
In the MI on the Remote unit, go to Remote-Configuration-Connect-RVP_Direct and set
WAN2 as the Primary WAN.
RVP_IP. Ensure that the correct UDP/TCP ports have been opened up to allow connectivity of your
remote EXTenders through your company firewall. The following UDP/TCP port requirements must be
met:
PBXgateway II System Administrator's Guide
153
Advertisement
Table of Contents
