3com APX30M/4 User Manual

NBX Installation Guide

NBX V3000

SuperStack 3 NBX

NBX 100

Release 5.0

Part Number 900-0214-01

April 2005

http://www.3com.com/

3Com Corporation 350 Campus Drive Marlborough, MA 01752-3064

Copyright © 1998–2005, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation.

3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change.

3Com Corporation provides this documentation without warranty, term, or condition of any kind, either implied or expressed, including, but not limited to, the implied warranties, terms, or conditions of merchantability, satisfactory quality, and fitness for a particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.

If there is any software on removable media described in this documentation, it is furnished under a license agreement included with the product as a separate document, in the hardcopy documentation, or on the removable media in a directory file named LICENSE.TXT or !LICENSE.TXT. If you are unable to locate a copy, please contact 3Com and a copy will be provided to you.

UNITED STATES GOVERNMENT LEGEND

If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following:

All technical data and computer software are commercial in nature and developed solely at private expense. Software is delivered as “Commercial Computer Software” as defined in DFARS 252.227-7014 (June 1995) or as a “commercial item” as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in 3Com’s standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this guide.

_______________________________________________________________________

PATENT INFORMATION

NBX Telephones 3C10281PE, 3C10226PE, 3C10228IRPE, and 3C10248PE are covered by one or more of the following U.S. patents and other patent applications pending:

5,994,998; 6,140,911; 6,329,906; 6,496,105; 6,535,983; 6,483,203; 6,449,348; 6,212,195

_______________________________________________________________________

TRADEMARKS

Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries. 3Com, NBX, the 3Com logo, and SuperStack are registered trademarks of 3Com Corporation. NBX NetSet and pcXset are trademarks of 3Com Corporation.

Adobe is a trademark and Adobe Acrobat is a registered trademark of Adobe Systems Incorporated. InstallShield is a registered trademark of InstallShield Software Corporation. Internet Explorer, Microsoft, Windows, Windows 2000, and Windows NT are registered trademarks of Microsoft Corporation. Netscape and Netscape Navigator are registered trademarks of Netscape Communication Corporation in the United States and other countries. All other company and product names may be trademarks of the respective companies with which they are associated.

_______________________________________________________________________

TECHNOLOGY ACKNOWLEDGEMENTS

_______________________________________________________________________

RSA Data Security, Inc. MD5 Message-Digest Algorithm

License to copy and use this software is granted provided that it is identified as the “RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing this software or this function.

License is also granted to make and use derivative works provided that such works are identified as “derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing the derived work.

RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided “as is” without express or implied warranty of any kind.

These notices must be retained in any copies of any part of this documentation and/or software.

_____________________________________________________________________

libtar 2.1.11

Developed by:

Campus Information Technologies and Educational Services, University of Illinois at Urbana-Champaign

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal with the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

■Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimers.

■Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimers in the documentation and/or other materials provided with the distribution.

■Neither the names of Campus Information Technologies and Educational Services, University of Illinois at Urbana-Champaign, nor the names of its contributors may be used to endorse or promote products derived from this Software without specific prior written permission.

THE SOFTWARE IS PROVIDED “AS IS,” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE SOFTWARE.

_____________________________________________________________________

OpenBSD: basename.c,v 1.4 1999/05/30 17:10:30 espie Exp

OpenBSD: dirname.c,v 1.4 1999/05/30 17:10:30 espie Exp

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3.The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

_____________________________________________________________________

OpenBSD: fnmatch.c,v 1.6 1998/03/19 00:29:59 millert Exp

This code is derived from software contributed to Berkeley by Guido van Rossum.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3.All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes software developed by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

_____________________________________________________________________

gethostname.c: minimal substitute for missing gethostname() function

created 2000-Mar-02 jmk

requires SVR4 uname() and -lc

by Jim Knoble <jmknoble@pobox.com>

This software is provided “as is,” without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the author(s) be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software.

_____________________________________________________________________

glob.c

This code is derived from software contributed to Berkeley by Guido van Rossum.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3.All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes software developed by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

_____________________________________________________________________

OpenBSD: strdup.c,v 1.3 1997/08/20 04:18:52 millert Exp

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3.All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes software developed by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

_____________________________________________________________________

OpenBSD: strlcat.c,v 1.5 2001/01/13 16:17:24 millert Exp

OpenBSD: strlcpy.c,v 1.4 1999/05/01 18:56:41 millert Exp

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3.The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

_____________________________________________________________________

strmode.c

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3.All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes software developed by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

_____________________________________________________________________

OpenBSD: strsep.c,v 1.3 1997/08/20 04:28:14 millert Exp

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1.Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3.All advertising materials mentioning features or use of this software must display the following acknowledgement:

This product includes software developed by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

_____________________________________________________________________

zlib.h — Interface of the “zlib” general-purpose compression library, version 1.1.4, March 11th, 2002

This software is provided “as-is”, without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1.The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2.Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

—Jean-loup Gailly jloup@gzip.org

—Mark Adler madler@alumni.caltech.edu

_____________________________________________________________________

imapproxy

Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Carnegie Mellon University not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Carnegie Mellon University makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA, OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE, OR OTHER TORTUOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

_____________________________________________________________________

imap daemon

Program: IMAP4rev1 server

Author: Mark Crispin

Networks and Distributed Computing

Computing & Communications, Administration Building, AG-44

University of Washington

Seattle, WA 98195

Internet: MRC@CAC.Washington.EDU

Date: 5 November 1990

Last Edited: 6 January 1997

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both the above copyright notice and this permission notice appear in supporting documentation, and that the name of the University of Washington not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. This software is made available “as is”, and THE UNIVERSITY OF WASHINGTON DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, WITH REGARD TO THIS SOFTWARE, INCLUDING WITHOUT LIMITATION ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND IN NO EVENT SHALL THE UNIVERSITY OF WASHINGTON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, TORT (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

_____________________________________________________________________

imapclient

Author: Mark Crispin

Networks and Distributed Computing

Computing & Communications, Administration Building, AG-44,

University of Washington

Seattle, WA 98195

Internet: MRC@CAC.Washington.EDU

Date: 22 November 1989

Last Edited: 9 January 1998

name of the University of Washington not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. This software is made available “as is”, and THE UNIVERSITY OF WASHINGTON DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, WITH REGARD TO THIS SOFTWARE, INCLUDING WITHOUT LIMITATION ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND IN NO EVENT SHALL THE UNIVERSITY OF WASHINGTON BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, TORT (INCLUDING NEGLIGENCE) OR STRICT LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

_____________________________________________________________________

IMAP\imapproxy\amigados.c, IMAP\imapproxy\amigpk.c, and IMAP\imapproxy\amigaunpk.c

Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Mike W. Meyer not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Mike W. Meyer makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.

MIKE W. MEYER DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL MIKE W. MEYER BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA, OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE, OR OTHER TORTUOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

CONTENTS

ABOUT THIS GUIDE

	How to Use This Guide			17
	Conventions	18
	International Terminology			18
	Your Comments on the Technical Documentation						19

1 INTRODUCTION
	NBX IP Telephony Platforms				21
	NBX V3000	21
	SuperStack 3 NBX V5000				24
	NBX 100	27
	SuperStack 3 NBX V5000 Gateway Chassis						29
	NBX Cards and Devices			32
	Analog Line Card		32
	T1 Digital Line Card			33
	E1 Digital Line Card			36
	BRI-ST Digital Line Card				39
	10BASE-T Uplink Card			40
	Analog Terminal Card			41
	Analog Terminal Adapters				42
	3Com Telephones		44
	Legacy Link Devices			45
	Third-party Devices and Applications					45
	Optional Software		46
	NBX Licensing	47
	Individual Device Limits				48
	Licensed Device Limits			48
	How the System Limits Interact 48
	Table of Maximum Device Counts					49
	Device Licenses		52
	Group Device Licenses			53

	Dynamic License Assignment				54
	Upgrading Device Licenses from R4.X to R5.0 56
	Rebooting from R5.X to R4.X				57

2 INSTALLING SYSTEM HARDWARE COMPONENTS
	Introduction 60
	International Feature Support			60
	Power Fail Transfer	60
	Analog Terminal Connectors				60
	Language Support	60
	Installation Requirements		61
	Electrical Requirements		61
	Environmental Requirements				61
	Physical Requirements		62
	Local Telephone Service		62
	Installation Questions	63
	Who Should Install the NBX System?					63
	Does the Telephone Company Need to Be Involved?							63
	Is Any Additional Equipment Required?						63
	What External Devices Can Connect to an NBX System? 64
	What Effect Does an NBX System Have on a LAN?							64
	Before You Begin Installation			66
	Required and Recommended Tools and Equipment							66
	Important Safety Information			67
	Lithium Battery Safety		70
	Consignes Importantes de Sécurité				70
	Batterie au lithium	72
	Wichtige Sicherheitsinformationen				72
	Lithiumbatterie 73
	Unpacking and Examining the Components						74
	Installing the NBX System Hardware 74
	Recording MAC Addresses			74
	Optionally Upgrading NBX Memory					75
	Mounting an NBX 100 Chassis				75
	Installing the SuperStack 3 NBX System						78
	Mounting the NBX Gateway Chassis					79
	Installing a Second Disk for Disk Mirroring						79

	Powering Your NBX System			80
	Configuring NBX System Networking					80
	Establishing IP Connectivity			80
	Modifying Default IP Settings				80
	Configuring the NBX System IP Address						84
	Establishing LAN Connections				84
	Test Connectivity	85
	Connecting Cards and Devices			86
	Connecting Analog Line Cards				86
	Connecting Digital Line Cards				87
	Connecting Analog Terminal Cards					87
	Connecting an Analog Terminal Adapter						88
	Selecting Regional Software and Components							90
	Installing Regional Software and Components							91
	Using Auto Discover for Initial System Configuration								92
	Initial System Configuration			93
	Disabling the Auto Discover Feature					96
	NBX System Operating Modes				96
	Reassigning Extensions and Setting Line Card Port Options 97
	Connecting Telephone Lines			99
	Adding External Hardware		99
	Connecting a Music-on-Hold (MOH) Input Device								99
	Connecting a Paging Amplifier				99
	Configuring Routing Devices			100

3 TELEPHONES AND ATTENDANT CONSOLES
	Adding Telephones	103
	Auto Discover Telephones			103
	Manually Configure Telephones				106
	Connecting Power to the Telephone					107
	Connecting the Telephone to the LAN						109
	3Com Cordless Telephones			113
	3Com Entry Telephones		114
	Verifying Telephone Installation				116
	Adding a 3Com Attendant Console				116
	Connecting Power to the Attendant Console							116

Using a Powered Ethernet Cable to Power an Attendant Console 117

	Connecting the Attendant Console to the Network						118
	Using Auto Discover for an Attendant Console					119
	Associating an Attendant Console with a Specific Telephone							121
	Verifying Extension Assignments on an Attendant Console							121
	Attendant Console Labels	122
	Adding a Remote Telephone	122
4
4	ANALOG LINES
	Auto Discover Analog Line Cards		123
	Inserting an Analog Line Card	124
	Verifying an Analog Line Card	124
	Using the NBX NetSet Utility		124
	Using Status Lights 125
5
5	ANALOG DEVICES
	Adding an Analog Terminal Card		128
	Inserting an Analog Terminal Card		128
	Verifying Analog Terminal Card Ports			130
	Using the NBX NetSet Utility		130
	Adding an Analog Terminal Adapter (ATA)				131
	Connecting the Analog Terminal Adapter				131
	Verifying an Analog Terminal Adapter or the ATA Port						132

6 BRI-ST DIGITAL LINE CARD
	Adding a BRI-ST Digital Line Card		136
	Preparing the NBX System for BRI Cards				136
	Ordering DID, CLIP, and MSN Services for BRI					136
	Enabling the Auto Discover Feature			137
	Inserting the BRI-ST Digital Line Card				137
	Verifying a BRI-ST Digital Line Card		138
	Using the NBX NetSet Utility		138

7 E1 ISDN PRI DIGITAL LINE CARD
	Adding an E1 Digital Line Card	140
	Preparing the NBX System for E1 Cards				140

	Ordering DID, CLIP, and MSN Services for E1						140
	Enabling the Auto Discover Feature for Digital Line Cards 141
	Inserting the E1 Digital Line Card				141
	Verifying an E1 Digital Line Card			142
	Using the NBX NetSet Utility			142
	Using the Status Lights		143

8 T1 DIGITAL LINE CARD
	Adding a T1 Digital Line Card			146
	Preparing the NBX System for a T1 Card					146
	Ordering DID (Direct Inward Dialing) Services for T1							146
	Enabling Auto Discover for Digital Line Cards						147
	Inserting the T1 Digital Line Card				147
	Verifying the T1 Digital Line Card				148
	Using the NBX NetSet Utility			148
	Using the Status Lights		149

9 CONFIGURING IP TELEPHONY
	IP Telephony Overview	152
	Implementing IP	152
	Standard IP Configuration			152
	IP On-the-Fly Configuration			154
	Providing the NCP IP Address to Devices					154
	Configuring IP Telephony		155
	Selecting the Operating Mode				155
	Configuring IP On-the-Fly 156
	Configuring the DHCP Server 157
	Manually Configuring Telephone IP Settings						157
	Automatically Configuring Telephone IP Settings							159
	Configuring Analog Line Card Ports 159
	Configuring T1, E1, and BRI Channels					160
	Low-bandwidth Telephony			161
	Broadband Telephony		163

10 TROUBLESHOOTING
	System-level Troubleshooting			166

	Connecting a Computer to an NCP					169
	Servicing the Network Call Processor Battery							170
	Getting Service and Support			170
A
A	SPECIFICATIONS
	Government Approvals		172
	Safety 172
	EMC Emissions	172
	EMC Immunity	172
	European Community CE Notice					172
	Other Approvals	172
	NBX V3000 Call Processor			173
	SuperStack 3 NBX V5000 Call Processor						173
	SuperStack 3 NBX V5000 Chassis					174
	NBX 100 Call Processor		174
	NBX 100 6-Slot Chassis		175
	NBX Analog Line Cards		175
	NBX Analog Terminal Cards			177
	NBX Analog Terminal Adapter (ATA)					177
	NBX BRI-ST Digital Line Card			178
	NBX E1 and T1 Digital Line Cards					178
	NBX Hub Card 178
	NBX Uplink Card	179
	3Com 3102 Business Telephone				179
	3Com 2102 and 2102-IR Business Telephones							180
	3Com 1102 Business Telephone				180
	3Com 3101 and 3101SP Basic Telephones						181
	3Com 2101 Basic Telephone			182
	3Com 3105 Attendant Console				182
	3Com 1105 Attendant Console				183
	3Com 3106C Cordless Telephone					183
	3Com 3107C Cordless Telephone					184
	3Com 3103 Manager’s Telephone					185
	3Com 3100 Entry Telephone			185
B
B	CIRCUIT PROVISIONING
	Caller ID Choices for Analog Lines					187

T1	Prerequisites	188
T1	Recommendations		188
ISDN PRI Prerequisites			189
	CSU Required	189
ISDN PRI Recommendations				189
ISDN BRI Prerequisites			190
ISDN BRI Recommendations				191

C GUIDELINES FOR CONNECTING REMOTE AUDIO DEVICES

Maximum Transfer Unit (MTU) 193
Communication Latency Requirements			194
Large Packet Latency	194
Small Packet Latency	194
Bandwidth Requirements	195
Layer 2 Mulaw (G.711) Audio (Normal Setting) 195
Layer 3 Mulaw (G.711) Audio		195
Layer 2 ADPCM Audio (Reduced Bandwidth Setting)				195
Layer 3 ADPCM Audio (Reduced Bandwidth Setting)				195
Notes on Bandwidth Requirements			195
Installing Fax Machines with ATAs		196

D OBTAINING SUPPORT FOR YOUR 3COM PRODUCTS

Solve Problems Online 197

Purchase Extended Warranty and Professional Services 198

Access Software Downloads 198

Telephone Technical Support and Repair 199

INDEX

FCC CLASS A VERIFICATION STATEMENT

INDUSTRY CANADA NOTICE

3COM END USER SOFTWARE LICENSE AGREEMENT TERMS AND CONDITIONS AND LIMITED WARRANTY

ABOUT THIS GUIDE

This guide provides information and instructions for installing an NBX® Networked Telephony Solution. It is intended for authorized installation technicians.

■ If the information in the release notes differs from the information in this guide, follow the instructions in the release notes.

■ Release notes and all product technical manuals are available on the NBX Resource Pack CD and the 3Com web site.

■ For information about monitoring, changing, and maintaining the

	system, see the NBX Administrator’s Guide on the NBX Resource Pack
	CD or in the NBX NetSet interface.
	■ For information about using the telephones on an NBX system, see
	the NBX Telephone Guide and the NBX Feature Codes Guide on the
	NBX Resource Pack CD or in the NBX NetSet interface.

How to Use	Table 1 shows where to look for specific information in this guide.
This Guide	Table 1 Overview of the Guide
	Table 1 Overview of the Guide

	Description	Chapter

	An overview of the installation process and hardware components	Chapter 1

	How to install hardware components and telephone lines	Chapter 2

	How to install Telephones and Attendant Consoles	Chapter 3

	How to install Analog Line Cards	Chapter 4

	How to install Analog Terminal Cards and	Chapter 5
	Analog Terminal Adapters

	How to install BRI-ST Digital Line Cards	Chapter 6

	How to install E1 ISDN PRI Digital Line Cards	Chapter 7

	How to install T1 Digital Line Cards	Chapter 8

	How to configure IP telephony	Chapter 9

18 ABOUT THIS GUIDE

Table 1 Overview of the Guide (continued)

Description	Chapter

Troubleshooting information	Chapter 10

System and component specifications	Appendix A

ISDN BRI, ISDN PRI, and T1 circuit provisioning information	Appendix B

Guidelines for connecting remote audio devices	Appendix C

Obtaining Support for Your 3Com Product	Appendix D

References to all topics in this book	Index

FCC, Industry Canada, Software License Agreement, and	the last pages in
Warranty information	this book

Conventions	Table 2 lists conventions that are used throughout this guide.
	Table 2	Notice Icons

	Icon	Notice Type	Description

		Information note	Information that describes important features
			or instructions

		Caution	Information that alerts you to potential loss of data
			or potential damage to an application, device,
			system, or network

		Warning	Information that alerts you to potential personal
			injury


International	Table 3 lists the United States and international equivalents of some of the
Terminology	specialized terms used in the NBX documentation.
	Table 3	International Terminology

	Term used in U.S.		Term used outside the U.S.

	Toll restrictions		Call barring

	Pound key (#)		Hash key (#)

	CO (central office)		Telephone Exchange

	Toll-free		Free-phone

	Analog Line Card		Analog Trunk Line Interface Module

Your Comments on the Technical Documentation 19

Your Comments on Your suggestions are important to us. They help us to make the NBX the Technical documentation more useful to you.

Documentation

Send comments about this guide or any of the 3Com NBX documentation and Help systems to:

Voice_TechComm_Comments@3com.com

Include the following information with your comments:

■Document title

■Document part number (found on the front page)

■Page number

■Your name and organization (optional)

Example:

NBX Installation Guide

Part Number 900-0212-01 Rev AA

Page 20

As always, address all questions regarding the NBX hardware and software to your 3Com NBX Voice-Authorized Partner.

20 ABOUT THIS GUIDE

INTRODUCTION

This chapter describes the NBX® system in these topics:

■NBX IP Telephony Platforms

■NBX Cards and Devices

■Optional Software

■NBX Licensing

■Device Licenses

For information about how to prepare your site for installation, see the

NBX System Planning Guide on the NBX Resource Pack CD or on the 3Com web site.

For information about configuring the Dial Plan and maintaining your NBX system, see the NBX Administrator’s Guide in the NBX NetSet™ utility, on the NBX Resource Pack CD, or on the 3Com web site.

NBX IP Telephony The NBX IP Telephony Solution includes these hardware platforms:

Platforms

■The NBX V3000

■The SuperStack® 3 NBX V5000

■The NBX 100

NBX V3000 The NBX V3000 (Figure 1) houses the Network Call Processor (NCP), which manages call traffic, voice mail, and the Automated Attendant, the system disk drive and power supply, and front panel connections for network and external device connectivity. See “NBX Licensing” on

page 47 for more information on the total number of supported devices.

22 CHAPTER 1: INTRODUCTION

NBX V3000 Connectors and LEDs

Table 4 describes the front panel connectors and status lights shown in

Figure 1.

Figure 1 NBX V3000 Connectors and LEDs

1	2	3	4	5	6	7	8	9	10	11	12	13

Table 4 NBX V3000 Connectors and LEDs

1Status Lights

DISK ACT. — Disk activity. Flashing indicates disk activity. PWR/STATUS:

■Blinking green — System is booting.

■Blinking red — System boot has failed.

■Solid green — System is operational.

2	Ext. Alert	Reserved for future use.

3	Paging	RJ-11 connector for a 600 Ohm analog paging amplifier.

4	MOH	Mini-jack (mono or stereo) that accepts Music-On-Hold audio
		(maximum 2V peak to peak) from the line output of a CD player,
		tape player, or other music source.

5	Console	DB-9 connector that provides an RS-232 (DCE) TTY terminal
		connection for access to system CLI commands and status
		messages. For more information, see “Connecting a Computer to
		an NCP” on page 169.

6	Status	Status lights S1 (bottom) and S2 (top) show boot status:
	Lights	■ S2 flashing green — System boot sequence has started.
		■ S2 flashing green — System boot sequence has started.
		■ S2 green — Disk drive initialization is complete.
		■ S1 and S2 flash alternately — A file system check (FSCK) is
		running due to previous improper system shutdown. Do not
		turn off the system until you have run the system shutdown
		operation through the NBX NetSet utility
		(Operations > Reboot/Shutdown).

7	USB	Reserved for future use.

NBX IP Telephony Platforms

Table 4 NBX V3000 Connectors and LEDs (continued)

8	Ethernet	The RJ-45 Ethernet port connects the system to the network. The
		connection can operate at 10Mbit or 100Mbit.
		LNK/SPEED:
		■ Yellow — 10Mbit link
		■ Green — 100Mbit link
		■ Off — No link
		ACT:
		■ Flashing Green — Activity on port
		■ Off — No activity

9	ATA (FXS)	Analog Terminal Adapter port, RJ-11 FSX (Foreign Exchange
		Station) connector for connecting an analog device, such as an
		analog telephone or a fax machine. The LED associated with the
		port indicates the state of the port:
		Initialization:
		■ Fast steady blink — Waiting for software download.
		■ Solid on — Software has been downloaded. The flash memory
		on the board is being loaded.
		■ Slow, non symmetric blinking pattern — Waiting for
		completion of the binding process to the NCP.
		Operation:
		■ Off for 9 to 10 seconds, on briefly — Idle, line is not in use.
		■ On for 9 to 10 seconds, off briefly — A telephone call is
		connected on this port.

10	PFT	Power Fail Transfer port. RJ-11 connector accepts a standard POTS
		(2500-series compatible) telephone. During a power failure, this
		port continues to provide dial tone and telephone service.

11Analog Line Four RJ-11 Foreign Exchange Office (FXO) ports for connecting Ports (FX0) central office telephone lines.

12Status A status light for each FXO port indicates the state of port.

Lights Initialization:

■Fast steady blink — Waiting for software download.

■Solid on — Software has been downloaded. The flash memory on the board is being loaded.

■Slow, non-symmetric blinking pattern — Waiting for the completion of the binding process to the NCP.

Operation:

■Off for 9 to 10 seconds, on briefly — Idle.

■On for 9 to 10 seconds, off briefly — Call is connected.

24 CHAPTER 1: INTRODUCTION

Table 4 NBX V3000 Connectors and LEDs (continued)

13 Front Label Shows the system ID number, which you must use when ordering licensed features. A label on the back of the NBX V3000 shows the system ID, the system serial number, and the analog port MAC address.

SuperStack 3 The SuperStack 3 NBX V5000 (Figure 2) houses the Network Call NBX V5000 Processor (NCP), which manages call traffic, voice mail, and the

Automated Attendant; the system disk drive and power supply; and front panel connections for network and external device connectivity. The SuperStack 3 NBX is also available with redundant power supplies. You can also add a second “mirrored” disk drive. Disk mirroring is described in the NBX Administrator’s Guide in the NBX NetSet™ utility, on the NBX Resource Pack CD, and on the 3Com web site. See “NBX Licensing” on page 47 for more information on the total number of supported devices.

SuperStack 3 NBX V5000 Connectors and LEDs

Figure 2 shows the front panel of the SuperStack 3 NBX and Table 5 describes each front panel connector and status light.

Figure 2 SuperStack 3 NBX V5000

1	2	3	4	5	6	7	8		9		10 11 12 13			14	15
																NBX Call Processor
								L	1	1		V		External
								N 0		0		o		External		P
KYBD	Mouse	Video		USB	Com 1	Com 2	Ethernet 1	K		0	Ethernet 2	l	MOH Paging	Alert	S W
															1	R
								1	1	1					1
								2	2	2					2	3
																SuperStackR 3 NBX

Table 5 SuperStack 3 NBX V5000 Connectors and LEDs

1	KYBD	Reserved for future use.

2	Mouse	Reserved for future use.

3	Video	Reserved for future use.

NBX IP Telephony Platforms

Table 5 SuperStack 3 NBX V5000 Connectors and LEDs (continued)

4	Disk Drive	Shipped with the primary drive installed on the left.
	Tray

5	USB	Reserved for future use.

6	COM1	DB-9 connector that provides an RS-232 (DCE) TTY terminal
		connection for access to system CLI commands and status
		messages. For information on how to connect to the
		NBX system using the Console connector, see “Connecting a
		Computer to an NCP” on page 169.

7	COM2	Reserved for future use.

8	Ethernet 1	RJ-45 connector to connect the SuperStack 3 NBX to the
		network. This port can operate at 10 Mbps and 100 Mbps; it
		automatically senses the speed of your LAN.

9	Network	Three LEDs for each of the 2 Ethernet ports indicate port
	Status LEDs	status:
		■ LNK — Solid on indicates link; Off indicates no link.
		■ 10 — Blinking indicates network activity at 10 MB;
		Solid on indicates heavy network activity.
		■ 100 — Blinking indicates network activity at 10 MB;
		Solid on indicates heavy network activity.

10	Ethernet 2	A fail-over port that is active only if the Ethernet 1 port
		experiences a link failure. This port can operate at 10 Mbps
		and 100 Mbps; it automatically senses the speed of your LAN.

11	VOL	This adjusting screw controls the volume of Music-On-Hold.

12	MOH	Mini-jack (mono or stereo) that accepts Music-On-Hold audio
		(maximum 2V peak to peak) from the line output of a CD
		player, tape player, or other music source.

13	Paging	This RJ-11 connector provides an audio output or a dry
		contact switch connection for use with a public address
		system.

14	Ext. Alert	Reserved for future use.

15	System Status	S1, S2, S3 and PWR provide a visual indication of system
	LEDs	status. See Table 6, next.

Table 6 SuperStack 3 NBX System Status LEDs

Explanation	S1	S2	S3	PWR

Attempting to boot from disk 0 (zero)	Off	On	Off	On

Attempting to boot from disk 1	Off	Off	On	On

Boot process completed, system initializing	Flashing	N/A	N/A	On

System is running

N/A

26 CHAPTER 1: INTRODUCTION

Explanation	S1	S2	S3	PWR

Flash codes for disk problems:	N/A	Flashing	Flashing	On

■2 flashes: No valid disk (system is halted).

■3 flashes: Two valid disks, but they are not paired (system is halted).

■4 flashes: Configuration problem (system is halted).

■5 flashes: Two disks present, but no mirroring license installed. System is running but the system is not using the second disk.

Using disk 0 (zero) only	N/A	On	Off	On

Using disk 1 only	N/A	Off	On	On

Synchronizing — disk 0 is valid, disk 1 is	N/A	On	Flashing	On
becoming a fully mirrored disk. LED 3 flash
rate indicates progress.
If LED 3 stops normal flashing and
intermittently flashes twice, the mirroring
process has failed.

Synchronizing — disk 1 is valid, disk 0 is	N/A	Flashing	On	On
becoming a fully mirrored disk. LED 2 flash
rate indicates progress.
If LED 2 stops normal flashing and
intermittently flashes twice, the mirroring
process has failed.

LED 2 and LED 3 flash alternately: the two	N/A	Flashing	Flashing	On
disks are resynchronizing

Synchronized	N/A	On	On	On

NBX IP Telephony Platforms

NBX 100 The NBX 100 6-Slot Chassis (Figure 3) houses the Network Call Processor (NCP), which manages call traffic, voice mail, and the Automated Attendant, and the system disk drive, and the power supply. An NBX 100 system can have one or more chassis, but only one NCP. The number depends on how many external telephone lines the system must support, the equipment that you choose for attaching telephones, and the type of network connections you want. The top slot has no access to the backplane. Always cover the top slot with a blank faceplate.

See “NBX Licensing” on page 47 for more information on the total number of supported devices.

Figure 3 NBX 100 Chassis with Network Call Processor and Cards

S	S	S	V	MOH	PAGING EXT. ALERT	10BT UPLINK	COM 1	COM 2
S	S	S	V
1	2	3	O
			L
3C10110D 3Com NBX Call Processor						MDI-X

PWR	1	2	3	4	5	6	7	8
								1	8

3C10370 3Com NBX Uplink Card

						CF	10BT UPLINK
						CF	CONSOLE
						RA
			T1
3C10116C 3Com NBX Digital Line Card						Nominal	MDI-X
						LB	MDI-X
						LB
1	2	3	4
			PFT	1	2	3	4

NBX 100

	115 volts	115
230	230 volts

3C10114C 3Com NBX Analog Line Card

1 2 3 4

PFT

3C10114C 3Com NBX Analog Line Card

1 2 3 4

PFT

3C10114C 3Com NBX Analog Line Card

The NBX 100 6-Slot Chassis can be used as an expansion chassis for an NBX system. You must install an NBX Uplink Card or Hub Card to connect the chassis to the network. The top slot of an NBX 100 6-Slot Chassis has no access to the backplane. If you are using an NBX 100 6-Slot chassis as an expansion chassis, always cover the top slot with a blank faceplate.

28 CHAPTER 1: INTRODUCTION

NBX 100 Network Call Processor Connectors and LEDs

The NBX 100 NCP has two models. The current model, 3C1011D, does not include a BNC connector. Figure 4 shows the two models of the NBX 100 NCP and Table 7 describes each front panel connector and status light.

Figure 4 NBX 100 Call Processor 3C10110D (top) and 3C10110C (bottom)

	1		2	3	4	5	6	7	8	9
S	S	S	V	MOH	PAGING	EXT. ALERT		10BT UPLINK	COM 1	COM 2
			V
			O
1	2	3	O
1	2	3	L
			L
3C10110D 3Com NBX Call Processor								MDI
								MDI
S	S	S	V	MOH	PAGING	EXT. ALERT		10BT UPLINK	COM 1	COM 2
S	S	S	O
1	2	3	O
			L

3C10110C 3Com NBX Call Processor	BNC 10B2	MDI-X
Table 7 NBX 100 NCP Connectors and LEDs
1	Status LEDs S1 and S2 — Indicate operating system status.

■S1 and S2 both flashing (approximately 2 flashes per second). The hardware is initializing.

■S1 on and S2 off. The operating system has started successfully.

■S1 and S2 are both on. The operating system software has not started successfully.

■S1 and S2 flash in an alternating pattern. A file system check is in progress, possibly due to an improper shutdown. The boot process will take longer than normal.

S3 — Indicates the status of Music-On-Hold (MOH).

■S3 flashing (approximately 2 flashes per second). The MOH processor is initializing. If this flashing continues for more than 2 minutes, the processor has not started successfully.

■S3 solid on. The MOH processor has started successfully.

■S3 flashing slowly (approximately 1 second on and 1 second off). The MOH processor has started successfully, but no music source is connected.

2	VOL	This adjusting screw controls the volume of Music-On-Hold.

3	MOH	Mini-jack (mono or stereo) that accepts Music-On-Hold audio
		(maximum 2V peak to peak) from the line output of a CD
		player, tape player, or other music source.

NBX IP Telephony Platforms

Table 7 NBX 100 NCP Connectors and LEDs (continued)

4	Paging	This RJ-11 connector provides an audio output or a dry
		contact switch connection for use with a public address
		system.

5	Ext. Alert	Reserved for future use.

6	BNC 10B2	BNC connector to connect to an external Ethernet switch or
	(3C1011C only)	hub.
	and LINK LED	The older 3C10110C Network Call Processor (no longer
		available) includes a BNC connector and an RJ-45 connector
		for uplink connections. The BNC and RJ-45 connectors are
		alternative connections for a single port. They cannot be used
		simultaneously.

If you use the 10BT Uplink connector, be sure to program the switch or router on the other end for 10 MB operation.

710BT Uplink RJ-45 connector provides means to connect to an external and LINK LED Ethernet switch or hub. Be sure to program the switch or

router on the other end for 10 MB operation.

8	COM1	DB-9 connector that provides an RS-232 (DCE) TTY terminal
		connection for access to system CLI commands and status
		messages. For information on how to connect to the NCP
		using the Console connector, see “Connecting a Computer to
		an NCP” on page 169.

9	COM2	Reserved for future use.

SuperStack 3 NBX The SuperStack 3 NBX V5000 Gateway Chassis Figure 5, contains four V5000 Gateway card slots so that you can connect optional interface cards to your system.

Chassis As shipped from the factory, the top three have faceplates and the fourth is left open. For installation instructions, see Chapter 2.

The 3C10200B is an updated version of the 3C10200, which is no longer available. The update removed one port (3 in Figure 5) and improved the switchover performance of the Ethernet ports so that both ports have connectivity prior to switchover.

30 CHAPTER 1: INTRODUCTION

Figure 5 SuperStack 3 NBX Chassis 3C10200 (top) and 3C10200B (bottom)

1	2 3
	10M Shared
	10/100M Switched
	10M Link
	100M Link
	10/100M Switched
	10M Link
	100M Link
	3C10200 NBX Gateway Chassis

10/100M Switched

10M Link

100M Link

10/100M Switched

10M Link

100M Link

3C10200B NBX V5000 Chassis

Table 8 SuperStack 3 NBX V5000 Gateway Chassis Connectors

1	4-slot chassis	Removable faceplates installed.
2	10/100 Mbps switched Ethernet	Two redundant uplink ports. Use the
	connection	upper port to connect to the LAN. The
		lower port is normally inactive and
		becomes active only if the upper port
		experiences a link failure. On the
		3C10200B, both ports show a positive
		link status even though only one port
		at a time is active.
3	10 Mbps shared Ethernet	One port (3C10200 only)
	connection

You must use straight-through Ethernet cable connections; you cannot use MDI/MDIX connections.

+ 182 hidden pages

3com APX30M/4 User Manual

ABOUT THIS GUIDE

Conventions

International Terminology

Your Comments on the Technical Documentation 19

INTRODUCTION

■NBX IP Telephony Platforms

Figure 2 SuperStack 3 NBX V5000