NEC Univerge sv8500 Manual

NEC Univerge sv8500 Manual

Fp85-110 s7
Hide thumbs Also See for Univerge sv8500:
Table of Contents

Advertisement

FP85-110 S7
Peripheral Equipment Description
NWA-041680-001
ISSUE 12.0

Advertisement

Table of Contents
loading

Subscribe to Our Youtube Channel

Summary of Contents for NEC Univerge sv8500

  • Page 1 FP85-110 S7 Peripheral Equipment Description NWA-041680-001 ISSUE 12.0...
  • Page 2 NEC Corporation reserves the right to change the specifications, functions, or features, at any time, without notice. NEC Corporation has prepared this document for use by its employ- ees and customers. The information contained herein is the property of NEC Corporation, and shall not be reproduced without prior written approval from NEC Corporation.
  • Page 3 Incorrect use of the equipment may limit the system performance or cause the system to fail. The telephone system can only be used in NEC-designated countries. If a system-down, malfunction, defect or external factor such as an electrical failure indirectly causes a loss of profit, the company (or affiliates) will not be held responsible.
  • Page 4: Safety Considerations

    It might cause a fire, an electrical shock or a system failure. Be sure to use cables designated by NEC or cables attached to the equipment. If cables are not designated particularly, choose cables with considering safety and transmission performance carefully.
  • Page 5 Be careful when using any peripheral equipment’s Liquid Crystal Display (LCD). If the liquid leaks, it can be harmful to the user and to the system. Before connecting any non-NEC, customer-provided equipment, check with the supplier to ensure that the equipment is compatible. If the supplier cannot confirm the compatibility, do not connect the equipment.
  • Page 6 PRODUCT LIABILITY WARNING Do not place any object on the system or the main power source. If the object falls, it might cause personal injury or damage to the equipment. When removing a plug from an outlet, be sure to grip the plug, not the cord. Gripping the cord to remove the plug could cause a fire or an electrical shock to occur.
  • Page 7 PRODUCT LIABILITY WARNING Observe the following precautions when using any optional batteries: • The system’s emergency back-up battery may be a rechargeable lead battery. Check the emergency battery for an electrical failure. • Battery acid (electrolyte) is extremely harmful to human skin and eyes. If battery acid contacts skin, wash the affected area with soap and water.
  • Page 8 PRODUCT LIABILITY ATTENTION Do not use benzine, thinner or alcohol for cleaning. When removing dust and dirt, put diluted, mild detergent on a cloth and then wring out the cloth. Remove the dust and dirt with the cloth and then wipe the cleaned area with a dry cloth.
  • Page 9 The telephone company may make changes in its technical operations and procedures. When such changes af- fect the compatibility or use of the UNIVERGE SV8500 system, the telephone company is required to give adequate notice of the changes in order for you to maintain uninterrupted service.
  • Page 10 The consumer/purchaser/supplier instructions accompanying this equipment and/or software features must contain the following notice: The software contained in the UNIVERGE SV8500 to allow user access to the network must be upgraded to recognize newly established network area codes and exchange codes as they are placed into service.
  • Page 11 Failure to upgrade the premises systems or peripheral equipment to recognize the new codes as they are estab- lished will restrict the customer and the customer’s employees from gaining access to the network and these codes. DIRECT INWARD DIALING Note: ALLOWING THIS EQUIPMENT TO BE OPERATED IN SUCH A MANNER AS TO NOT PROVIDE FOR PROPER ANSWER SUPERVISION IS A VIOLATION OF PART 68 OF THE FCC RULES.
  • Page 12 This has been identified as a major nationwide problem. 1.10 HEARING AID COMPATIBILITY NEC Multiline Terminals and NEC Single Line Telephones that are provided for this system are hearing aid compatible. The manufacturer of other Single Line Telephones for use with the system must provide notice of hearing aid compatibility to comply with FCC rules that now prohibit the use of non-hearing aid compatible telephones.
  • Page 13 • CAN/CSA C22.2 No. 60950-1-03 – Safety of Information Technology Equipment – Part l: General Re- quirements • UL 60950-1-SAFETY, 1st Edition – Safety of Information Technology Equipment – Part I: General Re- quirements 4. INDUSTRY CANADA REQUIREMENTS Industry Canada has established rules that permit this telephone system to be directly connected to the tele- phone network.
  • Page 14 Industrie Canada. 5. BATTERY DISPOSAL The UNIVERGE SV8500 system includes the batteries listed below. When disposing of these batteries, Chas- sis, and/or Blades, you must comply with applicable federal and state regulations regarding proper disposal procedures.
  • Page 15 For Ni-Cd batteries, you can also call 1-800-8-BATTERY when further information is required. • The packaging for the UNIVERGE SV8500 system contains the following labels regarding proper dispos- PRODUCT PACKAGE LABELING CONTAINS NICKEL-CADMIUM BATTERY. BATTERY MUST BE RECYCLED OR DISPOSED OF PROPERLY.
  • Page 16 Some products described in this manual are not (yet) available for specific countries or markets. For this rea- son, the related specifications, instructions for installation and use of these specific products are not valid for these markets. Refer to NEC Unified Solutions B.V. for more details in case of any questions about these prod- ucts.
  • Page 17 If no arrangement has been made with your supplier, please contact the local author- ities for further information. 3. Declaration of Conformity • Česky “NEC Corporation” tímto prohlašuje, že tento “SV8500” je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 1999/5/ES.  http://www.nec-unified.com/doc REGULATORY...
  • Page 18 1999/5/CE.  http://www.nec-unified.com/doc • Íslenska Hér með lýsir “NEC Corporation” yfir því að “SV8500” er í samræmi við grunnkröfur og aðrar kröfur, sem gerðar eru í tilskipun 1999/5/EC.  http://www.nec-unified.com/doc REGULATORY...
  • Page 19 • Italiano Con la presente “NEC Corporation” dichiara che questo “SV8500” è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva 1999/5/CE.  http://www.nec-unified.com/doc • Latviski Ar šo “NEC Corporation” deklarē, ka “SV8500” atbilst Direktīvas 1999/5/EK būtiskajām prasībām un citiem ar to saistītajiem noteikumiem.
  • Page 20 “NEC Corporation” declara que este “SV8500” está conforme com os requisitos essenciais e outras dis- posições da Directiva 1999/5/CE.  http://www.nec-unified.com/doc • Slovensko “NEC Corporation” izjavlja, da je ta “SV8500” v skladu z bistvenimi zahtevami in ostalimi relevantnimi določili direktive 1999/5/ES.
  • Page 21 In this manual, the following are used unless the types of the Telephony Server and the PBX need to be identified. TERMS USED IN THIS MANUAL SYSTEM NAMES SV8500, the system UNIVERGE SV8500 SV7000, the system UNIVERGE SV7000 Note 1...
  • Page 22 TERMS IN THIS MANUAL Terminal Name In this manual, the following terminals are mentioned as each common term unless these types need to be identified. TERMINAL NAMES GENERIC TERMS USED IN THIS MANUAL Dterm Series E/Dterm 75 Dterm Dterm Series i Digital terminal DT310 DT300 Series...
  • Page 23 From FP85-110 S7, SIP Handler can also control Standard SIP Video terminals and Standard SIP Voice terminals which are controlled by SP in FP85-109 S6 or earlier. Standard SIP terminals require connection tests of NEC. When service conditions of Standard SIP terminals vary depending on controlling device, Standard SIP terminals are mentioned as shown below.
  • Page 24 TERMS IN THIS MANUAL Media Gateway (MG), Media Converter (MC), and Voice Conference Server (VS) Names In this manual, the following are mentioned as each common term unless these types need to be identified. GENERIC TERMS USED IN THIS MANUAL EQUIPMENT NAMES MG(PRI) Card [SCA-24PRIA] MG(PRI) Box [MG-24PRIA]...
  • Page 25 TERMS IN THIS MANUAL GENERIC TERMS USED IN THIS MANUAL EQUIPMENT NAMES VS-32 VS32 VS-32(Dual) Card [SCA-VS32VA] VS-32(Dual) Box [MG-VS32VA] IPG Digital IPG Analog UG50 Note 6 General Terms • PIR on this manual is a term equivalent to GC (Gateway Chassis) in the North America. •...
  • Page 26 TERMS IN THIS MANUAL Note 7: For Proprietary Protocol mode, “[Proprietary Protocol]” will not display on the IPAN command. MG (PRI) in this manual indicates the following terminals: Note 8: • MG (PRI) Card [SCA-24PRIA] • MG (PRI) Box [MG-24PRIA] •...
  • Page 27 INTRODUCTION INTRODUCTION 1. Quick Reference Sheet The figure below shows devices/terminals explained in this manual. Others Terminal Desk Console Network Interface - Analog C.O. Line - ISDN Add-On Console - Analog TIE Line - PFT LOAD LOAD LINE LINE Terminal-Related Devices LINE LINE SPEED...
  • Page 28 INTRODUCTION 2. LT Cable Accommodations and Time Slot Allocations for PIR The following shows PIR LT cable accommodations and Time Slot allocation. INT-2...
  • Page 29 INTRODUCTION LT Cable Accommodations The figure below shows LT cable accommodations for PIR. A maximum of twelve LT cable conductors that range from LT 0 to LT 11 are provided on the backplane of PIR. The LT connector to be used is determined by the Circuit Card Mounting Location.
  • Page 30 INTRODUCTION Time Slot Allocation The figure below shows Time Slot allocation for PIR. Four Groups compose one Highway. Each Group consists of eight Time Slots. 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 20-23 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 : Time Slot LV 7 LV 0...
  • Page 31: Table Of Contents

    INTRODUCTION 3. Channel Accommodating Conditions The system has restrictions in accommodating IP equipment. A maximum of 460 channels can be accommodat- ed per LP. Make sure the total number of channels does not exceed 460. Each IP equipment occupies a certain number of channels as shown in the table below.
  • Page 32 INTRODUCTION 4. Operation of IP Equipment/Terminals When a Fault Occurs During a Conversation A conversation can be retained even if a fault occurs during the conversation. This section explains operation of IP equipment/terminals when a fault occurs during a conversation. Examples The following figures show examples for operation of IP equipment/terminals when a fault occurs during a conversation.
  • Page 33 INTRODUCTION Call Retention Function Status in IP Equipment/Terminals The following table shows the operation of IP equipment/terminals when a fault occurs during a conver- sation. The table describes information when Call Retention function is activated in IP equipment/terminals. If IP equipment/terminals have particular conditions such as the case that Call Retention function becomes inactive, the conditions are noted below the table.
  • Page 34 INTRODUCTION Time Duration Required Event which causes the discon- IP Equipment/Terminal Call can be Firmware tinuation of Call/Call Retention Remarks (Note 1, Note 17) retained (Note 2) function (Note 3) SP Controlled Standard SIP Terminal: No Limit terminal (Keep-alive through No Condition Telephony Server: Key operation on terminal...
  • Page 35 INTRODUCTION Time Duration Required Event which causes the discon- IP Equipment/Terminal Call can be Firmware tinuation of Call/Call Retention Remarks (Note 1, Note 17) retained (Note 2) function (Note 3) Up to 2 minutes 30 Analog 2MC No Condition seconds When Health Check timeout occurs Note 13 When a loop is opened in the self-office...
  • Page 36 INTRODUCTION Time Duration Required Event which causes the discon- IP Equipment/Terminal Call can be Firmware tinuation of Call/Call Retention Remarks (Note 1, Note 17) retained (Note 2) function (Note 3) SP-3927 • When a loop is opened at counter MCMG party PROG-B Is- No Limit...
  • Page 37 INTRODUCTION Time Duration Required Event which causes the discon- IP Equipment/Terminal Call can be Firmware tinuation of Call/Call Retention Remarks (Note 1, Note 17) retained (Note 2) function (Note 3) SP-3884 MG • When RTP communication stops Proprie- PRI PROG-A •...
  • Page 38 INTRODUCTION Time Duration Required Event which causes the discon- IP Equipment/Terminal Call can be Firmware tinuation of Call/Call Retention Remarks (Note 1, Note 17) retained (Note 2) function (Note 3) Earlier than • When Health Check timeout occurs SP-3987 • When a communication failure oc- Note 16 MGSIP Up to 4 minutes...
  • Page 39 INTRODUCTION Time Duration Required Event which causes the discon- IP Equipment/Terminal Call can be Firmware tinuation of Call/Call Retention Remarks (Note 1, Note 17) retained (Note 2) function (Note 3) Up to 6 minutes 30 • When Health Check timeout occurs IPG Digital No Condition seconds...
  • Page 40: Lbus

    INTRODUCTION Note 5: When Call Retention function is inactivated or when any key on the terminal such as Line/Feature key is pressed during a conversation using a headset/speaker, a call will be disconnected in 60 to 90 seconds (Call can be retained until the key operation.). When Call Retention function is inactivated, if the terminal starts to communicate with the Telephony Serv- Note 6: er, a call will be disconnected after the SIP timeout.
  • Page 41 INTRODUCTION Telephony Server/IP Equipment/Terminal Status No Control Signals between Telephony Server and IP Equipment/ Telephony Telephony CPU Restart associ- Terminal Server Mode Server Mode ated with New ACT- IP Equipment/Terminal Change by LAN Change Manu- side TP Memory Clear Viewpoint Cable Link Down ally by CMOD (Ex: ACT-side CPU...
  • Page 42 INTRODUCTION Telephony Server/IP Equipment/Terminal Status No Control Signals between Telephony Server and IP Equipment/ Telephony Telephony CPU Restart associ- Terminal Server Mode Server Mode ated with New ACT- IP Equipment/Terminal Change by LAN Change Manu- side TP Memory Clear Viewpoint Cable Link Down ally by CMOD (Ex: ACT-side CPU...
  • Page 43 INTRODUCTION Telephony Server/IP Equipment/Terminal Status No Control Signals between Telephony Server and IP Equipment/ Telephony Telephony CPU Restart associ- Terminal Server Mode Server Mode ated with New ACT- IP Equipment/Terminal Change by LAN Change Manu- side TP Memory Clear Viewpoint Cable Link Down ally by CMOD (Ex: ACT-side CPU...
  • Page 44 INTRODUCTION Telephony Server/IP Equipment/Terminal Status No Control Signals between Telephony Server and IP Equipment/ Telephony Telephony CPU Restart associ- Terminal Server Mode Server Mode ated with New ACT- IP Equipment/Terminal Change by LAN Change Manu- side TP Memory Clear Viewpoint Cable Link Down ally by CMOD (Ex: ACT-side CPU...
  • Page 45 INTRODUCTION 5. Basic Terms and Features This chapter explains IP-related basic terms and features that are used in the system. For more detailed informa- tion, refer to the reference documents. Basic Terms Registration To support communication between IP devices/stations and the Telephony Server, the IP addresses of them must be notified each other.
  • Page 46 INTRODUCTION ToS (Type of Service) Type of Service (ToS) is 1-byte data field used in IP packet. ToS value is used to assign priorities to IP packets that are exchanged in a network for QoS Control. DiffServ and IP Precedence are typical QoS Control Technics. QoS (Quality of Service) Quality of Service guarantees network bandwidth and availability for applications.
  • Page 47 Available SIP terminals in the system are DT700 Series, DtermIP (SIP), Soft Phone (SIP), WLAN Handset (MH Series) and Standard SIP Voice/Video Terminal. WLAN Handset (MH Series) supports the various features equivalent to the built-in PHS terminal. When using a locally purchased Standard SIP Terminal, NEC connec- tion test is required.
  • Page 48 INTRODUCTION IPPAD (PA-32IPLB) IPPAD is a gateway interface card that is automatically used when an IP station attempts to make/receive a call to/from a station and TRK accommodated in PIR. One IPPAD can control a maximum of 32 calls. Refer to the Circuit Card Description for more details.
  • Page 49 INTRODUCTION MG-PRI/PRA Media Gateway Primary Rate Access Interface (MG-PRI/PRA) is an interface between IP network and ISDN, and it provides an efficient network and cost-effective network through interaction with the Telephony Server by using the IP network via MG. MG-SIP128/96/16 Media Gateway-Session Initiation Protocol (MG-SIP) is an interface that enables your system to build a multi- service and reliable Voice over IP (VoIP) networks using Session Initiation Protocol (SIP) defined by IETF.
  • Page 50: Mg-Sip16 [Sca-16Sipmga/Mg

    INTRODUCTION MG(PRI) (1.5M) [SCA-24PRIA/MG-24PRIA] MG(PRI) [SCA-24PRIA/MG-24PRIA] is a media gateway between ISDN network and IP network to provide a Primary Rate Interface (T1) through interaction with the system. MG(PRI) is controlled by the Telephony Server, and a variety of services can be performed. 100M LINK CONSOLE 100M LINK...
  • Page 51 INTRODUCTION MG-COT Card [SCA-6COTA/SCA-6COTB] MG-COT Card [SCA-6COTA/SCA-6COTB] has a function of Media Gateway (MG) which is an interface be- tween IP network and Analog PSTN line. Also an analog telephone for exclusive use of Power Failure Transfer (PFT) can be connected through a PFT connector on this card. MG usually works independently. In the case of failure of MG-COT, PFT connects C.O.
  • Page 52 INTRODUCTION VS-32(Dual) [SCA-VS32VA/MG-VS32VA] Voice Server Conference Server provides Announcement feature, External Hold-Tone feature, and Conference feature. These features can be performed over IP network that may reduce communication cost drastically, com- pared with the existing Public Switched Telephone Network (PSTN). VS-32(Dual) has two types of Signaling Controls;...
  • Page 53 INTRODUCTION IP Gateway (IPG) IPG is a gateway device to allow a maximum of 32 Digital Multiple Line telephones/Single Line telephones to be accommodated in the SV8500 via a LAN. It enables the system to accommodate Digital Multiple Line tele- phones/Single Line telephones without the use of PIRs.
  • Page 54 INTRODUCTION Network Service Features, Terms Bandwidth Control Bandwidth for conveying IP packets can be controlled. When a call is made or received, the system automati- cally determines whether sufficient bandwidth can be reserved or not. If sufficient bandwidth is not remained, the system restricts call origination or termination.
  • Page 55 INTRODUCTION Echo Canceler Control by Location ID Echo is voice signal reflection to the calling party.Typical network-related echo is caused by poor impedance matching. Echo Canceler serves to alleviate this echo. In the system, Echo Canceler can be set to ON/OFF on a Location ID basis that is given to each network location.
  • Page 56 REVISION SHEET UNIVERGE SV8500 Peripheral Equipment Description - Introduction NWA-041680-001 Revision Sheet :DATE JULY,2013 TERMS IN THIS MANUAL :DATE MARCH,2011 4,5,6 Introduction Introduction 18, 24, 25, 5,6,12,13,14,15,17,18,19,22,23, 24,25,26,27 :DATE AUGUST,2010 :DATE JUNE,2013 Regulatory Notice 2, 4, 8, 9, 10 TERMS IN THIS MANUAL...
  • Page 57 NWA-041680-001 ISSUE 12.0 JULY, 2013 UNIVERGE SV8500 Peripheral Equipment Description Volume 1 TABLE OF CONTENTS Page CHAPTER 1 Devices Required to Build Network ......
  • Page 58 TABLE OF CONTENTS (CONTINUED) Page 7. Cable Specifications ............. . CHAPTER 2 IP-Related Basic Feature Programming .
  • Page 59 TABLE OF CONTENTS (CONTINUED) Page 3.3 ToS Control by Location ID ........... . . 133 3.3.1 General .
  • Page 60 TABLE OF CONTENTS (CONTINUED) Page 2. ZT/CS Installation Design ............167 2.1 Basic Knowledge on ZT Installation .
  • Page 61 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1. DHCP Server This section explains Dynamic Host Configuration Protocol (DHCP) Server Installation, Setup and the Optional Setting Procedure. By installing a DHCP server, IP addresses listed below can be automatically set to IP Termi- nals on the LAN.
  • Page 62 Be sure to install the latest version of Service Pack. Note: The figure below is an example of the network configuration that is used in this section. Network Configuration Domain : nec.com DHCP Server (IP Address:10.136.20.150) -Start Address:10.136.20.221 DNS Server -End Address:10.136.20.230...
  • Page 63 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK (2) Click “Services” tab to see services that are installed on the PC. When “Microsoft DHCP Server” is listed as follows, this procedure is not required. Close the Network Dialog Box, and move on to “2. DHCP Server Setup.”...
  • Page 64 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.1.2 Setting up DHCP (Microsoft Windows NT) STEP 1: Startup of Microsoft Windows NT Server Start the Microsoft Windows NT Server. STEP 2: Startup of DHCP Server service (1) Select “Start” -> “Settings” -> “Control Panel” and click the “Services” button. Then the “Services” dialog box appears as shown below.
  • Page 65 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: Startup of DHCP Manager Start DHCP Manager by selecting “Start” -> “Programs” -> “Administrative Tools [Common]” -> “DHCP Manager” as shown below. STEP 4: DHCP Server Address Entry (1) Select “Server” -> “Add” on the menu bar of the “DHCP Manager.” Then the following dialog box is dis- played.
  • Page 66 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK (2) Enter the IP address of the DHCP server. As an example, “10.136.20.150” is entered as the address of the DHCP server. (It is recommended to enter the IP address of the Microsoft Windows NT server.) (3) Click “OK”...
  • Page 67 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK (2) Select “Scope” -> “Create” on the menu bar as shown below. VOL.1-7...
  • Page 68 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK (3) When “Create” is selected, “Create Scope” dialog box is displayed. Enter Start Address, End Address, Sub- net Mask, and Lease Duration. In this example, the following is assigned: Start Address: 10.136.20.221 End Address: 10.136.20.230 Subnet Mask: 255.255.255.0 Lease Duration:3 Day(s) STEP 6: Activating the New Scope...
  • Page 69 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.1.3 Setting up DHCP Options - Default Gateway (Microsoft Windows NT) Note: This data assignment is optional. STEP 1: Adding Options (1) Select the activated scope (highlighted in blue) in the “DHCP Servers” list box. (2) Select “DHCP Options”...
  • Page 70 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK (3) The following “IP Address Array Editor” appears. Enter the IP address of the default Gateway in the “New IP Address” text box. (4) Click “Add->” button on the “IP Address Array Editor.” As an example “10.136.20.254” is assigned. (5) Click “OK”...
  • Page 71 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK (7) Click “OK” to close “DHCP Options: Scope” dialog box. (8) Make sure that “003 Router” is selected in the “Option Configuration” list box. Up to this point “DHCP Options” data assignment has completed. The DHCP server can notify the IP ad- dress of the default gateway to DHCP clients (including IP terminals) as option.
  • Page 72 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.1.4 Setting up DHCP Options - DRS Address (Microsoft Windows NT) Note: This data assignment is optional. Note: “DRS (Device Registration Server)” used in this section refers to Telephony Server. Telephony Server acts as DRS where IP device/terminal is registered.
  • Page 73 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK “DHCP Options: Default Values” dialog box appears. Click “New...” button. “Add Option Type” dialog box appears. Enter the following data of the new option: Name: Any name is available as far as it is not duplicated. In this case “DRS” is assigned as an example.
  • Page 74 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK The display returns to “DHCP Options: Default Values” as shown below. Make sure that “161 DRS” is added in the list box. Click “OK” button to close the dialog box. STEP 2: Adding Options Add the newly assigned option as performed in “2”...
  • Page 75 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK Click “Edit Array...” button. The “IP Address Array Editor” is displayed. Enter the IP address you want to use as the DRS in the “New IP Address” text box on the “IP Address Ed- itor”...
  • Page 76 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK When assigning “DRS Secondary”, enter two IP Addresses as shown below. In this case, the upper address is “DRS Primary” and the lower is “DRS Secondary.” Click the “OK” on the dialog box to close the “IP Address Array Editor.” The display returns to the “DHCP Options: Scope.”...
  • Page 77 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK Make sure that “003 Router” is selected in the “Option Configuration” list box. Up to this point “DHCP Options” data assignment has completed. The DHCP server can notify the IP address of the DRS to DHCP clients (including IP Enabled Dterm) as option. VOL.1-17...
  • Page 78 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.1.5 Setting up DHCP Address Conflict Detection (Microsoft Windows NT) Set the number of times the DHCP Server executes the Ping Command for the detection of IP address conflict. Follow the procedure below. * Be sure to perform this setting. DHCP Server must be installed in advance.
  • Page 79 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: The following dialog box appears. Enter the number of times the DHCP Server executes the Ping Command for the detection of IP address conflict. (Default: 0) VOL.1-19...
  • Page 80 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.1.6 Setting up DHCP Address Static (Microsoft Windows NT) By the following setting, a DHCP client is always assigned the same IP address. In consideration of network security, etc., follow the procedure below if necessary. DHCP Server must be installed in advance.
  • Page 81 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: The following dialog box appears. Enter the appropriate IP address and MAC address. The following figure is example. STEP 4: Then click “Add” button. After all the necessary IP addresses are set, click “Close” button. STEP 5: Select “Scope”...
  • Page 82 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 6: When the DHCP server reserves the address request from the target client, the message changes to “Reservation in use” as the following figure. VOL.1-22...
  • Page 83 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK When using Microsoft Windows 2000 Before installing DHCP server, prepare the following: • PC (Microsoft Windows 2000 Server) • CD-ROM of Microsoft Windows 2000 Server Be sure to install the latest version of Service Pack. Note: The figure below is an example of the network configuration that is used in this section.
  • Page 84 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK  STEP 2: Make sure that Microsoft DHCP Server is installed on the PC. Select “Start” -> “Settings” -> “Control Panel” -> “Add/Remove Programs” -> “Add/Remove Win- dows Components”, then the dialog below appears. Click the check box of “Networking Services”, and click “Details”...
  • Page 85 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: The dialog below appears, click the check box of “Dynamic Host Configuration Protocol (DHCP)”, and then click “OK”. STEP 4: Windows Components dialog box is displayed again, click “Next”. VOL.1-25...
  • Page 86 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 5: CD-ROM request dialog appears. Specify the location of CD-ROM (Drive:\i386) into edit box and click “OK”. Components start to be configured in the diagram below. STEP 6: Windows Components Wizard is complete, and the following diagram appears. Click “Finish”. VOL.1-26...
  • Page 87 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.2.2 Setting up DHCP Server (Microsoft Windows 2000) STEP 1: Start the Microsoft Windows 2000 Server. STEP 2: Select “Start” -> “Program” -> “Administrative Tool” -> “DHCP” then the dialog below appears. Se- lect “Action”...
  • Page 88 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 4: DHCP Administrative Tool dialog box appears again. Move the mouse pointer to the newly added DHCP IP Address (ss2p251[10.40.13.1]), and then select “Action” -> “New Scope”. STEP 5: Click “Next” on the dialog to create a new scope. VOL.1-28...
  • Page 89 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 6: Enter the scope name (DRS2) into the “Name:” edit box and click “Next”. STEP 7: Specify the effective IP Addresses (Start IP Address: 10.40.13.250, End IP Address: 10.40.13.253) and Subnet Mask, which DHCP server allocates to IP terminals. Then click “Next”. VOL.1-29...
  • Page 90 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 8: Enter the range of IP Addresses (Start IP address: 10.40.13.1, Start IP address: 10.40.13.4), which DHCP server does not allocate to IP devices/terminals. (Exclusive Range) STEP 9: Specify the lease duration (8 days) and click “Next”. VOL.1-30...
  • Page 91 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 10: Select the DHCP options. Select “Yes, I want to configure these option now”, and click “Next” to con- figure the DHCP options. VOL.1-31...
  • Page 92 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.2.3 Setting up DHCP Server Option (Microsoft Windows 2000) STEP 1: Select the DHCP options. Select “Yes, I want to configure these option now”, and click “Next”. The dialog below is displayed. STEP 2: Specify the domain name and IP address of DNS and click “Add” to register the IP address. After making sure that IP address is listed in the box, click “Next”.
  • Page 93 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: When Microsoft Windows Internet Name Service (WING) Servers are needed in the network (When NetBIOS comes into effect in IP network), specify the WING server name (WING) and the IP address (10.40.13.5).
  • Page 94 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 4: Select “No, I will activate this scope later” and click “Next”. STEP 5: Click “Finish” to complete the New Scope Wizard. VOL.1-34...
  • Page 95 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.2.4 Setting up DHCP Server Options - DRS Address (Microsoft Windows 2000) Note: “DRS (Device Registration Server)” used in this section refers to Telephony Server. Telephony Server acts as DRS where IP device/terminal is registered. Note: “SIP server”...
  • Page 96 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK For DT700 Series, and DtermIP(SIP): Firmware version 3.0.0.0 or later, select Option according to the following priorities: 1st priority is option 162. If there is no option 162, 2nd priority is option 120. If there is no option 120, 3rd priority is terminal local setting.
  • Page 97 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK Note: In the case that “120” is set to DHCP Server, when MH250s, Standard SIP terminals, and DtermIP(SIP)s coexist in a network using SIP Wireless Terminal Backup feature: - MH250 and Standard SIP terminal try to use a virtual IP address created by SIP Wireless Terminal Back- - DtermIP(SIP) tries to use Telephony Server’s IP address Because of the above, two DHCP Servers need to be prepared to distribute two types of IP addresses.
  • Page 98 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 4: Enter IP address of DRS (10.40.13.4) and click “Add”. After confirming the IP address is added, click “OK”. When setting two IP addresses, the first one in the column indicates IP address of DRS primary, and the Note: second one indicates that of DRS secondary.
  • Page 99 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 6: After completing the DRS setting, go back to the following window. Select “Scope Options” in the tree, and then select “Action” -> “Configure Options”. STEP 7: Click the check box of an appropriate option. The data entry field becomes available. •...
  • Page 100 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK • When IP address used with DHCP Options (120) is assigned. Select “Decimal”, and click “Add” after specifying a value per octet of the IP address. After all the settings are done, click “OK”. For example, when SIP Server’s IP address in the network is “10.40.13.6”, the following numbers have to be specified.
  • Page 101 “OK”. For example, when SIP Server name (host name) in the network is “sp0.nec.co.jp”, the following numbers have to be specified. Note that you have to click “Add” after specifying each of the number set into New value.
  • Page 102 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK Use the following ASCII spread sheet for specifying a SIP domain name. Note that available characters to be used for the domain name are different, depending on countries. 0x20: Space 0x21-0x7e: Graphic Characters CHAR.
  • Page 103 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 8: Highlight “Scope [10.0.0.0] ss2”, and select “Action” -> “Activate”. VOL.1-43...
  • Page 104 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.2.5 Setting up DHCP Address Conflict Detection (Microsoft Windows 2000) Set the number of times the DHCP Server executes the Ping Command for the detection of IP address conflict. Follow the procedure below. * Be sure to perform this setting. DHCP Server must be installed in advance.
  • Page 105 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: Click “Advanced” tab. The display changes as follows. STEP 4: Set the number of times the DHCP Server executes the Ping Command for the detection of IP address conflict. In the following example, “3” is specified as the number of times Ping is carried out. VOL.1-45...
  • Page 106 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 1.2.6 Setting up DHCP Address Static (Microsoft Windows 2000) By the following setting, a DHCP client is always assigned the same IP address. In consideration of network security, etc., follow the procedure below if necessary. DHCP Server must be installed in advance.
  • Page 107 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 4: Click “Address Leases” in the tree. The display changes as follows. The message “Reservation (inac- tive)” is displayed until the DHCP server receives the address request from the target client. STEP 5: When the DHCP server reserves the address request from the target client, the message changes to “Reservation (active)”...
  • Page 108 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 2. DNS Server This section explains how to set up a DNS server. The DNS server allows IP devices/terminals to set the IP ad- dress of the DRS Primary automatically. Follow the procedure below to set up the DNS server. This section con- sists of the following.
  • Page 109 DtermIP DRS Server IP Address: 10.136.20.100 (3) Connect to DRS Server Domain : nec.com Note: “DRS (Device Registration Server)” used in this section refers to Telephony Server. Telephony Server acts as DRS where IP device/terminal is registered. 2.1.1 Installing Microsoft DNS Server in Microsoft Windows NT STEP 1: Start the Microsoft Windows NT Server.
  • Page 110 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK Network Services List Box (Example) VOL.1-50...
  • Page 111 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: Click “Add” button on the “Network” dialog box. “Select Network Service” dialog box appears with the Network Service listing. Select Network Service STEP 4: Select “Microsoft DNS Server” in the list box and click “OK.” STEP 5: A dialog box appears to transfer necessary files for the server, indicating insertion of Microsoft Win- dows NT CD-ROM and input of file path information.
  • Page 112 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 2.1.2 Setting up DNS Server (Microsoft Windows NT) STEP 1: Start the Microsoft Windows NT Server. STEP 2: Start “DNS Manager.” • Select “Start” -> “Programs” -> “Management Tool” -> “DNS Manager.” Startup of DNS Manager STEP 3: Click “DNS”...
  • Page 113 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 7: Click the right mouse button on the added DNS. STEP 8: Select “New Zone.” Selecting New Zone Note: To distribute arbitrary domain name to IP terminals, use DHCP server. STEP 9: Select “Primary” radio button and click “Next” button. “Selecting Primary”...
  • Page 114 STEP 10: The database file name is automatically input in “Zone File” text box. Click “Next” button to create zone. STEP 11: Make sure that the zone is created for “nec.com.” STEP 12: Click the right mouse button on the created zone and select “New Record” on the menu.
  • Page 115 New Resource Record STEP 14: Enter the IP Address (ex. “10.136.20.100) of the DRS and click “OK.” When an IP terminal inquires the IP address of “necdrs1.nec.com,” the DNS server replies “necdrs1.nec.com is 10.136.20.100.” STEP 15: Double click the nec.com of 10.136.20.150.
  • Page 116 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 2.1.3 Setting up DHCP Options - DNS Server Address, Domain Name (Microsoft Windows NT) Note: This data assignment is optional. This section explains how to set DHCP options for IP Enabled Dterm to obtain DNS server address, domain name.
  • Page 117 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 5: Click “Value>>>” button on the dialog box. “Edit Array...” button appears. Router Address Entry STEP 6: Click “Edit Array...” button. “IP Address Array Editor” dialog box appears. STEP 7: Enter the IP address of the DNS server in the “New IP Address” text box. [Example] New IP Address: 10.
  • Page 118 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK [Domain Name of DNS server] STEP 1: Select “015 Domain Name” from “Unused Options” list box and click “Add” button. “015 Domain Name” moves to “Active Options:” list box. Adding Options (Domain Name) STEP 2: Enter the Domain Name.
  • Page 119 DRS (necdrs1) DtermIP DRS Server IP Address: 10.136.20.100 (3) Connect to DRS Server Domain : nec.com “DRS (Device Registration Server)” used in this section refers to Telephony Server. Telephony Server acts Note: as DRS where IP device/terminal is registered. VOL.1-59...
  • Page 120 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 2.2.1 Installing Microsoft DNS Server in Microsoft Windows 2000 STEP 1: Start the Microsoft Windows 2000 Server. STEP 2: Make sure that Microsoft DNS Server has been installed on the PC. • Select “Start” -> “Settings” -> “Control Panel” -> “Add/Remove Program”. •...
  • Page 121 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 2: Check the box of “Domain Name System[DNS]” and Click “OK”. CD-ROM request dialog box appears.Specify the location of CD-ROM into edit box, and click “OK”. Components start to be configured in the diagram below. VOL.1-61...
  • Page 122 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: Click “Finish” to complete the DNS installation. VOL.1-62...
  • Page 123 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 2.2.2 Setting up DNS Server (Microsoft Windows 2000) STEP 1: Start the Microsoft Windows 2000 Server. STEP 2: Start “DNS Manager”. Select “Start” -> “Programs” -> “Administrative Tools” -> “DNS”. STEP 3: Click “Action” on the menu bar and point to “Connect To Computer...”. STEP 4: Select “This computer”...
  • Page 124 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 5: Highlight the DNS on DNS console, and then select “New Zone...” on pulldown of “Action”. Note: When the specified domain name is given to IP terminal, DHPC Server must be used. STEP 6: Click “Next”...
  • Page 125 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 7: Select “Standard primary” and click “Next”. STEP 8: Select “Forward lookup zone” and click “Next”. VOL.1-65...
  • Page 126 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 9: Enter a domain name (nec.co.jp) in the Name on the screen, and then click “Next”. STEP 10: Make sure the file name (nec.co.jp.dns) on the screen, and then click “Next”. VOL.1-66...
  • Page 127 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 11: Click “Finish” to complete the process. STEP 12: Make sure that the zone is created on DNS screen. VOL.1-67...
  • Page 128 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 13: Highlight the created zone (nec.co.jp). Click the right mouse button and select “New Host...” on the menu. VOL.1-68...
  • Page 129 Host name of IP terminal is set to "necdrs1" as an initial setting. STEP 15: Enter the IP Address of the DRS (10.136.20.100) and click “OK”. When an IP Enabled Dterm inquires the IP address of “necdrs1.nec.com”, the DNS server replies “necdrs1.nec.com is 10.136.20.100”. VOL.1-69...
  • Page 130 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 2.2.3 Setting up DHCP Options - DNS Server Address, Domain Name (Microsoft Windows 2000) This section explains how to set DHCP options for IP terminals to obtain DNS server address and domain name. Refer to 1.2.3 Setting up DHCP Server Option (Microsoft Windows 2000).
  • Page 131 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 3: Check the box of “006 DNS Servers” and specify IP address (10.136.20.150). Then click “Add”. IP address moves to “Active Options:” list box. STEP 4: After confirming the IP address, click “OK” on the dialog box. STEP 5: Confirm that DNS Server is added on DHCP Console.
  • Page 132 DEVICES REQUIRED TO BUILD NETWORK STEP 6: Select “Configure Options...” on “Action”. Check the box of “015 DNS Domain Name” and specify domain name (nec.co.jp), and then click “OK”. STEP 7: Confirm that DNS Server and DNS domain name are added on DHCP Console.
  • Page 133 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 3. FTP Server This section explains how to set up FTP Service and the related data assignment. FTP service allows IP terminals to download the program files by FTP. This section consists of the following. 10.
  • Page 134 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK “Network” dialog box (example) STEP 3: Click “Add” button on the “Network” dialog box. “Select Network Service” dialog box appears with the Network Service listing. STEP 4: Select “Microsoft Internet Information Server” in the list box and click “OK.” A dialog box appears to transfer necessary files for the server, indicating insertion of Microsoft Win- dows NT CD-ROM and input of file path information.
  • Page 135 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK FTP Service Setup This section explains how to set up FTP service. STEP 1: Start the Microsoft Windows NT Server. STEP 2: Start “Internet Service Manager.” Select “Start” -> “Program” -> “Internet Service Manager.” “Microsoft Internet Service Manager” ap- pears.
  • Page 136 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 4: Click the right mouse button on the FTP server icon. A pull-down menu appears. “Service Properties...” on pull-down menu STEP 5: Select “Service Properties...” on the menu. FTP Service Property dialog box appears. “FTP Service Properties for server”...
  • Page 137 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK STEP 6: Check “Allow Anonymous Connections” and “Allow only anonymous connections” boxes on the Service tab. STEP 7: Select “Directories” tab. Directory used for download is displayed. The default is “C:\InetPub\ftp- root.” Copy the files you want to download to the directory. Directory for Download VOL.1-77...
  • Page 138 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 4. Maintenance Administration Terminal (PCPro) This section explains the installation procedure of PCPro. The PCPro can be connected to the system via one of the following: • Using LAN Cable • Using RS-232C Cable (IOC card provides RS-232C interface.) •...
  • Page 139 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK When Using RS-232C Cable (Direct Connection) When the distance between Telephony Server and the PCPro within 15 meters (49 feet), Telephony Server can be connected using RS-232C cables. See the figure below for details. PCPro Cable Connection Diagram when using RS-232C Connect the PCPro, using the following cables: SV 4PORT CA-A, RS-232C CA-(1), and RS-232C.
  • Page 140 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK When Using RS-232C Cable via MODEMs If the distance between Telephony Server and the PCPro exceeds 15 meters (49 feet), then connect Telephony Server and the PCPro using modems. START Prepare the PCPro. Set up the personal computer, monitor, printer, etc.
  • Page 141 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 5. System Message Printer When connecting a System Message dedicated printer, follow the procedure below. START Install the printer. Install the printer, referring to the printer’s instruction manual. Connect the cable. Referring to the figure below, connect the cable between Telephony Server and the dedicated System Message Printer, which is equipped with a parallel port.
  • Page 142 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 6. Station Message Detail Recording (SMDR) Terminal This section explains the cable connection for the Station Message Detail Recording (SMDR) terminal.The SMDR terminal can be connected to the system via one of the following: •...
  • Page 143 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK When using RS-232C cable (Direct Connection) When the distance between Telephony Server and the SMDR terminal is within 15 meters (49 feet), Telephony Server can be directly connected using RS-232C cables. See the figure below for details. SMDR Terminal Cable Connection Diagram, when using RS-232C Connect the SMDR terminal, using the following cables: SV 4PORT CA-A, RS-232C CA-(1), and RS-232C.
  • Page 144 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK When using RS-232C cable via MODEMs If the distance between Telephony Server and the SMDR terminal exceeds 15 meters (49 feet), then connect Telephony Server and the terminal using modems. START Prepare the PC. Set up the personal computer, monitor, printer, etc.
  • Page 145 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK 7. Cable Specifications SV 4PORT CA-A Cable Cable Specification SV 4PORT CA-A 2000mm 200mm Cable Accommodation (TYP1) Cable Accommodation (A) OR-BK1 GY-BK1 W-BK1 Y-BK1 P-BK1 OR-BK2 GY-BK2 W-BK2 Y-BK2 P-BK2 OR-BK3 GY-BK3 W-BK3 Y-BK3 P-BK3 OR-BK4...
  • Page 146 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK RS-232C CA-(0) Detail RS-232C CA-(0) 1500mm (4 feet 11 inches) Champ Connector 25-Pin Cannon Connector (Female) (Male) TYPE-1-SD DTE-3-RD TYPE-2-RD TYPE-2-SD TYPE-3-RS TYPE-8-CD TYPE-4-CS TYPE TYPE-5-DR TYPE-20-ER TYPE-6-SG TYPE-7-SG Connect to TYPE-7-CD TYPE-4-RS IPX 2PORT CA-A Connect to PRT -5-CS...
  • Page 147 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK RS-232C CA-(1) Detail RS-232C CA-(1) 1500mm (4 feet 11 inches) Champ Connector 25-Pin Cannon Connector (Female) (Female) TYPE-1-SD DTE-3-RD TYPE-2-RD TYPE-2-SD TYPE-3-RS TYPE-8-CD TYPE-4-CS TYPE TYPE-5-DR TYPE-20-ER TYPE-6-SG TYPE-7-SG Connect to TYPE-7-CD TYPE-4-RS Connect to IPX 2PORT CA-A RS-232C Cable...
  • Page 148 CHAPTER 1 DEVICES REQUIRED TO BUILD NETWORK RS-232C CA-(3) Detail RS-232C CA-(3) 1500mm (4 feet 11 inches) Champ Connector 25-Pin Cannon Connector (Female) (Male) TYP-1-SD DCE-2-SD TYP-2-RD DCE-3-RD TYP-3-RS DCE-4-RS TYP-4-CS DCE-5-CS TYP-5-DR DCE-6-DR Connect to IPX 2PORT CA-A Connect to Modem TYP-6-SG DCE-7-SG TYP-7-CD...
  • Page 149 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING This chapter explains how to assign IP-related data using PCPro. Detailed information on each subject is ex- plained in the related guides. This chapter covers the following subjects: •...
  • Page 150 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 2. IP Related Basic Programming This section explains basic programming for IP devices/terminals, as listed below: • How to Assign Internal PHE • How to Assign Internal PHI • How to Assign SP-PHD • How to Assign SP-PHI •...
  • Page 151 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING How to Assign Internal PHE 2.1.1 General Internal PHE is a type of PH embedded in TP, which is one of the two registration destinations (TP and SP) in Telephony Server. Internal PHE handles signaling control data for IP devices including Analog 2MC/UG50- 2MC/UG50 (LC)/UG50-IPG (Analog) and MC part of MC&MG-COT/UG50-4LC2COTA.
  • Page 152 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 2.1.4 Data Programming STEP 1: ASYDL Assign Internal PHE as valid. SYS 1, Index 880, Bit 3 = 1 (Internal PHE is valid.) STEP 2: (ADTM) Assign the Internal PHE Port Number when changing the default value (= 60130). When the data are modified in this command, initialize Internal PHE by ADPM command.
  • Page 153 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING How to Assign Internal PHI 2.2.1 General Internal PHI is a type of PH embedded in TP, which is one of the two registration destinations (TP and SP) in the Telephony Server. Internal PHI handles signaling control data for IP devices in Proprietary Protocol mode, including MG(BRI) and MG(PRI).
  • Page 154 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 2.2.4 Data Programming STEP 1: ASYDL Assign Internal PHI as valid. SYS 1, Index 880, Bit 1 = 1 (Internal PHI is valid) Assign PHI Re-transmission Timer. SYS 1, Index 884, Bit 0 (PHI Re-transmission Timer) 0 = 256 ms (default setting) 1 = 512 ms STEP 2: (ADTM)
  • Page 155 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING The figure below is an example to show Internal PHI accommodated location. In this example, “01308” is specified to LENS and the Group colored blue is the accommodated location corresponding to the LENS. 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 20-23 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 17 21...
  • Page 156 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING How to Assign SP-PHD 2.3.1 General SP-PHD is a type of PH which controls communication between IP stations. In the communication, signaling control data are handled by SP-PHD while voice data are sent/received by peer-to-peer between IP stations. IP stations are registered in the Telephony Server to be controlled by SP-PHD.
  • Page 157 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 2.3.4 Data Programming SP-PHD is embedded in, and controlled by MPH. For the use of MPH, it is required to make Internal Note: PHE function valid. So Internal PHE data assignment is also necessary for the use of SP-PHD. About the procedure for Internal PHE data assignment, refer to Section 2.1, How to Assign Internal PHE.
  • Page 158 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 20-23 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 17 21 16 20 Highway Number HW9 HW10 VOL.1-98...
  • Page 159 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING How to Assign SP-PHI 2.4.1 General SP-PHI is a type of PH embedded in the Telephony Server. SP-PHI controls signaling control data for IP devices in SIP mode including MG(BRI)/MG(PRI) [SIP]/MC&MG-COT/MG-COT/8LC Card/VS32 (SIP mode). Some of IP devices in Proprietary Protocol mode are also controlled by SP-PHI ( ).
  • Page 160 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 2.4.4 Data Programming SP-PHI is embedded in, and controlled by MPH. For the use of MPH, it is required to make Internal Note: PHE function valid. So Internal PHE data assignment is also necessary for the use of SP-PHI. About the procedure for Internal PHE data assignment, refer to Section 2.1, How to Assign Internal PHE.
  • Page 161 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 20-23 00-01 02-03 04-05 06-07 08-09 10-11 12-15 16-19 17 21 16 20 Highway Number HW9 HW10 VOL.1-101...
  • Page 162 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING How to Assign Virtual PIR 2.5.1 General Virtual PIR is a non-physical Port Interface Rack. Some PHs must be accommodated in Virtual PIR. Virtual PIR can also be used for IP terminal, the Subline of Dterm, and voice channel for CCIS over IP. Virtual PIR Available MGs IMG0 IMG1...
  • Page 163 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 2.5.4 Data Programming STEP 1: ASYDL (Virtual PIR Assignment) Using SYS1 INDEX 556, 557, set 1 to each bit of the corresponding PIR to be used as Virtual PIR. The default value is 0 (=Physical PIR). The following shows the relationship between bit and PIR. IMG1 IMG0 Index...
  • Page 164 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING How to Set Terminal Software (when using HyperTerminal) 2.6.1 General Terminal software is necessary for assigning configuration data to IP devices. For Windows computers, HyperTerminal was bundled with Windows 95 to Windows XP. This section Note: explains the procedure for setting data by using HyperTerminal as an example.
  • Page 165 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING STEP 5: Port setting screen appears. Set appropriate data and click OK. Terminal software setting has completed. VOL.1-105...
  • Page 166 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 3. Network Data Programming This section explains data programming of network related data programming. The following topics are covered here: • Guideline for Calculating Bandwidth Required • Peer to Peer Bandwidth Control (by Location ID) •...
  • Page 167 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Guideline for Calculating Bandwidth Required This section provides a guideline for designing network that includes IP terminals in terms of bandwidth. 3.1.1 Bandwidth Required for Voice Traffic Bandwidth required for carrying voice traffic varies depending on the CODEC/Payload Size that is used for the traffic.
  • Page 168 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Equipment Payload Type Payload Size Remarks IP terminal DtermIP, G.711, G.729a 10ms, 20ms, 30ms, 40ms DtermIP INASET, G.723.1 (5.3k6.3k), 30ms, 60ms Note 2 IP Enabled Dterm G.723.1 (6.3k5.3k) Note 3 SIP Multiple DT700 Series DT750, G.711, G.729a 10ms, 20ms, 30ms, 40ms...
  • Page 169 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Equipment Payload Type Payload Size Remarks MG(PRI) MG-24PRIA, G.711, G.729a 10ms, 20ms, 30ms, 40ms Note 7 MG-30PRIA, G.723.1 (5.3k6.3k), 30ms, 60ms SCA-24PRIA, G.723.1 (6.3k5.3k) SCA-30PRIA T.30 (for Fax) G.726 (for Fax) 10ms, 20ms, 30ms, 40ms T.38UDP (for Fax) MG-PRI/MG-PRA G.711, G.729a...
  • Page 170 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Equipment Payload Type Payload Size Remarks MG(SIP) MG-SIP16, G.711, G.729a 20ms, 30ms, 40ms Note 8 MG-SIP16 [MG-16SIPMGA/ SCA-16SIPMGA], MG-SIP16 [SCA-16SIPMG(US)] MG-SIP96 G.711, G.729a 20ms, 30ms, 40ms MG-SIP128 [MG-128SIPMGG] G.711, G.729a 20ms, 30ms, 40ms MG-SIP128 [MG-128SIPMGJ] G.711 20ms Soft Phone...
  • Page 171 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Note 2: For DtermIP 8 button-type (ITR-8D), G.723.1 cannot be used. Payload type G.722 can be used only for: Note 3: • The connection between DT700 Series (DT730/DT730G/DT750) • The connection between DtermSP30 Version 15 and DT700 Series (DT730/DT730G/DT750) The payload type/payload size depends on the connecting SIP terminals.
  • Page 172 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Note 11: When Soft Client SP350 is used as an ACD terminal, assign the following payload type and payload size. Payload Type Payload Size G.711 20ms, 30ms, 40ms G.729a Following payload type and payload size are effective only for the connection to DtermSP30 (Version 15 or later), SP350, DT750, DT730, DT730G.
  • Page 173 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING 3.1.2 Bandwidth Required for Control Signal The following shows approximate value of bandwidth required for carrying control signal. Relationship between Equipment and Bandwidth Required for Control Signal Bandwidth Equipment Required [kbps] Remarks Note 1 Note 2 Analog MC Analog 2MC per unit...
  • Page 174 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Bandwidth Equipment Required [kbps] Remarks Note 1 Note 2 MG(SIP) MG-SIP16 {10% of bandwidth for call} per unit See Remarks. Note 3 MG-SIP16 Card [SCA-16SIPMGA] {10% of bandwidth for call} per unit See Remarks. Note 3 MG-SIP16 Box [MG-16SIPMGA] {10% of bandwidth for call} per unit...
  • Page 175 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Bandwidth Equipment Required [kbps] Remarks Note 1 Note 2 VS-32 VS32 VS-32(Dual) Card Proprietary per unit (15kbps/ch) [SCA-VS32VA] Protocol per unit (37.5kbps/ch) 1200 VS-32(Dual) Box [MG- Proprietary per unit (15kbps/ch) VS32VA] Protocol per unit (37.5kbps/ch) 1200 per unit IPG Digital...
  • Page 176 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Bandwidth Equipment Required [kbps] Remarks Note 1 Note 2 Proprietary Protocol Mode UG50 Multi-slot mode • UG50 (COT-TYPE1) • UG50 (COT-TYPE2) [Proprietary Protocol] per channel UG50 Retrofit mode • UG50-4LC2COTA (MG part) • UG50-6COT [Proprietary Protocol] Proprietary Protocol Mode UG50 Multi-slot mode •...
  • Page 177 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING Peer to Peer Bandwidth Control (by Location ID) 3.2.1 General This feature can realize effective use of available bandwidth, by specifying adequate Payload Type and Payload Size on a location-location basis by using Location ID. Location is a group of equipment accommodated to the Telephony Server, which can be divided flexibly.
  • Page 178 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING As mentioned, LOC-ID is the basic unit for setting Bandwidth Control. LOC-IDs can be assigned on the basis of several units; network address, Point Code, Fusion Point Code, Station Number. The following explains about them. In addition, another type of LOC-ID called “Dummy Location” is also described here. [1] Network Address The figure below shows a network configuration where LOC-IDs are assigned on a network address ba- sis.
  • Page 179 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING [2] Station Number Assigning LOC-ID on a Station Number (STN) basis meets the requirement for more flexible configura- tion. By putting a specific station in an individual location, the station can be used in different bandwidth from other stations.
  • Page 180 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING [3] Point Code Assigning LOC-ID to Point Code (PC) is necessary for Bandwidth Control in CCIS over IP network. In CCIS over IP network, each Node manages Bandwidth Control individually. Each Node assigns LOC-ID to PC for the other Node.
  • Page 181 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING [4] Fusion Point Code Assigning LOC-ID to Fusion Point Code (FPC) is necessary for Bandwidth Control in FCCS network. In FCCS network, each Node manages Bandwidth Control individually. Each Node assigns LOC-IDs to FPCs except for its own. So each FPC, which means all equipment or whole locations controlled by an- other Node, is considered as single location.
  • Page 182 CHAPTER 2 IP-RELATED BASIC FEATURE PROGRAMMING [5] Dummy Location When network routes branched off in multiple directions, it is available to combine these routes into one by assigning Dummy Location as a branch point. Also, when multiple Locations exist in a single network, these Locations can be combined into