Manuale d’uso / di manutenzione del prodotto NN43001-314 del fabbricante Nortel Networks
Vai alla pagina of 418
Nor tel Communication Ser v er 1000 Br anch Office Installation and Commissioning NN43001-314 ..
Document status: Standard Document version: 01.02 Document date: 20 June 2007 Copyright © 2007, Nor tel Networks All Rights Reser v ed. Sourced in Canada.
3 Re vision histor y June 2007 This document has been up-issued to reflect changes in technical content f or CR Q01514742. May 2007 Standard 01.01. This document is issued to suppor t Communication Ser v er 1000 Release 5.0. This document contains information previously contained in the following legacy document, now retired: (553-3001-314).
4 Revision history Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
5 Contents New in this release 17 MG 1000B hardware platform 17 Media Card MC32S 18 Main and Branch Office r unning different releases 18 Main Office and Branch Office Migration 18 How to get help .
6 Contents MG 1000B with MGC Data Networking 38 MGC Network Connections 40 MG 1000B platform configuration ov er view 44 MG 1000B platform without an MG 1000B Expander 45 MG 1000B platf or m with an .
Contents 7 Every Branch Office HLOC is shared with the main office 96 No Branch Office HLOC is shared with the main office, but can be shared with another Branch Office 97 No Branch Office HLOC .
8 Contents Network Class of Ser vice 144 Network Routing Ser vice (NRS) 145 T runk Route Optimization (TRO) 145 Vir tual Office 145 Feature pac kaging 145 Feature implementation using Command Line In.
Contents 9 Planning and management 179 Contents 179 Data network planning 179 LAN/W AN bandwidth requirements 180 Branch Office dialing plan 181 Emergency Services 182 Zones 182 Music on Hold 182 ESN.
10 Contents Main office configuration 209 Contents 209 Introduction 209 Zone parameters 210 Element Manager zone configuration 213 IP Phone passwords and par ameters 215 MG 1000B IP Phone configuration 218 MG 1000B IP Phone configur ation using TM 3.
Contents 11 Summary of steps 255 Configuring the Media Cards 256 Configuring the trunks and lines 256 Zone parameters 256 Element Manager Branch Office zone configuration 260 Adding the Branch Of.
12 Contents Emergency Services configuration 315 Contents 315 Overview 315 Emergency Ser vices Access (ESA) 316 Routing ESA calls 316 Configuring ESA for the Branch Office 317 Element Manager ESA c.
Contents 13 Appendix A Preprogrammed data 361 Contents 361 Introduction 361 P asswords and codes 362 Default n umber ing plan 362 First digits 363 Impor tant extension n umbers 363 Flexib le Feature C.
14 Contents Provisioning 406 Main office 406 NRS 408 Branch Office 409 Call example 409 Main office 410 NRS 410 Branch Office 410 List of terms 411 Procedures Procedure 1 Printing intrazone and in.
Contents 15 Procedure 31 Using the T est Local Mode feature 286 Procedure 32 Using the Set-Based Remov al feature 288 Procedure 33 Configur ing the main office 299 Procedure 34 Configur ing the NRS.
16 Contents Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
17 Ne w in this release This document is a global document. Contact your system supplier or y our Nor tel representative to v erify that the hardware and software described are suppor ted in your area. This document descr ibes the Branch Office f eature and contains information on planning, installation, configuration, and maintenance.
18 New in this release Media Card MC32S F or CS 1000 Release 5.0, the new Media Card 32S (MC32S) fully replaces the functionality of the current V GMV pack NTVQ01BB . Y ou can use the new pack in both large and small systems, and an ywhere you can use the current NTVQ01BB pack.
19 Ho w to g et help This chapter explains how to get help for Nor tel products and ser vices. Getting help from the Nor tel web site The best wa y to get technical suppor t f or Nor tel products is from the Nor tel T echnical Suppor t web site: h ttp://www .
20 How to get help http://www .nor tel.com/ erc Getting help through a Nor tel distributor or re-seller If you purchased a service contract f or your Nor tel product from a distributor or authorized re-seller , contact the technical suppor t staff for that distributor or re-seller .
21 Overview Contents This section contains information on the following topics: "What is Branch Office?" (page 22) "Main Office and Branch Office Migration" (page 24) "MG 1000.
22 Overview "MGC Network Connections" (page 40) "MG 1000B platform configuration overview" (page 44) "MG 1000B platform without an MG 1000B Expander" (page 45) "MG 1.
What is Branch Office? 23 f or large systems to be suppor ted as a Branch Office. A mixture of pre CS 1000 Release 5.0 branches are suppor ted with CS 1000 Release 5.0 branches as long as the main office is r unning the latest software. The Branch Office f eature does not change with the addition of large system based branches.
24 Overview Figure 1 Branch Office associated with a CS 1000E main office Main Office and Branch Office Migration All Main Office call ser vers in CS 1000 Release 5.0 are large system based. A CS 1000 Small System Main Office is no longer suppor ted.
MG 1000B (MGC) compared to the MG 1000B (SSC) 25 mgcsetup command. With a properly designed data network, the multiple ELAN and TLAN interfaces can be used to implement a dual homed configuration f or the MG 1000B with MGC . F our of these interf aces are accessed by using RJ45 connectors on the f aceplate.
26 Overview tolerance, the MGC is equipped with a clock ref erence input/output. The clock ref erence input and output connections and cable detect are provided through a 15-pin DSUB connector . MGC Serial P or ts Each MGC installed in a CS 1000B pro vides the oppor tunity f or 3 remote SDIs.
MGC Serial Ports 27 MGC serial por t default configuration The def ault settings for the ser ial por ts are • Baud rate = 9600 • Number of data bits = 8 • Number of stop bits = 1 • P arity = .
28 Overview SSTD (NTAK03) not supported n/a n/a Card Option Mail not supported n/a n/a Standard Option 11C minimum vintages apply to all pac ks and daughter boards. Attempts to install unsuppor ted CEMux packs or to configure an unsuppor ted application are bloc ked.
MG 1000B platform hardware description 29 The diagrams throughout this document show a CS 1000E main office. All of the systems appearing in the list perf or m identical main office functions as f ar as the Branch Office f eature is concer ned. MG 1000B platf orm hard ware description The MG 1000B system has been enhanced f or CS 1000 Release 5.
30 Overview Figure 2 CS 1000 Release 5.0 MG 1000B System CS 1000 Release 5.0 continues to suppor t the e xisting Branch Office configuration that uses the SSC processor , but Nor tel no longer offers sales of the SSC based Branch Office. CS 1000 Release 5.
MG 1000B platform hardware description 31 MG 1000B Core, and the optional chassis expander perf or ms the same functionality as the MG 1000B Expander . Ref er to "Converting a Small System to a Branch Office" (page 201) for more inf or mation.
32 Overview Figure 3 MG 1000B Core/MG 1000B Expander MG 1000B Chassis CEMux packs are suppor ted in card positions 1 to 4 of an MG 1000B chassis. They are not suppor ted in the MG 1000B e xpander chassis, similar to what is the suppor t in the Option 11C SIPE system.
MG 1000B platform hardware description 33 slots MGC DLC slot #s slot s slot #s MG 1000B Core 50 Not used 1-4 4 7-10 MG 1000B Cabinet 11 0 Not used 1-10 (see Note 1) N/A N/A MG 1000B Chassis 5 0 4 (see.
34 Overview • The MG 1000B Expander is connected to the MG 1000B Core with copper wire . Theref ore, the bac k of the MG 1000B Expander does not hav e an Ether net por t. Figure 3 "MG 1000B Core/MG 1000B Expander" (page 32) shows the MG 1000B Expander .
MG 1000B platform hardware description 35 F or more information on the Signaling Ser ver , refer to Signaling Ser ver Installation and Commissioning (NN43001-312) . F or more inf or mation on SIP , H.323, and ov er lap signaling, ref er to IP P eer Networking Installation and Commissioning (NN43001-313) .
36 Overview When configur ing the NRS it is necessar y to enable the NCS. Ensure the check bo x "Network Connection Ser ver enab led" is check ed in the NRS configuration window of CS 1000 Element Manager . F or inf or mation on configuring the NRS, ref er to IP P eer Networking Installation and Commissioning (NN43001-313) .
MG 1000B platform hardware description 37 IP Audio Conference Phone 2033 i2001 2033 IP Softphone 2050 i2050 2050PC Mobile Voice Client 2050 i2050 2050MC WLAN Handset 2210 i2004 2210 WLAN Handset 2211 .
38 Overview (500/2500-type) or digital telephone or the PSTN uses one DSP por t. Calls between two IP Phones do not require any DSP por ts, as there is no need f or IP-to-circuit-switched tr anscoding. Media Cards provide echo cancellation, compression, and decompression of voice streams.
MG 1000B with MGC Data Networking 39 Y ou can connect the MGC to a Lay er 2 switch to handle signaling betw een the Call Server and the MG 1000Bs . If two of the MGC ELAN por ts connect to separate La yer 2 switches , the MG 1000B can remain operational if one of the Lay er 2 switches f ails.
40 Overview MGC Network Connections In the f ollowing diagr ams, two connections are sho wn to the e xter nal data equipment for the dual-homing f eature, distributed and nondistr ib uted.
MG 1000B with MGC Data Networking 41 The follo wing figure illustrates a typical network configuration that suppor ts dual homing of both the ELAN and TLAN. With this configuration, howe ver , a single La yer 2 s witch remains a single point of f ailure.
42 Overview Figure 7 Single server por t network connections (dual-homing - distributed) The f ollowing figure illustrates a typical network configuration f or a dual CPU Call Ser ver configur ation that suppor ts dual homing of both the ELAN and TLAN.
MG 1000B with MGC Data Networking 43 Figure 8 Multi server por t network configuration (dual-homing - distributed) Cascading can occur f or the MGC network connections f or up to a maxim um of 2 cabinets. Y ou can directly cable the MGCs , without the need f or e xter nal Lay er 2 switches .
44 Overview Multi Ser ver (CP-P4) P or t Network Configuration (Dual-homing - Distributed), shows a configuration with a Call Ser ver platf or m that does not reside in a MG 1000B cabinet and chassis; therefore no direct connection e xists to the MGC.
MG 1000B platform configuration overview 45 MG 1000B platform without an MG 1000B Expander Figure 11 "MG 1000B platf or m without MG 1000B Expander" (page 45) shows an MG 1000B platf or m configured without an MG 1000B Expander . This configuration has a single MG 1000B Core.
46 Overview F or more information on the V oice Gatewa y Media Card configuration, ref er to IP Line Fundamentals (NN43100-500) . For more inf or mation on Integrated Conf erence Bridge, refer to Integrated Conf erence Br idge Ser vice Implementation Guide (NN43001-558) .
Software requirements 47 Capacity Each CS 1000 main office can suppor t up to 255 branch offices. Each Branch Office suppor ts up to 400 IP Phone users. How ev er , since all IP Phones register with the main office, the governing f actor is the maximum number of IP Phones that can be suppor ted at the main office.
48 Overview Main and Branch Office running different releases The Main Office Call Ser ver and the Branch Office can ha ve diff erent software releases, as long as the Main Office r uns at the highest release. With the introduction of CS 1000 Release 5.
Software requirements 49 Features in mixed-software configurations F eature operation of IP Phone users in Normal Mode is the f eature set on the main office. IP Phone users in Local Mode use the f eature set on the Branch Office. Users of analog and digital devices alwa ys use the feature set on the Branch Office.
50 Overview Ref er to "Fir mware downloads" (page 345) for more inf ormation on upgrading firmware f or the IP Phone 2001, IP Phone 2002, IP Phone 2004, and IP Phone 2007. P ackage Combinations The MG 1000B with MGC requires existing packages 402 SOFTSWITCH and 403 IPMG that were introduced in Rls 4.
Survivability 51 If the main office Call Ser ver f ails and call processing ser vices are provided by an alternate Call Ser ver , the MG 1000B IP Phones register with the alternate Call Ser ver and receiv e call processing ser vices from it.
52 Overview Local Mode at the Branch Office, the MG 1000B telephones remain in Local Mode, displa ying a Server Unreachable (1) message and receives all call processing ser vices from the CP PM in the MG 1000B Core.
Survivability 53 A CF mode The A CF f eature f or IP Phones enables an IP Phone to reregister in the A CF mode dur ing a suppor ted system f ailure. The ACF mode preser ves the f ollowing: • active .
54 Overview F or fur ther information on this configuration and its limitations, see "Configuring non-zero S2 IP Addresses" (page 169) . Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
55 Band width Management Contents This section contains information on the following topics: "Introduction" (page 55) "Codec negotiation" (page 56) "Codec selection" (pag.
56 Bandwidth Management With the Network Bandwidth Management f eature, you can configure bandwidth zones on a network basis so that codec selection and bandwidth allocation software can identify whe.
Codec negotiation 57 Nor tel recommends configuring the same pa yload size for all codecs in the same node. SIP example If a G.711 20ms codec and G.729 30ms codec are configured, then codec negotiation uses the minimum pa yload size of 20 ms . That is, the G.
58 Bandwidth Management G.711 A-law and m u-law interw orking In case the far end uses a diff erent Pulse Code Modulation (PCM) encoding law f or its G.711 codec, systems that are configured as G.711 A-law also include G.711 mu-la w on their codec preferences list.
Codec negotiation 59 Codec selection F or ev er y Vir tual T r unk call, a codec must be selected bef ore the media path can be opened. When a call is set up or modified (that is , media redirection), one of two processes occurs: • The ter minating node selects a common codec and sends the selected codec to the originating node.
60 Bandwidth Management Algorithm details The H.323 Master/Slav e algorithm operates in the f ollowing manner : • The Master node uses its own codec list as the preferred one and finds a common codec in the f ar end’s list.
Codec negotiation 61 This is the preferred method of operation. • The calling user agent sends an SDP offer with its codec list in the INVITE message with a "sendrecv" attribute. The called user agent returns more than one codec in the SDP ans wer .
62 Bandwidth Management Configuring Bandwidth Mana g ement parameters The f ollowing sections describe how to configure Bandwidth Management in a CS 1000 network. Nor tel recommends that you read the Bandwidth Management section in Conv erging the Data Network with V oIP (NN43001-260) bef ore using the following configur ation information.
Configuring Bandwidth Management parameters 63 3 Choose unique Bandwidth Zone numbers for the Vir tual T r unks in the network. 4 Choose the codecs that will be enab led on each Call Ser ver . 5 Identify what the interzone codec strategy will be (BB-Best Bandwidth or BQ-Best Quality) f or each zone in the network.
64 Bandwidth Management Figure 13 Configuring a codec Configuring Bandwidth Management The steps to configure Bandwidth Management on the Call Ser ver are as f ollows: Step Action 1 Define a VPNI number in LD 15.
Configuring Bandwidth Management parameters 65 — Interzone Bandwidth = maximum bandwidth usage allowed between peer Call Ser vers • Call Ser ver zones that will be used f or Vir tual T runks with.
66 Bandwidth Management Figure 14 Zones web page Configuration using LD 117 A new Bandwidth Management zone is configured in LD 117 using the NEW ZONE command. An existing zone can be modified using the CHG ZONE command. LD 117 Configure a new or existing Band width Management zone .
Configuring Bandwidth Management parameters 67 Command Description • interZoneStrategy = BB (Best Bandwidth) or BQ (Best Quality); Nortel recommends this value be set to BB to conserve interzone bandwidth.
68 Bandwidth Management Figure 15 Maintenance Commands for Zones web page 3 Do one of the follo wing: • T o displa y intrazone statistics: 1. Select Print Interzone Statistics (PRT INTERZONE) from the Action drop-down list.
Configuring Bandwidth Management parameters 69 The Maintenance Commands for Zones web page reopens, displa ying the statistics for the specified zone or zones . A blank field indicates that statistic is either not av ailable or not applicable to that zone.
70 Bandwidth Management Command Description Print intrazone statistics for the identified zones, where: • zone = ALL or 0-255 The output of this command displays the following information: • Zone .
Adaptive Netw or k Bandwidth Management 71 to another Call Ser ver , the av ailable bandwidth is reduced automatically between those two zones . When the QoS between the two zones improv es, then the bandwidth limit is allow ed to retur n to nor mal.
72 Bandwidth Management Call scenario A call is requested from a telephone in VPNI 1/Zone 2 on Call Ser ver A to a telephone in VPNI 3/Zone 3 on Call Ser ver B. Both zones ha ve Adaptive Network Bandwidth Management enabled. 1. Call Ser ver A contacts the Network Redirect Ser ver to obtain the address of Call Ser ver B .
Adaptive Netw or k Bandwidth Management 73 Figure 17 Call Progress with Adaptive Netw ork Bandwidth Management Zone bandwidth management and Adaptive Network Bandwidth Management Using Element Manager.
74 Bandwidth Management When a call is made from a zone with Adaptiv e Network Bandwidth Management enabled, to a third par ty gatewa y , which has no zone, then the zone of the Vir tual T runk (VTRK) is used and appears in the zone tab le.
Adaptive Netw or k Bandwidth Management 75 Multiple Appearance Director y Numbers (MADN) can e xist on different zones. Calls to an MADN are handled the same as other IP Phone calls, and are subject to the same bandwidth limitations. New SNMP alar ms are provided to monitor the system.
76 Bandwidth Management Figure 20 Effect of a higher CQoS Coefficient Other configurab le coefficients used in the calculation are the QoS Coefficient (CQoS), QoS Response Time Increase (ZQRT), and QoS Response Time Inter val (ZQR TI).
Adaptive Netw or k Bandwidth Management 77 Configuration rules The configuration rules for Adaptiv e Network Bandwidth Management are as f ollows: • Each main office Call Server in a netw or k must ha ve a unique non-zero VPNI.
78 Bandwidth Management 4. T andem the inbound Branch Office calls b y creating a dialing plan which routes all calls destined for the Branch Office through the main office. Adv anced Configuration Notes 1. The default v alues f or Cpl, Cj, Cd, Cr and CQos can be increased to increase the response time for Sliding Maximum changes.
Adaptive Netw or k Bandwidth Management 79 Figure 21 Adaptive Network Bandwidth Management and CA C web page If the Adaptive Network Bandwidth Management f eature is enab led using the Enable Call Admission Control f eature (ZCA C) check bo x, then the other parameters can be adjusted as required.
80 Bandwidth Management Field Title Field Definition LD 117 equivalents QoS Response Time Increase (ZQRT) Bandwidth limit increment, as a percentage of the QoS factor for the zone CHG ZQRT QoS Respons.
Adaptive Netw or k Bandwidth Management 81 Command Description Change the Cd coefficient in the formula that determines how quickly an alarm reduces the Sliding Maximum bandwidth for the identified zo.
82 Bandwidth Management Command Description Change the parameters of an existing zone, where: • zoneNumber = 1-255 • intraZoneBandwidth = 1000000 (Mbit/s) • intraZoneStrategy = intrazone preferr.
Adaptive Netw or k Bandwidth Management 83 Command Description Change the QoS Response Time Interval while alarms are not coming, to increase the Sliding Maximum for the identified zone, where: • Zo.
84 Bandwidth Management Command Description — BMG = Branch Media Gateway (Branch Office) zone — VTRK = Virtual Trunk zone • zoneResourceType = resource intrazone preferred strategy — shared DS.
Adaptive Netw or k Bandwidth Management 85 Procedure 2 Displaying CA C parameters f or one or more zones Step Action 1 Select IP Network > Zones from the na vigator . The Zones web page opens (see Figure 14 "Zones web page" (page 66) ). 2 Click Maintenance Commands f or Zones (LD 117) .
86 Bandwidth Management Figure 22 Element Manager - CAC parameters Maintenance using LD 117 The same information can be display ed using commands in LD 117.
Adaptive Netw or k Bandwidth Management 87 Command Description Print intrazone statistics for the identified zones, where: • zone = ALL or 1-255 The output of this command displays the following inf.
88 Bandwidth Management Command Description • Strategy = BB/BQ • MO/VTRK /BMG= zoneIntent • QoS factor = % • Bandwidth configured = Kbps • Sliding max = Kbps • Usage = Kbps • Peak = % .
Adaptive Netw or k Bandwidth Management 89 Command Description • ZQRTI = 10-120 • ZQUAT = 1-99 • ZQWAT =1-99 • CACVT = 1-255 Sample outputs for PR T commands Figure 23 "Sample output for PR T INTRAZONE command" (page 89) shows an e xample of the output of the PR T INTRAZONE command.
90 Bandwidth Management Figure 24 Sample output for PRT INTERZONE command T andem Bandwidth Mana gement o ver view In order f or the main office to correctly keep tr ack of all the bandwidth being used to and from a Branch Office the call must be tandemed through the main office.
Dialing Plan Overview 91 Bandwidth utilization f or the Branch Office is trac ked at the main office and can be display ed in LD 117 using the PRT INTERZONE command.
92 Bandwidth Management Figure 25 A call between two branch offices tandems thr ough the main office Figure 26 "General legend" (page 93) on Figure 26 "General legend" (page 93) shows a general legend f or the figures in the follo wing section.
Network using Uniform Dialing Plan 93 Figure 26 General legend Network using Uniform Dialing Plan The f ollowing section provides general netw ork configuration for a network using UDP only . Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
94 Bandwidth Management Figure 27 "Scenar io 1: UDP throughout the network" (page 94) shows two or more main offices with their branch offices, within a larger netw or k. Callers within each main office/Branch Office "region" use UDP to place calls between systems.
Network using Uniform Dialing Plan 95 T able 7 "Configuration details f or the general case" (page 95) describes the network configuration and the steps that a call takes dur ing its setup.
96 Bandwidth Management Region Provisioning detail 1 The DMI for the Branch Office "LOC" inserts a gateway routing prefix in front of the number.
Network using Uniform Dialing Plan 97 2. The Branch Office sends the call to 395-3456 to the main office. 3. The main office deter mines that this is LOC 39534, to another Branch Office, with gatewa y routing prefix 552. The system inser ts the prefix and transmits 552-395-3456 to the NRS.
98 Bandwidth Management 3. The main office deter mines that this is LOC 39534 to another Branch Office, with gatewa y routing prefix 552. The system inser ts the prefix and transmits 552-395-3456 to the NRS.
Network using Uniform Dialing Plan 99 determines that all calls to prefix 552 are to be sent to Branch Office A2; it directs the call to the Branch Office . 4. The main office sends the call to 552-399-3456 to the Br anch Office. The Branch Office deletes the prefix and the HLOC, and rings set 3456.
100 Bandwidth Management that all calls are to be sent to the main office; it directs the call to the main office. 2. The Branch Office sends the call to 444-3456 to the main office. 3. The main office deter mines that this is to another main office.
Network using Uniform Dialing Plan 101 Figure 33 Call flow f or Scenario 1 - call to remote Branch Office (originator side) 1. The Branch Office user dials 6-444-3456.
102 Bandwidth Management Figure 34 Call flow f or Scenario 1 - call to remote Branch Office (destination side) 1. Main office B determines that this LOC plus digits is to a local Branch Office with prefix 225. (If sharing this LOC with another Branch Office, the e xtended LOC is 44434.
Network using Uniform Dialing Plan 103 Figure 35 Call flow f or Scenario 1 - call to remote Branch Office (originator side) 1. The Branch Office user dials 6-444-3456.
104 Bandwidth Management Figure 36 Call flow f or Scenario 1 - call to remote Branch Office (destination side) 1. Main office B deter mines that LOC 444 is to a local Branch Office with prefix 225. The system transmits 225-444-3456 to the NRS . The NRS checks its pro visioning, and deter mines that this call goes to Branch Office B1.
Network using Uniform Dialing Plan 105 which provides service for the Branch Office using the LOC . See step 3 . 4 Provision the NRS to send all calls to a LOC with a gatewa y routing prefix to the Branch Office directly .
106 Bandwidth Management Figure 37 Pro visioning example Procedure 3 Pro visioning T andem Bandwidth Management Step Action 1 Enter the main office Gatewa y endpoint identifier in the T andem Endpoint field for each Branch Office GW configured on the NRS.
Network using Uniform Dialing Plan 107 Figure 38 T andem endpoint configuration in Element Manager 2 Plan the gatew ay routing prefix es. At least one prefix is needed per Branch Office, although any branch offices that hav e a prefix for ESA "911" calls does not necessarily require another .
108 Bandwidth Management T able 9 "Main office B DMI and RLI provisioning (for calls in Branch Office B)" (page 108) lists main office B DMI and RLI provisioning.
Network using Uniform Dialing Plan 109 7 Provision the main office and Branch Office with a home location code (HLOC) or multiple codes to ter minate all calls that should terminate on this system.
110 Bandwidth Management Create an RLI Create a LOC ROUT 71 FLEN 7 RLI 51 T able 13 "Main office A LOC provisioning f or LOC to remote main office systems - main office B is LOC 841" (page 110) lists main office A LOC provisioning f or LOC to the remote office.
Network using Uniform Dialing Plan 111 Network using mixed Coordinated Dialing Plan and Uniform Dialing Plan The follo wing section provides general details of the network setup . Figure 39 "Scenario 2 - UDP between main offices , CDP inside the main office region" (page 111) shows an e xample of a mixed network configuration.
112 Bandwidth Management Region Provisioning detail 1, 2, 3 Prefixes for branch offices for regular calls not required. May still have prefixes for E-911 calls, if required. 1 All branch offices are provisioned at the NRS to route all calls through the main office.
Network using Uniform Dialing Plan 113 4. The main office sends the call to 3456 to the Branch Office. The Branch Office rings set 3456. Abnormal case - calls originating using UDP , but terminating using CDP Figure 41 Call flow f or Scenario 2 - local call dial UDP 1.
114 Bandwidth Management Figure 42 Call flow for Scenario 2 - local call to remote Branch Office (originator side) 1. The Branch Office user dials 6-444-3456. The system transmits 444-3456 to the NRS. The NRS checks its provisioning, and deter mines that all calls are to be sent to the main office; it directs the call to the main office.
Network using CDP only 115 Figure 43 Call flow f or Scenario 2 - call to remote Branch Office (destination side) 1. The main office B deletes the HLOC, and determines that this is to a local Branch Office .
116 Bandwidth Management Figure 44 Scenario 3 - full CDP network T able 16 "Provisioning details f or this case" (page 116) lists the provisioning details f or a full CDP network. Ta b l e 1 6 Pro visioning details for this case Region Provisioning detail 1, 2, 3 CDP used for all calls within the region.
Network using CDP only 117 Region Provisioning detail 1 All branch offices are provisioned at the NRS to route all calls through the main office. 1 Main office sends all CDP calls to destinations that are not its own Branch Office to the NRS with unchanged dialled digits.
118 Bandwidth Management to the NRS. The NRS checks its provisioning, and deter mines that all calls to prefix 552 are to be sent to Branch Office A2; it directs the call to the Branch Office. 4. The main office sends the call to 552-43456 to the Branch Office.
Network using CDP only 119 Figure 47 Call flow for Scenario 3- calls to remote Branch Office (destination side) 1. Main office B deter mines that this is to a local Branch Office with prefix 225. The system transmits 225-53456 to the NRS. The NRS checks its provisioning, and determines that this call goes to Branch Office B1.
120 Bandwidth Management Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
121 Band width Management Suppor t f or Netw ork Wide Vir tual Office Contents This section contains information on the following topics: • Section "F eature descr iption" (page 121) • .
122 Bandwidth Management Suppor t for Network Wide Vir tual Office The customer can check the value of the Current Zone f or IP sets using LD 20, PR T command - as this value is not configur able, no changes are made to LD 11.
Feature implementation 123 Interaction with Zone-based Digit Manipulation A new prompt is added to the Customer Data Block (CDB) to configure the zone (Current or Configured) to be used f or Zone-based Digit Manipulation f eature.
124 Bandwidth Management Suppor t for Network Wide Vir tual Office Prompt Response Description TYPE: NET_DATA Networking. -VPNI 1-16283 Virtual private network identifier.
Feature oper ation 125 Prompt Response Description ZONE <number> Zone Number which Nortel Networks IP Phone set belongs. CLS VOLA Allow/deny Virtual Office operation from this TN. VOUA Allow/deny Virtual Office login onto this TN using other phone (destination of Virtual Office login).
126 Bandwidth Management Suppor t for Network Wide Vir tual Office Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
127 Alternative Call Routing f or Netw ork Band width Management Contents This section contains information on the following topics: "Description" (page 127) "Operating parameters".
128 Alternative Call Routing f or Network Bandwidth Management Figure 48 "Example of Alter native Call Routing f or NBWM in operation" (page 128) shows a diagr am of a typical network where Alter native Call Routing for NBWM can be used. It illustrates the sequence of e vents that are explained in the information follo wing the diagram.
Description 129 • Branch Office calls to or from another Branch Office controlled b y the same main office The ter m "Branch Office" refers to Media Gatewa y 1000B (MG1000B) and Sur vivab le Remote Gatewa y (SRG) systems in this document.
130 Alternative Call Routing f or Network Bandwidth Management The AL TPrefix applies to the zone in which the call originates. There is one AL TPrefix for each zone that requires alter nate routing. All Call Ser vers must be able to translate the AL TPrefix es for all zones that require Alter nativ e Call Routing f or NBWM.
Description 131 5. The call is routed over the PSTN/MCDN to the telephone at the Br anch Office. With the AL TPrefix digits inser ted, the resulting number must be one that CDP or VNR software can process as a steering code.
132 Alternative Call Routing f or Network Bandwidth Management Calls preceded by the AL TPrefix can be handled by the V acant Number Routing (VNR) f eature.
Description 133 Configuration required Configure the f ollowing: At the main office: • Use one of the dialing plan software packages to process the call, such as CDP or NARS. • Provision an AL TPrefix for the BO2 zone . • Provision the AL TPrefix as a Steering Code at the main office.
134 Alternative Call Routing f or Network Bandwidth Management Figure 50 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 1.
Description 135 4. The call is routed to the vir tual tr unk by CDP or VNR. The vir tual tr unk sends a request to the NRS for address resolution. The digit string sent to the NRS contains the AL TPrefix. The NRS retur ns the IP address of the Branch Office endpoint to the vir tual tr unk.
136 Alternative Call Routing f or Network Bandwidth Management gatekeeper/Netw or k Routing Ser vice (NRS) that can be co-resident with a Signaling Ser ver . IP Phones are also shown associated with each system. T elephone A belongs to the main office.
Description 137 • Set up a DMI to outpulse the correct digits to the Branch Office telephone. At the Branch Office: • No provisioning required. At the NRS: • No provisioning required.
138 Alternative Call Routing f or Network Bandwidth Management Example: AL TPrefix assigned is 777. The dialed number becomes 777 3121. 4. The call is routed by CDP or VNR to the outgoing route using an RLI. Example: 7773 is a steering code, translated to go to an RLI where there is one entr y , a PSTN trunk route.
Description 139 Figure 53 Example of an alternatel y routed call between a Branch Office telephone and another Branch Office telephone T elephone B in the BO2 zone calls T elephone F in the BO1 zone (the user dials 6020). In this example , the call alternately routes to the PSTN.
140 Alternative Call Routing f or Network Bandwidth Management At the NRS: • Create a CDP entr y for the AL TPrefix in the Branch Office gatewa y .
Description 141 Figure 54 Illustration showing digits dialed and outpulsed with Alternative Call Routing for NBWM 1. The user of IP Phone B in the BO2 zone dials IP Phone F in the BO1 zone (DN 6020) (.
142 Alternative Call Routing f or Network Bandwidth Management 2. The main office Call Ser ver deter mines there is insufficient bandwidth between the BO2 and BO1 zones. 3. The Call Ser ver inser ts the AL TPrefix configured for the BO2 z one prior to IP Phone F’s telephone number , dialed by the user .
Operating parameters 143 The configuration and provisioning f or the All Calls mode is exactly the same as the regular Alternative Call Routing f or NBWM f eature except that the Alter nate Routing for All Calls option is selected in LD 117 or Element Manager .
144 Alternative Call Routing f or Network Bandwidth Management This feature does not apply to vir tual trunk calls. It only applies to station-to-station calls, and routes them over the PSTN or MCDN network.
Feature implementation using Command Line Interf ace 145 Network Routing Service (NRS) Both the main office and Branch Office must be registered on the Nor tel NRS f or tandem routing to work f or main office to Branch Office tandeming.
146 Alternative Call Routing f or Network Bandwidth Management Command Description Enable Alternative Call Routing for NBWM, where: <zone> Input zone number (0-255). Configure the Branch Office zone using LD 117 at the main office. LD 117 - Configure Alternate Prefix number for a par ticular zone and the All Calls option, if desired.
Feature implementation using Element Manager 147 Feature implementation using Element Manager Zone configuration Use Element Manager to configure the specific zone proper ties. 1. Access the Zones web page to select Alternate Routing for Calls between IP Stations .
148 Alternative Call Routing f or Network Bandwidth Management Figure 56 Access the Zones web page to select Alternate Routing for Calls between IP Stations 2 Under Configuration click beside the Zone , or click the Zone yo u are programming, to expand the choices under it.
Diagnostics 149 Figure 57 Access the Alternate Routing for Calls between IP Stations web page to configure the feature The Zone Number f or the zone y ou selected in step 3 is displa yed. 4 Select the Enable Alternate Routing feature (ENL_ZAL T) check bo x to enable the Alter native Call Routing f or NBWM feature .
150 Alternative Call Routing f or Network Bandwidth Management The printout for all configured zones appears as f ollows: # Alternate Routing Status 10 ENL 11 DIS 12 DIS LD 117 - Obtain status for a Branch Office zone(s).
Diagnostics 151 Figure 58 System Maintenance web page 2 Click Select b y Functionality . The Select by Functionality web page appears. (See Figure 59 "Maintenance web page showing Select by Functionality" (page 152) .) Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
152 Alternative Call Routing f or Network Bandwidth Management Figure 59 Maintenance web page showing Select by Functionality 3 Click Zone dia gnostics . The Maintenance Commands f or Zones web page appears. (See Figure 60 "The Maintenance Commands f or Zones web page with PR T ZAL T results" (page 153) .
Diagnostics 153 Figure 60 The Maintenance Commands for Zones web page with PRT ZAL T results 4 Select Print Zone Alternate Prefix Information (PRT ZAL T) from the the drop-down list beside Action . 5 Select ALL or a zone number from the Zone Number drop-down list.
154 Alternative Call Routing f or Network Bandwidth Management 3 Click Zone dia gnostics . The Maintenance Commands for Zones web page appears. (See Figure 61 "Show the status of the Alternative Call Routing feature f or the Branch Office zone" (page 154) .
Maintenance 155 Maintenance Command Line Interface maintenance LD 117 - Enable and disab le Alternative Call Routing for NBWM f or a zone. Command Description ENL ZALT <zone> Enable Alternative Call Routing for Bandwidth Management for zone specified.
156 Alternative Call Routing f or Network Bandwidth Management Procedure 7 Enabling a zones Branc h Office behavior Step Action 1 F rom the navigator , clic k System > Maintenance . The Maintenance web page appears. (See Figure 58 "System Maintenance web page" (page 151) .
Maintenance 157 7 Click Submit . The display updates with new configuration data f or the zone y ou specified. —End— Suppress alarms Procedure 8 Suppress Alternative Call Routing for NBWM alarms Step Action Y ou can suppress alar ms QoS0038 and QoS0039 for a configurab le amount of time (0 - 3600 seconds).
158 Alternative Call Routing f or Network Bandwidth Management —End— Feature operation No specific operating procedures are required to use this feature . Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
159 Ho w the Branch Office f eature w orks Contents This section contains information on the following topics: "Introduction" (page 160) "Normal Mode and Local Mode operation" (pa.
160 How the Branch Office feature w or ks "MG 1000B Core interoperability" (page 176) "Network Wide Redundancy Phase II and Network Music" (page 176) Introduction The Br anch Office connects to the main office using Vir tual T r unks ov er the LAN or W AN.
Normal Mode and Local Mode operation 161 An IP Phone at the Branch Office ma y be in Local Mode for two diff erent reasons: • IP Phone may ha ve just booted up • IP Phone cannot communicate to the main office because of a W AN f ailure or a f ailure of the main office components.
162 How the Branch Office feature w or ks Bef ore the Branch Office IP Phone attempts to register with the main office, the MG 1000B first quer ies the Pr imar y NRS (NCS) fro the main office for the Vir tual T runk node IP address to redirect the IP Phone .
Normal Mode and Local Mode operation 163 After Vir tual Office login, the Branch Office does not star t the redirection procedure to the Main Office f or a logged in set immediately . The Main Office can accept only an IP Phone 2004 compatib le phone follo wing a Branch Office redirection.
164 How the Branch Office feature w or ks The licensing f eature applies only if more than four IP Phones are in Local Mode at the same time. If four or f ew er phones are in Local Mode simultaneously , the licensing f eature is not activated.
Normal Mode and Local Mode operation 165 IP Phone calls When an IP Phone calls another IP Phone, each telephone receiv es the address of the other to e xchange media directly between the telephones. Also note that when in Nor mal Mode, an MG 1000B IP Phone calling a main office IP Phone does not require any trunking to setup the call.
166 How the Branch Office feature w or ks V acant Number Routing (VNR) is mandator y in a Branch Office . It enables a Branch Office to route calls through the NRS , or other alter nate routes if configured, with minimal configuration.
Normal Mode and Local Mode operation 167 A TTENTION IMPORT ANT! If you are using one Access Code f or both local and long-distance calls, and that Access Code is associated with a Branch Office zone, all calls (local and long-distance) are routed through that Branch Office.
168 How the Branch Office feature w or ks The conferencing f eature for MG 1000B systems suppor ts up to 30 par ties with the addition of the MGC as the gatew ay controller f or the MG 1000B.
Configuring non-zero S2 IP Addresses 169 When the telephone detects that it has lost communication with the main office, it reboots and registers to the MG 1000B TPS. This means that, depending on the network configuration (or the point of f ailure in the network), not all MG 1000B IP Phones go into Local Mode at the same time.
170 How the Branch Office feature w or ks Figure 64 Configuration using S2 IP Address P oints to remember When an IP set registers to the main office using S2, remember the f ollowing impor tant points: • An IP Phone registered to the main office using S2 appears in the main office TPS as a "regular online" user .
Configuring non-zero S2 IP Addresses 171 System or a CS 1000E, a TN mismatch occurs and redirection from Branch Office to main office is not successful.
172 How the Branch Office feature w or ks 3 Program the IP address , subnet mask, and gatew ay addresses f or the MG 1000B IP Phone. 4 Program the S1 IP Address , action, and retr y parameters. The S1 IP Address is the MG 1000B Node IP Address. 5 Program the S2 IP Address , action, and retr y parameters.
Emergency services 173 The ke y difference between the main office user and the Branch User is the route selected f or the emergency call. An emergency call must be handed off to the PSTN ov er a tru.
174 How the Branch Office feature w or ks With all sites using the same ESDN, a conflict occurs in the NRS. The conflict is resolved b y using a unique prefix f or each site, which the main office adds as it routes the call.
Abbre viated Dialing 175 This f eature is implemented with a pre-translation group assigned to ev er y telephone. All IP Phones in the same bandwidth management zone use the same pre-translation g roup. TDM telephones, which share the same dialing plan with IP Phones in a bandwidth management zone, also use the same pre-translation group .
176 How the Branch Office feature w or ks • Calling Line Identification (CLID) on outgoing PSTN calls from the main office or the Branch Office are modified from f our to six digits. Additional digits can be added using the capabilities of CLID .
Network Wide Redundancy Phase II and Network Music 177 or the CS 1000/2100 itself is down. When the link to the remote 2100/CS 1000 or to the remote CS 1000/2100 itself is restored, the IP telephones are automatically redirected back to the remote CS 1000/2100 to receive telephony ser vices.
178 How the Branch Office feature w or ks Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
179 Planning and management Contents This section contains information on the following topics: "Data network planning" (page 179) "LAN/WAN bandwidth requirements" (page 180) ".
180 Planning and management • jitter CA UTION Service Interruption If the network is planned so IP Phones use a different route to the main office than the MG 1000B TPS, a f ault condition can occur .
Branch Office dialing plan 181 The maximum bandwidth required f or these activities is appro ximately 13 Kbps. This is insignificant when compared to the bandwidth requirement f or the expected v oice traffic.
182 Planning and management F or more information about CDP , ref er to Dialing Plans Reference (NN43001-283) . For details on other Numbering Plan options, refer to Communication Ser ver 1000S: Overview (NN43031-110) . F or more inf or mation on ESN, refer to "ESN Access Codes" (page 182) .
Branch Office dialing plan 183 Configuration example f or PSTN resources at the Branch Office IP Phones registered to the main office Call Ser ver can be grouped into one of two categories: • th.
184 Planning and management • All other long-distance numbers ha ve other routing as appropriate (1-NP A-NXX-XXXX). At the Branch Office, the f ollowing items must be configured: • Long-distance numbers in the same area code, such as 1-506-234-1234 or 1-506-675-1234.
Management 185 Command Description Tells the system the NARS Access Codes for local dialing and the NARS Access Code to convert the call into a long-distance call, to route the call to the Branch Office. In this case we are converting a call, such as "9 555-1212" into the call "6 1 506 555-1212", a conversion from AC2 to AC1.
186 Planning and management — trunks — the IP telephony node — Electronic Switched Network (ESN) data — Digital Signal Processing (DSP) channels — Branch Office zone f eatures — Emergency Ser vices Access at the Branch Office — Da ylight Savings Time at the Branch Office T elephony Manger 3.
Management 187 office, or any other Branch Office in the network. Howe ver , IP Phone calls to de vices or local trunks at the Branch Office are counted as incoming Vir tual T runk calls to the analog or digital de vices or local trunks.
188 Planning and management The identifying digits in the main office Call Ser ver’s CDR log are the manipulated string as specified by the Br anch Office zone. F or example , the Branch Office user dialed "9, 555-1212", but the main office Call Ser ver changes it to "6, 1-613-555-1212".
Management 189 A TTENTION IMPORT ANT! The notification lev el for a Branch Office zone must be configured exactly the same in the main office and the Branch Office. System security CS 1000E and CS 1000M (Large System) system secur ity is e xplained in detail in System Management Reference (NN43001-600) .
190 Planning and management Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
191 Adding a Branc h Office Contents This section contains information on the following topics: "Introduction" (page 191) "Main office requirements" (page 192) "Branch Office requirements" (page 193) "Implementation summary" (page 194) "Adding a CS 1000 Release 5.
192 Adding a Branch Office firmware for the e xisting branch offices. Y ou can choose not to upgrade the firmware at the e xisting branch offices only if the IP Phones in those br anch offices are r unning at least the minimum v ersion of firmware as specified in "T elephones" (page 36) .
Main office requirements 193 share the v oicemail system in the main office. For an y configurations using centralized Call Pilot on the main office with one or more branch offices in separate time zones, the NMS pac kage is required at the main office f or the branch IP Phones.
194 Adding a Branch Office • Emergency Ser vices Access (ESA) package 329 • Vir tual Office (VIRTU AL_OFFICE) pac kage 382 and M3900 Phase III Vir tual Office Enhancement (VIR_OFF_ENH) package 387. These packages are optional; they are required only for Vir tual Office functionality .
Implementation summary 195 a. Upgrade the main office software to CS 1000 Release 5.0. Ref er to , Communication Ser ver 1000E Upg rades (NN43041-458) or CS 1000M and Mer idian 1 Large System Upgrades Over vie w (NN43021-458) . b . If not already implemented, implement IP P eer Networking as par t of a system installation or upgrade.
196 Adding a Branch Office g. Install and provision the local trunks (the XUT , PRI, and DTI cards). h. If applicable, configure Abbre viated Dialing. See "Abbre viated Dialing configuration" (page 337) . i. Provision the Vir tual T runks.
Adding a CS 1000 Release 5.0 Br anch Office to a Branch Office with a pre vious software release 197 F or fur ther inf or mation on upgrading the IP Phone fir mware, ref er to IP Line Fundamentals (NN43100-500) .
198 Adding a Branch Office Upgrade only the main office to CS 1000 Release 5.0 A TTENTION IMPORT ANT! A mixed software configur ation between the main office and branch offices running , CS 1000 4.0, CS 1000 Release 4.5 or CS 1000 Release 5.0, is per mitted.
Adding a CS 1000 Release 5.0 Br anch Office to a Branch Office with a pre vious software release 199 4 Install the ne w CS 1000 Release 5.0 Branch Office as described in "Implementation summar y" (page 194) . —End— Upgrade main office without IP Phone firmware upgrade T o upgrade the main office to CS 1000 Release 5.
200 Adding a Branch Office Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
201 Con ver ting a Small System to a Branch Office Contents This section contains information on the following topics: "Introduction" (page 201) "Requirements" (page 201) "Co.
202 Conv er ting a Small System to a Branch Office • single-chassis Meridian 1 Option 11C Mini/Meridian 1 PBX 11C Chassis with or without a chassis expander • single-cabinet CS 1000M Cabinet • .
Conv ersion 203 on upgrading an e xisting system to CS 1000 Release 5.0 software. Ref er to Signaling Ser ver Installation and Commissioning (NN43001-312) fo r instructions on installing a Signaling Ser ver on a Meridian 1 system.
204 Conv er ting a Small System to a Branch Office 2 F or each Small System that is to be conv er ted to a Branch Office: a. P ower down the system, including reser ve power if so equipped. b . Upgrade the system controller card if required. Ref er to Meridian 1 Small System Software -only Upgrade (NN43011-459) .
Conv ersion 205 i. Configure the V oice Gatew ay Media Cards. Refer to IP Line Fundamentals (NN43100-500) . Use the same zone f or DSP ph ysical TNs and IP Phone TNs. The zone n umber must match that at the main office . Refer to IP Line Fundamentals (NN43100-500) .
206 Conv er ting a Small System to a Branch Office Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
207 Upgrading to CS 1000 Release 5.0 Contents This section contains information on the following topics: "Introduction" (page 207) "Upgrading to CS 1000 Release 5.0" (page 208) Introduction This chapter describes upgrading an e xisting main office and its associated branch offices from CS 1000 4.
208 Upgrading to CS 1000 Release 5.0 Upgrading to CS 1000 Release 5.0 If the main office has not already been upgraded to CS 1000 Release 5.0, begin with step 1 . If the main office has been upgraded to CS 1000 Release 5.0, skip to step 2 . Step Action 1 At the main office: a.
209 Main office configuration Contents This section contains information on the following topics: "Introduction" (page 209) "Zone parameters" (page 210) "Element Manager zon.
210 Main office configuration Zone parameters Zone parameters must be configured at both the main office Call Ser ver and MG 1000B Call Ser ver . The main office procedure is similar to an IP P eer Network configuration with the Branch Office-specific configuration outlined in this chapter .
Zone parameters 211 Prompt Response Description - VPNI (0)-16283 Virtual Private Network Identifier for Bandwidth Management feature 0 or X = Disables feature 1-16383 = Enables feature <cr> = No Change 2 Configure the Branch Office zone. Configure the zone proper ties f or IP telephony bandwidth management.
212 Main office configuration Command Description • interZoneBandwidth = Interzone available bandwidth (see Note Note 1: ) 0-1000000 Kbps • interZoneStrategy = Interzone preferred strategy (BQ f.
Zone parameters 213 Command Description If the Branch Office observes Daylight Savings Time (DST), these parameters specify the start and end of DST. During DST, the clock automatically advances one hour forward.
214 Main office configuration Figure 67 Branch Office-specific Zone Basic Property and Bandwidth Management Figure 68 Zone Time Difference and time zone Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
IP Phone passwords and parameters 215 Step Action 1 Select IP Network > Zones in Element Manager navigator . The Zones window opens ( Figure 66 "Branch Office-specific zone configuration" (page 213) ). The zone list is the main window used f or zone configuration.
216 Main office configuration related commands, and e xplanations are given in T able 19 "IP Phone node pass words" (page 216) . Ta b l e 1 9 IP Phone node passwor ds Command Description nodePwdSet Sets the node password.
IP Phone passwords and parameters 217 1 Configure the length of the passw ord, SCPL, to be of non-zero length in LD 15. LD 15 Configure the SCPW length in the Customer Data Block.
218 Main office configuration 3.01" (page 218) ) or ov er la ys (see Procedure 12 "Configuring MG 1000B IP Phones at the main office using LD 11" (page 218) ). —End— MG 1000B IP Phone configuration After the Branch Office z ones and passw ords are provisioned, provision the MG 1000B IP Phones at the main office.
MG 1000B IP Phone configuration 219 2 Configure the f ollowing telephone data in LD 11: • T er minal type • Customer Number • TN • Zone • Prime DN to correspond to BUID LD 11 Pro vision Branch User and SCPW at the main office Prompt Response Description REQ: NEW CHG Add new data, or change existing data.
220 Main office configuration Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
221 MG 1000B platf orm har d ware installation Contents This section contains information on the following topics: "Installing an MG 1000B Core" (page 221) "Readiness checklist" (p.
222 MG 1000B platform hardware installation T o connect to the PSTN, use one of the follo wing interf ace cards: • 1.5 Mb T1 Multi-functional Digital Interf ace • Extended Universal T runk (analog) • 2.
Installing an MG 1000B Core 223 T ools checklist T o install the system correctly , make sure that the tools listed in Ta b l e 21 "T ools checklist" (page 223) are av ailable bef ore assembling the components.
224 MG 1000B platform hardware installation 1 F asten the r ight guide brac ket to the r ight rac k suppor t. a. Inser t two #12-24 self-tapping screws into the two middle slots in the guide brack et and into the respective holes in the right rac k suppor t.
Installing an MG 1000B Core 225 be at the top of the brac ket and must f ace to the front of the MG 1000B Core. Figure 70 Right ear bracket installed on the MG 1000B Core 4 Attach the left ear brac ket (mark ed with an "L") to the holes on the left side of the MG 1000B Core (near the front).
226 MG 1000B platform hardware installation 5 Place the MG 1000B Core on the guide brack ets. Carefully slide the MG 1000B Core into the rac k until the ear brack ets come to rest against the rac k suppor t. 6 Use the four remaining #12-24 self-tapping screws to fasten the MG 1000B Core to the r ack suppor ts (two scre ws on each side).
Installing an MG 1000B Core 227 b . F ollow the instr uctions in T elephony Manager 3.1 Installation and Commissioning (NN43050-300) . A sample printout of the Ethernet configuration is provided. Do not connect a serial por t to the A UX connector . It can damage the por t.
228 MG 1000B platform hardware installation Figure 73 Media Card Install a tr unk card to connect with the PSTN and an analog or digital line card to connect with local resources.
Installing a Signaling Ser v er 229 3. The power cab le for the Signaling Ser v er . Check that the po wer cord is the e xact type required in the host region. Do not modify or use the supplied A C power cord if it is not the correct type. 4. The ser ial cable f or the Signaling Ser ver .
230 MG 1000B platform hardware installation Preparing for rac k-mounting Procedure 14 Preparing the Signaling Ser ver for rac k-mounting Step Action The F ront Mount Brack et assembly is not intended for use as a slide rail system. The Signaling Ser ver must be firmly attached to the rac k.
Installing a Signaling Ser v er 231 Figure 77 Left hinge mount Figure 78 Right hinge mount Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
232 MG 1000B platform hardware installation When the door is attached to the Signaling Ser ver and rac k-mount apparatus, it appears as shown in Figure 79 "Snapped-in bezel door" (page 232) . Figure 79 Snapped-in bezel door —End— Rack-mounting Read the f ollowing warnings carefully before installing the Signaling Ser ver in the rack.
Installing a Signaling Ser v er 233 W ARNING MAIN A C POWER DISCONNECT: Y ou must install an A C power disconnect for the entire rac k unit. This main disconnect must be readily accessible, and it must be labeled as controlling power to the entire unit, not just to the Signaling Server(s).
234 MG 1000B platform hardware installation a. Align the rac k-mount brack ets on the Signaling Ser ver with the slide rail system on the rac k posts. b . Slide the Signaling Ser ver into place. Ref er to Figure 81 "Rack-mounting the Signaling Ser ver" (page 234) .
Installing a Signaling Ser v er 235 Connecting and powering up the Signaling Ser ver W ARNING Do not modify or use a supplied AC pow er cord if it is not the e xact type required in the region where the Signaling Ser v er is installed and used. Replace the cord with the correct type.
236 MG 1000B platform hardware installation Do not modify or use the supplied A C power cord if it is not the correct type. Ref er to in Communication Ser ver 1000S: Installation and Configuration (NN43031-310) for a detailed power cord description. b .
Installing a Signaling Ser v er 237 2. Gently pull the tabs out and down to s wing open the hinged bezel door . Figure 84 Signaling Server with open bez el door The MA C addresses are visible on the lower right-hand side when the bezel door is open. See Figure 85 "MAC address" (page 237) .
238 MG 1000B platform hardware installation Figure 86 Signaling Server indicators and power switch The Signaling Ser ver LED indicators show the follo wing: • P ower – green LED on, power on; LED off, power off . • Status – red LED off, CPU running; LED on, CPU halted.
239 MG 1000B software installation Contents This section contains information on the following topics: "Signaling Server software installation" (page 239) "Materials required" (pag.
240 MG 1000B software installation The Install T ool installs all Signaling Ser ver software, including the operating system, applications, and web files . The Install T ool also copies softw are files f or the V oice Gatewa y Media Cards and IP Phones, which are used to upgrade these components.
Signaling Server software installation 241 3 Label the CD appropriately (f or example , Signaling Ser ver , sse-x.xx.xx). —End— The Software CD-R OM must be readable in a standard CD-R OM drive . After you create a CD from the CD image, the CD contains sev eral directories and files.
242 MG 1000B software installation 1 Enter t at the Main Menu to access the T ools menu. The T ools Menu appears as shown in T ools menu . Figure 87 T ools menu 2 Under the T ools Menu : a. Set the date and time (default). b . Repar tition and reinitialize the hard disk.
Signaling Server software installation 243 Signaling Server por t speed Use Procedure 19 "Changing the Signaling Ser ver por t speed" (page 243) to change the initial por t speed of the Signaling Ser ver f or a maintenance terminal connection.
244 MG 1000B software installation —End— After installing software and configuring basic information about the Signaling Ser ver , the Signaling Ser v er components can be configured using the web-based Element Manager interf ace. See Element Manager System Ref erence - Administration (NN43001-632) .
Connecting the MG 1000B Core to the network 245 Figure 88 Back of MG 1000B Core Connect to the 10BaseT ELAN network interface por t 1, or , in the case of the MGC , the A UI por t, that is connected to the Ether net por t on the motherboard. Use the A UI por t with an Ether net Media Attachment Unit (MA U) for the MGC .
246 MG 1000B software installation Procedure 21 Configuring the ELAN network interface IP address Step Action T o configure the active ELNK Ethernet interface f or the Branch Office: 1 Go into LD 117. 2 Create host entr ies with IP address on the ELAN subnet.
Connecting the MG 1000B Core to the network 247 Procedure 22 Connecting the Ethernet por ts Step Action T o configure the TLAN and ELAN network interfaces at the MG 1000B Core and enab le traffic ov er the LAN/W AN, connect the CA T5 cables and configure the data connectivity .
248 MG 1000B software installation • under SIP GW Settings (see Figure 90 "Confir m IP telephony node values SIP Redirect Ser ver" (page 249) ): — Primar y Proxy/Redirect IP address —.
Installing MG 1000B Hardware 249 Figure 90 Confirm IP telephony node values SIP Redirect Server Installing MG 1000B Hard ware T o upgrade the hardware f or an Option 11C Chassis, perf or m the follo wing steps: • P ower down the chassis. • Remov e the SSC card as described in Procedure 3.
250 MG 1000B software installation Installing the cards The f ollowing sections describe the process required to install the MGC and CP PM cards. Removing the SSC car d Step Action 1 Unlatch the SSC card. 2 Remov e the SSC card from its slot. A TTENTION The SSC card should be preser ved f or a minimum of five days .
Installing MG 1000B Hardware 251 Figure 91 DSP Daughterboard Installing a DSP Daughterboard Step Action 1 Place the MGC on a saf e ESD surf ace. 2 Place the DSP Daughterboard in either Daughterboard position 1 (f or DSP DB-96) or Daughterboard position 2 (for DSP DB-32), depending on how the Daughterboard will be configured from a TN perspective .
252 MG 1000B software installation Installing the MGC card Step Action 1 Inser t the MGC into Slot 0 of the Chassis. A TTENTION Y ou must ensure that all dongles (for both MGC and CP PM cards) are correctly identified. Please DESTR O Y or RETURN the SSC dongle to your local Nortel Repairs/Returns center.
Installing MG 1000B Hardware 253 —End— The preceding steps enable users to upgrade the system one MG 1000B at a time. For each additional IPMG, repeat Procedure 3 (Removing the SSC card) to Procedure 5 (Installing the CP PM card). Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
254 MG 1000B software installation Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
255 Branch Office configuration Contents This section contains information on the following topics: "Configuring the Branch Office" (page 255) "Summary of steps" (page 255) ".
256 Branch Office configuration —End— Configuring the Media Cards The Media Cards (see Figure 73 "Media Card" (page 228) ) arrive at a customer location with pre-installed software. T o install and upgrade these cards, y ou need the latest workfile.
Zone parameters 257 Procedure 23 Configuring the MG 1000B zone Step Action W ARNING Before and after an upgr ade, perform a datadump (using LD 43 EDD or NRS Manager) on the CPPM or MGC to back up the existing data. 1 Set the current date and time. See Software Input Output Administration (NN43001-611) .
258 Branch Office configuration 3 Configure V acant Number Routing (VNR). VNR must be configured at the Branch Office. When a Branch User is in Nor mal Mode, a call to that user arriving at the Branch Office will be routed to the main office.
Zone parameters 259 A TTENTION IMPORT ANT! Zone 0, the default z one, must not be configured as a Branch Office zone . Network Bandwidth Management does not suppor t zone 0. If zone 0 is configured as a Branch Office zone, the Network Bandwidth Management feature will not be activated.
260 Branch Office configuration 5 Configure the parameters for IP Phone pass words and modifications. This procedure is outlined in "IP Phone passw ords and parameters" (page 215) .
Adding the Branch Office endpoints to the NRS database 261 the BUID points to both the Branch Office and the main office. Howe ver , there ma y be situations where a separate BUID ma y be required, such as in a Multiple Appearance DN (MADN) configuration.
262 Branch Office configuration Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
263 MG 1000B telephones Contents This section contains information on the following topics: "Overview" (page 263) "Installing and configuring IP Phones" (page 264) "Password r.
264 MG 1000B telephones • Analog (500/2500-type) telephones and de vices – "Analog devices" (page 288) • Digital telephones and devices – "Digital de vices" (page 288) This chapter provides information on installing and configuring IP Phones, analog de vices, and digital de vices at the Branch Office.
Installing and configuring IP Phones 265 At the Branch Office, under a Branch User registration request (plugging an IP Phone into a jack), the main office Call Server checks the configured terminal type against the IP Phone type and configuration.
266 MG 1000B telephones Step Action 1 Connect the IP Phone to an Ether net jack and configure the S1 IP address (or use Dynamic Host Control Protocol (DHCP) to retr ie ve the IP address).
Installing and configuring IP Phones 267 2002 hav e a one-line display . The IP Phone 2004, IP Phone 2007 and IP SoftPhone 2050 hav e a three-line display .
268 MG 1000B telephones Figure 95 Set-Based Installation Step 3 4 Lift the handset and listen f or the continuous dial tone. The Model prompt is displa yed as shown in Figure 96 "Set-Based Installation Step 4" (page 268) .
Installing and configuring IP Phones 269 Figure 98 Set-Based Installation Step 7 8 Replace the handset when y ou hear a relocation tone and see "OK" on the screen displa y . 9 The IP Phone is now registered with the Call Ser ver . W ait appro ximately ten seconds f or the ke y map download to complete .
270 MG 1000B telephones Branch User Config T o complete the interf ace-based configuration of the Branch User , the administrator or a trusted user can configure the IP Phone with the Branch User Config command. Before proceeding, be sure to obtain the required pass words as described in "P assw ord requirements" (page 265) .
Installing and configuring IP Phones 271 • Main office pass word — IP Phone Installer’s P ass word, T emporar y IP Phone Installer’s P ass word, or SCPW . F or information on setting up passw ords, see "IP Phone passw ords and parameters" (page 215) .
272 MG 1000B telephones Figure 101 Branch User ID 4 Enter the branch passw ord, that is the IP Phone Installer’s P ass word or T emporar y IP Phone Installer’s P assw ord for the TPS node at the Branch Office. See Figure 102 "Branch passw ord" (page 272) .
Installing and configuring IP Phones 273 Figure 103 Main Office T erminal Number 6 Enter the IP Phone Installer’s P assw ord, T emporar y Inter net Installer’s P ass word for the main office, or the SCPW f or the Main Office TN. See Figure 104 "Main office passw ord" (page 273) .
274 MG 1000B telephones CA UTION Network Problems During Installation: Setup: The IP Phone in the Branch Office is on a different subnet to the MG 1000B TPS and has a different route to the main office. The MG 1000B TPS can connect to the main office but the IP Phone cannot.
Installing and configuring IP Phones 275 2 Configure the repor t file in the Customize a Repor t page: • Under Field Selection, choose fields that hav e been configured in the IP Phone. • Under Custom Criter ia, enter criteria SYNCST A TUS = T ransmitted .
276 MG 1000B telephones • Enter search cr iteria Sync Status = All and click Searc h . • All the impor ted telephones are listed, click on a f ew telephones to verify the attributes. • Select all the telephone(s) impor ted and click T ransmit to synchronize with the PBX and test appropriately .
Installing and configuring IP Phones 277 A Branch User Identification (BUID) and Main Office TN (MO TN) can be provisioned, if the Inter net telephone belongs to a MG 1000B Branch Office. The local TN configured for the Branch Office set with CS 1000 Release 5.
278 MG 1000B telephones LD 20 pr inting of the IP Phone TN Block with CS 1000 Release 5.0 MG 1000B with MGC shows the TN entered as f our-field f or mat, with the matching MO TN TN as f our-field format, shown in the follo wing example: Ref er to "T est Local Mode" (page 286) for details on testing Local Mode functionality .
Installing and configuring IP Phones 279 c. Press the Select soft ke y . This reregisters the telephone at the main office . If Resume Normal Mode is not selected, the IP Phone automatically returns to Nor mal Mode after ten minutes.
280 MG 1000B telephones The BUID , or pr imar y DN, of an MG 1000B IP Phone should match its primar y DN at the main office , though this is not a requirement. If diff erent DNs are configured, the dial-in numbers change when the Branch Office is in Local Mode.
Using the IP Phones 281 3 (Optional) Disallow usage of Vir tual Office. For more inf or mation on the Vir tual Office feature , ref er to Features and Services Fundamentals (NN43001-106-B1) . LD 11 Enable/disable Vir tual Office (optional). Prompt Response Description REQ: NEW CHG Add new data, or change existing data.
282 MG 1000B telephones Changing the SCPW Use Procedure 27 "Installing IP Phones through overla ys" (page 279) to change the SCPW of a telephone at an y time. Procedure 28 Changing the SCPW Step Action 1 Dial the SCPC code f ollowed b y the current Station Control P ass word.
Using the IP Phones 283 Figure 106 Options menu The Vir tual Office Login option only appears if V OLA CLS is configured. 2 Use the navigation ke ys to highlight T elephone Option . 3 Press the Select soft ke y to activate the f eature. 4 Use the Up or Down k eys to select an option.
284 MG 1000B telephones Virtual Office Login on the Branch Office The Vir tual Office Login f eature is described in IP Phones Fundamentals (NN43001-368) . Procedure 30 Using the Vir tual Office Login feature Step Action This procedure e xplains how to log in to and log out of Vir tual Office.
Using the IP Phones 285 b . Use the navigation k eys to highlight Vir tual Office Logout. See Figure 108 "Vir tual Office application menu" (page 285) .
286 MG 1000B telephones 2. Press the Vir tual soft ke y to activate Vir tual Office Login. In either case, the user is prompted f or the User ID and the SCPW . When a Branch User IP Phone re-powers, it registers with the MG 1000B Call Ser v er , and is automatically redirected to the main office.
Set-Based Remov al 287 Figure 110 Resume Normal Mode The Vir tual Office Login option only appears if V OLA CLS is configured. b . Use the Navigation ke ys to highlight Resume Normal Mode .
288 MG 1000B telephones Procedure 32 Using the Set-Based Remov al feature Step Action When the A utomatic Set Remov al (AREM) f eature is enabled and y ou hav e a Set Relocation Secur ity Code (SRCD), follo w these steps: 1 Lift the handset or press the DN k ey of the IP Phone to be remo ved.
Analog and digital devices in the Branch Office 289 Digital telephones at a Branch Office can be configured using: • Set-Based Installation (not f or M3900-ser ies telephones) • Overla ys (locally or remotely through a modem or Ether net connection).
290 MG 1000B telephones Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
291 Dialing plan configuration Contents This section contains information on the following topics: "Overview" (page 291) "Introduction" (page 292) "Dialing plans" (page 292) "Routing" (page 294) "SIP/H.
292 Dialing plan configuration This section primar ily describes the configuration of a dialing plan f or off-net calls from MG 1000B IP Phones in Nor mal Mode.
Introduction 293 select trunks at the main office, Branch Office, or other branch offices as required. Theref ore, the user can route calls to gatewa ys that minimize long-distance costs, minimiz e bandwidth usage, or meet other criter ia.
294 Dialing plan configuration The NRS replies with the address inf or mation for E.164 numbers . It also provides a list of alter nativ e SIP or H.323 endpoints, sor ted by cost. If a terminating endpoint resource is busy when a call attempt is made, the originating endpoint tries the ne xt alternative.
Zone-based digit manipulation 295 Bandwidth management zones An IP P eer network is divided into different bandwidth management zones. Each IP Phone, Vir tual T r unk, or V oice Gatewa y DSP channel is assigned to a bandwidth management zone.
296 Dialing plan configuration By perf or ming this zone-based digit manipulation, calls from main office users and Branch Users undergo different routing.
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 297 If ISPN is YES, the CLID is f or med based on the call-type bef ore digit manipulation.
298 Dialing plan configuration • At the main office, configure the Branch Office zone proper ties in LD 117, excluding the ZA CB and ZDP proper ties. Ref er to IP P eer Networking Installation and Commissioning (NN43001-313) for details . • At the main office, configure the routing f or PSTN access.
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 299 A sample configuration is given in Appendix "Off-net dialing plan configuration e xample" (page 405) . Procedure 33 Configuring the main office Step Action 1 Configure the ZACB proper ty f or the Branch Office zone.
300 Dialing plan configuration dials "2 87654321", zone-based digit manipulation does not occur and the digit string remains unchanged. • CHG ZA CB <zone> AC2 A C2 In this configuration, only calls dialed with A C2 undergo zone-based digit manipulation.
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 301 digit manipulation occurs before any digit processing in the main office Call Ser ver or NRS . If DialingCode1, DialingCode2, or DialingCode3 are already present in the dialed digits, then they will not be re-inser ted.
302 Dialing plan configuration a. Configure the DMI in LD 86 with the DGT f eature. LD 86 Configure the Digit Manipulation Index at the main office .
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 303 Prompt Response Description ROUT Route number of the Virtual Trunk as provisioned in LD 16. 0-511 Range for Large System and CS 1000E system 0-127 Range for Small System and Media Gateway 1000B .
304 Dialing plan configuration Prompt Response Description SPN x … x Special Number translation Enter the SPN digits in groups of 3 or 4 digits, separated by a space (for example, xxxx xxx xxxx). The SPN can be up to 19 digits long. The maximum number of groups allowed is 5.
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 305 (ZDP + two dialed digits), a maximum of 100 SPNs must be configured f or each Branch Office. For each additional dialed digit included in the SPN, the maximum number of SPNs that must be provisioned f or each Branch Office is increased by a f actor of ten.
306 Dialing plan configuration Procedure 34 Configuring the NRS database Step Action After configuring main office routing to the NRS, the NRS database must be provisioned to identify the desired endpoint f or the calls.
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 307 Figure 112 NRS Lookup path for gatewa y endpoints Figure 113 NRS Routing Entries window f or selected endpoint 7 Click Ad d in the Routing Entries window to add a routing entr y .
308 Dialing plan configuration If some calls are to be routed differently from others, it is possib le to provision the multiple Numbering Plan Entr ies in the NRS to achiev e this.
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 309 Prompt Response Description DEL (0)-19 Number of leading digits to be deleted.
310 Dialing plan configuration F or example , assume that the PSTN trunk is on route 18 and the Customer number = 0. >LD 86 REQ NEW CUST 0 FEAT DGT DMI 18 DEL 3 INST Set to remove ZDP added in the.
Configuring the dialing plan for PSTN access to Branch Users in Nor mal Mode 311 After configur ing the specialized route for calls that hav e been routed to the Branch Office b y the NRS, the route must be associated with the ESN Special Number .
312 Dialing plan configuration Figure 115 Zone Dialing Plan and Access Codes T esting PSTN access using an MG 1000B IP Phone Use Procedure 36 "T esting PSTN access using an MG 1000B IP Phone" (page 312) to test that PSTN access is working correctly .
T esting PSTN access using an MG 1000B IP Phone 313 F or calls that tandem ov er the Vir tual T runk to the Branch Office and go out to the PSTN tr unk(s) in the Branch Office, the f ollowing configuration problems can occur: • The call can receive ov erflow tones.
314 Dialing plan configuration Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
315 Emer g ency Services configuration Contents This section contains information on the following topics: "Overview" (page 315) "Emergency Services Access (ESA)" (page 316) ".
316 Emergency Services configuration Either of these methods hav e a Branch Office implementation which tr iggers the main office Call Ser v er to f orward emergency ser vices calls to the MG 1000B PSTN. Calls are redirected ov er a Vir tual T r unk using the ser vices of the NRS.
Emergency Ser vices Access (ESA) 317 The Selective Router looks up the caller’s ANI in its Selective Routing Data Base (which is synchroniz ed with the ALI database) to deter mine the correct PSAP and then routes the emergency call appropriately . Hence, the call can be routed to any CO in the correct E911 T andem area.
318 Emergency Services configuration 13 Configure the Branch Office z one on the Branch Office. 14 Configure the ESN SPN on the Branch Office. 15 Configure the NRS for the ESA Special Number used. 16 T est ESDN using an MG 1000B IP Phone. 17 T est ESDN using an analog (500/2500-type) or digital telephone located at the Branch Office.
Emergency Ser vices Access (ESA) 319 The basic ESA f eature only provides f or a single ESA route per system. Since all IP Phones are associated with the same main office, all ESA calls theref ore go to the same Public Saf ety Answ er ing P oint (PSAP) regardless from which Branch Office they originated.
320 Emergency Services configuration ESA uses a route number rather than ESN route list inde x. Howe ver , ESN is required at the Branch Office . 4 Configure Emergency Ser vices Access (ESA) in LD 24. Configure an A CD number as an Emergency Ser vices Directory Number .
Emergency Ser vices Access (ESA) 321 Command Description • ESA Route # = Virtual Trunk route to MG 1000B Core. • AC = Access Code to add to dialed digits. If no AC is required, AC0 is to be entered in place of AC1 or AC2. • ESA Prefix = Digit string added to start of ESDN.
322 Emergency Services configuration Prompt Response Description DMI is only prompted when the Directory Number Expansion (DNXP) package 150 is equipped and SDRR = LDID. The maximum number of Digit Manipulation tables is defined by prompt MXDM. DMI is not prompted if route TKTP = ADM.
Emergency Ser vices Access (ESA) 323 Prompt Response Description FEAT NET Network translation tables TRAN Translator AC1 AC2 Access Code 1 (NARS/BARS) Access Code 2 (NARS) TYPE SPN Special code transl.
324 Emergency Services configuration 7 T est ESDN using a main office telephone to confir m that main office calls go out the main office trunks. If OSDN is used, the ESA route number must be blank to make test calls without using any trunk resources.
Emergency Ser vices Access (ESA) 325 —End— Procedure 39 Configuring the Branch Office zone Step Action 1 Configure the Branch Office z one on the Branch Office. In the Branch Office, only the zone number and bandwidth/codec selection is configured.
326 Emergency Services configuration Procedure 40 T esting ESDN using an MG 1000B T elephone Step Action 1 F or IP Phones: a. Dial the ESDN on an MG 1000B IP Phone in Local Mode. Use Procedure 31 "Using the T est Local Mode feature" (page 286) to enter Local Mode.
Emergency Ser vice using Special Numbers (SPN) 327 Figure 116 Zone Emergency Service Information Emergency Service using Special Numbers (SPN) Determining the dialing plan for emergency access calls is critical. In many jurisdictions, the emergency number is a fixed n umber (for e xample, "112" or "999").
328 Emergency Services configuration CLID verification (CLID VER) Use the CLID VER prompt in LD 20 to verify that the ESA or non-ESA (SPN) emergency number is proper ly composed and configured. Refer to "V erify CLID" (page 355) for more inf or mation.
329 Basic Emer g ency Services When V O Logged Out Contents "Overview" (page 329) "Making an ESA Call From a Logged Out Phone" (page 330) "Receiving ESA Callback" (page 3.
330 Basic Emergency Ser vices When VO Logged Out New functionality is introduced: to provide the ability f or the logged out phone to make ESA calls and receive callbac ks, temporarily register with the Call Ser ver .
Contents 331 • CPND bloc k: uses the English str ing V OLO and is automatically configured against the pr imar y ke y of all the emergency TNs. • DES: All the emergency TNs hav e the ESTN designator . • DN: The emergency DN configured b y administrator .
332 Basic Emergency Ser vices When VO Logged Out • If the timer e xpires but the phone is in volv ed in a call, the time out e vent is ignored. When this call is finished, the 20 minute timer reloads .
Contents 333 The use case Scenar io: K eep Logged Out State provides the requirement to pre vent the logged out phone registered with the Call Server f or ESA from reregistering.
334 Basic Emergency Ser vices When VO Logged Out The call to PSAP occurs immediately after the set registers, requiring the correct location inf or mation; This is not desired. Special handling ma y be required, possibly by directly calling backg round LIS for the V OLO TN.
Contents 335 Element Manager CS 1000 Release 5.0 Element Manager suppor ts the f ollowing configuration, provisioning and maintenance aspects of the Basic Emergency Ser vices When V O Logged Out Feature. • Configuration: Changes in ESA data bloc k in LD 24.
336 Basic Emergency Ser vices When VO Logged Out Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
337 Abbre viated Dialing configuration Contents This section contains information on the following topics: "Overview" (page 337) "Recommended configuration" (page 337) "Confi.
338 Abbre viated Dialing configuration • Each bandwidth management zone has a unique pretranslation group number assigned to it. • CLID of calls going to the pub lic network (E.164/PSTN) are con ver ted to the shor ter DN by removing the digits added dur ing pretranslation.
Configuring Abbreviated Dialing 339 Procedure 41 Configuring Speed Call List (SCL) Step Action 1 In LD 18, configure the SCL for each main office zone.
340 Abbre viated Dialing configuration Procedure 42 Configuring Pretranslation Groups Step Action While not required, it is recommended that the Pretranslation Group number (XLA T) be the same as the number of the zone to which it is assigned. 1 In LD 18, configure the Pretranslation Group for each main office zone.
Configuring Abbreviated Dialing 341 —End— Procedure 43 Assigning Pretranslation Groups to the telephones Step Action The Pretranslation Group m ust be assigned to all IP Phones and TDM telephones. This procedure describes how to configure a single telephone, and it must be repeated for each telephone in the group .
342 Abbre viated Dialing configuration Procedure 44 Configuring Incoming DID Digit Con version (IDC) Step Action 1 In LD 15, configure Flexib le Code Restr iction f or IDC . LD 15 Configure Flexible Code Restriction (FCR) for Incoming DID Digit Con version.
Configuring Abbreviated Dialing 343 3 In LD 49, configure Fle xible Code Restriction to allow all codes. LD 49 Configure Flexible Code Restriction (FCR). Prompt Response Description REQ NEW Add new data. TYPE FCR Flexible Code Restriction CRNO (0)-254 Code Restriction tree number INIT ALOW Allow all codes .
344 Abbre viated Dialing configuration Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.
345 Maintenance and diagnostics Contents This section contains information on the following topics: "Firmware downloads" (page 345) "Troubleshooting" (page 349) "Signaling Ser.
346 Maintenance and diagnostics The administrator enters umsUpgradeAll command at the main office. The fir mware v ersion on the Nor mal Mode Branch Office IP Phone is compared to the fir mware policy of the main office. If the fir mware is the same as the main office, no fir mware update is required.
Firmware downloads 347 The umsUpgradeAll command has no immediate impact on IP Phones that are logged in or out by Vir tual Office. Howe ver , the firmware files may be upgr aded, if required, when the Vir tual Office session is ter minated. F or information on Enhanced UNIStim Fir mware, ref er to IP Line Fundamentals (NN43100-500) .
348 Maintenance and diagnostics 3 The Branch Office IP Phones that are in Nor mal Mode (for e xample, IP Phones registered to the main office Call Ser ver) are check ed to see if they require a fir mware upg rade. If the IP Phones require a firmware upgrade, the IP Phones are redirected back to the Branch Office.
T roubleshooting 349 —End— T roub leshooting This section contains error messages and troubleshooting inf or mation f or IP Phone operation. When a login is attempted and one of the messages provi.
350 Maintenance and diagnostics Message Probable Cause Actions Main office node is not registered as a SIP or H.323 endpoint to the NCS. Register the main office node to the NCS. Branch User ID endpoint is not in NCS database. Check NRS database and update as required.
T roubleshooting 351 Number Description 12 Branch User main office unreachable, or Main office is not registered with the NRS as an endpoint. 13 Branch User main office User ID Unknown, or Branch User main office User ID and Main Office TN Combination does not exist, or IP Phone telephone type and Main Office TN telephone type do not match.
352 Maintenance and diagnostics Message Probable Cause Actions Incorrect Branch User ID entered. Retry with correct Branch User ID. No Main Office TN associated with Branch User ID configured. Configure Main Office TN to associate with Branch User ID.
T roubleshooting 353 Message Probable Cause Actions Incorrect Branch User ID entered. Retry with correct Branch User ID. Permission Denied (2) IP Phone Installer’s Password at the main office TPS not configured or disabled and the Branch User ID is already assigned to a user in another Branch Office.
354 Maintenance and diagnostics Message Probable Cause Actions Incorrect Primary or Alternate NRS IP address configured. Correct Primary or Alternate NRS IP address. Primary or Alternate NRS IP address unreachable from this endpoint. Check network configuration and update as required.
Call Server commands 355 The lock out affects the Vir tual Office login or Branch User Config and lasts for one hour . This loc kout does not sur vive re-registration of the IP Phone. Howe ver , the installation technician can issue the clearLockout command to clear the loc kout for a par ticular telephone.
356 Maintenance and diagnostics The CLID VER repor t contains the CLID composed for the Branch User . If the repor t is generated on the main office Call Ser v er , the CLID is composed as f ollows: .
Call Server commands 357 Command Description Print a table of Branch Office zone time adjustment properties entries. PRT ZTP [<Zone>] Print a table of Branch Office zone time adjustment properties entries. Enable/disable Branc h Office zone features LD 117 contains commands to enable and disab le features f or the Branch Office zones.
358 Maintenance and diagnostics A TTENTION IMPORT ANT! The notification lev el for a Branch Office zone must be configured the same at both the main office and the Branch Office. LD 117 Chang e/print PVQ notification levels. Command Description CHG ZQNL ALL <Level> Change the notification level for all zones.
Call Server commands 359 T o register all IP Phones at the CP PM, disconnect the LAN/W AN connection to the main office (not recommended) or individually log out the IP Phones from the main office. See "T est Local Mode" (page 286) . LD 117 contains inv entor y commands.
360 Maintenance and diagnostics Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
361 Appendix A Prepr ogrammed data Contents This section contains information on the following topics: "Introduction" (page 361) "Passwords and codes" (page 362) "Default numb.
362 Appendix A Preprogr ammed data • "Def ault numbering plan" (page 362) • "Fle xible F eature Codes" (page 364) • "SDI por ts" (page 364) • "T runk routes&.
Default n umber ing plan 363 outside this range. This arrangement enables the CS 1000E to automatically configure telephones. First digits T able 30 "Def ault numbering plan First digit" (page 363) shows the def ault numbering plan for a Branch Office.
364 Appendix A Preprogr ammed data Flexib le Feature Codes Many administrativ e procedures use Flexib le Feature Code (FFC) data. T able 32 "Fle xible F eature Codes" (page 364) lists the FFCs for the CS 1000E system.
SDI por ts 365 TTY Number Card Port Use Configuration 10 0 MTC/SCH/BUG 1200/8/1/NONE 20 1 CTY 1200/8/1/NONE Ta b l e 3 4 Pre-configured PTY ports TTY Number Card Port Use 14 0 0 MTC/SCH/BUG 15 0 1 MTC/SCH/BUG Modem port The pre-configured modem por t enables the remote maintenance modem to be connected without additional system programming.
366 Appendix A Preprogr ammed data Setting Code USER CMS ENL NO T elephone tones The telephone tones in Nor th America are as follo ws: • Dial tone: A continuous tone. • Special dial tone: Three beeps f ollowed by contin uous dial tone. • Overflow tone: Like a busy tone , except f aster and higher .
T r unk models 367 Route Type Access Code Mode Interface 51 FEX 7151 ICT - 52 FEX 7152 OGT - T runk routes marked with an asterisk (*) are configured to suppor t Call Detail Recording (CDR) output.
368 Appendix A Preprogr ammed data super vision = YES. Ta b l e 3 8 Preprogrammed trunk r oute information Mode Card Model Signaling DIP or DTN BIMP and TIMP 1 GRD DIP 3COM/600 2 LOP DIP 3COM/600 3 GR.
T r unk models 369 Mode Card Model Signaling DIP or DTN BIMP and TIMP 7* LDR Wink Start Supv = YES DIP 3COM/900 8* LDR Wink Start Supv = YES DTN 3COM/900 1 GRD DIP 3COM/600 2 LOP DIP 3COM/600 3 GRD DT.
370 Appendix A Preprogr ammed data Mode Card Model Signaling DIP or DTN BIMP and TIMP 1 GRD DIP 3COM/600 2 LOP DIP 3COM/600 3 GRD DTN 3COM/600 4 LOP DTN 3COM/600 5 GRD DIP 3COM/900 6 LOP DIP 3COM/900 .
371 Appendix B Branch Office engineering e xample Contents This section contains information on the following topics: "Introduction" (page 371) "Assumptions" (page 372) "Calc.
372 Appendix B Branch Office engineering example Assumptions Equipment characteristics Assume the Branch Office has the equipment char acter istics provided in T able 39 "Equipment characteristics" (page 372) .
Calculations 373 Calculations Figure 119 "Branch Office traffic flow" (page 373) is a conceptual representation of an MG 1000B Core. An actual system could require diff erent types and numbers of cards.
374 Appendix B Branch Office engineering example 2 Calculate the IP Phone traffic to analog (500/2500-type) telephones: Number of A Ts x CCS f or each A T x % of calls to ITs = IT traffic to analog (500/2500-type) telephones 36 x 5 x 0.
Calculations 375 MG 1000B Core and MG 1000B Expander requirements T able 41 "MG 1000B Core and MG 1000B Expander card type , number and de vices" (page 375) shows the number of cards required and the de vices on those cards.
376 Appendix B Branch Office engineering example 252 x 100 ÷ 120 = 210 calls 3 Calculate the IP Phone to analog (500/2500-type) telephones: IT to A T CCS x 100 seconds ÷ av erage hold time = IT to .
Calculations 377 Bandwidth requirements Bandwidth requirements in this section refer to the information in Ta b l e 4 2 "Full Duplex Ethernet bandwidth for one channel (one Er lang)" (page 377) , T able 43 "T raffic capacity at P .01, P .
378 Appendix B Branch Office engineering example 1 Calculate the data rate: T otal traffic in Erlangs (from Page 439 ) x 95 kbps 22 x 95 kbps = 2090 kbps = 2.09 Mbps One Erlang of TDM 64 kbps channel becomes 95 kbps pack ets after G.711 codec transcoding, which adds ov erhead.
Calculations 379 = 333 kbps Ref er to T able 44 "LAN/W AN bandwidth for one channel (one Erlang)" (page 377) for other codecs or pa yload sizes. —End— Branch Office conference engineering With no local conference T wo par ties at a Branch Office using IP Phones call each other .
380 Appendix B Branch Office engineering example LAN/W AN kbps = TCON (er langs) x 37 kbps —End— Procedure 52 Calculating known conference traffic Step Action When a Branch Office is known or expected to make a significant number of conf erence calls, traffic statistics should be collected or estimated.
Calculations 381 Procedure 53 "Calculating Branch Office traffic, and LAN/W AN bandwidth without local messaging (CallPilot) capabil" (page 381) covers only simple CallPilot voice messaging traffic f or a LAN/W AN bandwidth calculation.
382 Appendix B Branch Office engineering example LAN/W AN kbps = VMT (erlangs) x 37 kbps —End— Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
383 Appendix C On-net dialing plan configuration e xamples Contents This section contains information on the following topics: "Introduction" (page 383) "Coordinated Dialing Plan".
384 Appendix C On-net dialing plan configuration e xamples Figure 120 Coordinated Dialing Plan (CDP) Call Scenarios This section describes the follo wing call scenar ios, all based on Figure 120 &quo.
Coordinated Dialing Plan 385 From Branc h Office to main office In this scenar io , the follo wing occurs: • DN 3101 (in the Branch Office) dials DN 3001 (or 3002 - both are registered with the main office). • The Branch Office recognizes 3001 as a vacant number .
386 Appendix C On-net dialing plan configuration e xamples TYPE DSC DSC 31 FLEN 4 RLI 12 Ref er to IP P eer Networking Installation and Commissioning (NN43001-313) f or more information. —End— NRS configuration T o configure the NRS, do the follo wing: Step Action 1 Create CDP Domain: "MO_BO_CDP".
Uniform Dialing Plan 387 TYPE: 2004P1, 2004P2 TN 61 0 CUST 0 BUID 3002 —End— Ref er to Procedure 27 "Installing IP Phones through ov erlays" (page 279) and IP P eer Networking Installation and Commissioning (NN43001-313) f or more information.
388 Appendix C On-net dialing plan configuration e xamples From main office to Branch Office In this scenario, the f ollowing occurs: • DN 3001 or 3002 dials DN "65043101" (a digital telephone in the Branch Office). • The main office Call Server recognizes the digit "6" as A C1 and the digits "504" as LOC.
Uniform Dialing Plan 389 — DN 3101 can call DN 3002 by dialing "3002", instead of the "65013002" dialed in Nor mal Mode. — DN 3002 can call DN 3001 by dialing "65013001", instead of the "3001" dialed in Nor mal Mode.
390 Appendix C On-net dialing plan configuration e xamples 5 Configure HLOC in Customer Data Block. >LD 15 REQ: CHG TYPE: CDB NET_DATA YES ISDN YES CLID YES ENTRY <xx> HLOC 501 6 Configure Vir tual T runk route.
Uniform Dialing Plan 391 —End— Ref er to IP P eer Networking Installation and Commissioning (NN43001-313) f or more information. Branch Office T o configure UDP at the Branch Office , do the follo wing: Step Action 1 Configure ESN Control Block f or UDP .
392 Appendix C On-net dialing plan configuration e xamples >LD 15 REQ: CHG TYPE: CDB NET_DATA YES ISDN YES CLID YES ENTRY <xx> HLOC 50 6 Configure Branch User .
Group Dialing Plan 393 Figure 122 Group Dialing Plan (GDP) Call Scenarios This section describes the follo wing call scenar ios, all based on Figure 122 "Group Dialing Plan (GDP)" (page 393).
394 Appendix C On-net dialing plan configuration e xamples • The MG 1000B Core ter minates the incoming Vir tual T runk call to DN 3101. • The V oice Gatew a y channel in the Branch Office provides IP-TDM transcoding.
Group Dialing Plan 395 • The NRS is queried f or a destination node IP address with which to route the call over the Vir tual T r unk. The main office node IP address is returned because "501" is registered to the main office.
396 Appendix C On-net dialing plan configuration e xamples 3 Configure Route List Block (RLB). F or more inf ormation, ref er to Procedure 9 "Configur ing ESN and MG 1000B zones" (page 210) . >LD 86 REQ NEW FEAT RLB RLI 12 ENTR 0 ROUT 120 DMI 0 4 Configure CDP Distant Steer ing Code (DSC).
Group Dialing Plan 397 ENTRY <xx> HLOC 501 8 Configure Vir tual T r unk Route. >LD 16 REQ NEW TYPE RDB CUST 00 ROUT 120 DES VTRKNODE51 TKTP TIE VTRK YES ZONE 101 NODE 51 PCID H323 ISDN YES M.
398 Appendix C On-net dialing plan configuration e xamples Branch Office T o configure GDP at the Branch Office , do the follo wing: Step Action 1 Configure ESN Control Block for CDP and AC1. >LD 86 REQ NEW CUST 0 FEAT ESN CDP YES MXSC 50 NCDP 4 AC1 6 DLTN YES 2 Configure Digit Manipulation.
T ransf erable DN 399 NET_DATA YES ISDN YES CLID YES ENTRY <xx> HLOC 504 6 Configure Branch User . >LD 11 REQ: NEW TYPE: 2004P1, 2004P2 TN 61 0 CUST 0 BUID 65013002 7 Configure Vir tual T r unk Route.
400 Appendix C On-net dialing plan configuration e xamples Original configuration (pre-transfer) Figure 123 "T ransf erable DN (TNDN) (pre-transf er)" (page 400) shows a sample of a TNDN configuration bef ore the move .
T ransf erable DN 401 — 3001 "MO" — 3002 "MO" — 3101 "BO" — 3201 "CS_B" The Move Alice is transf erred from main office A to Office B. Bob is transf erred from Office B to the Branch Office. Linda is transf erred from the Branch Office to main office A.
402 Appendix C On-net dialing plan configuration e xamples • Call Ser ver B — DN: 3001 (zone 20) — VNR: YES • MG 1000B Call Ser ver — DN: 3201 (zone 15, BUID 3201), 3101 — VNR: YES • NR.
T ransf erable DN 403 NET_DATA YES VNR YES RLI 12 2 Remov e the TN at Office A when the user has moved from office A to office B. >LD 11 REQ: OUT TYPE: 2004P1, 2004P2 TN 61 0 3 Add the new TN at Office B using a new telephone with the same DN. >LD 11 REQ: NEW TYPE: 2004P1, 2004P2 TN 62 8 4 Configure the NRS as follo ws: a.
404 Appendix C On-net dialing plan configuration e xamples Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.
405 Appendix D Off-net dialing plan configuration e xample Contents This section contains information on the following topics: "Introduction" (page 405) "Call scenario" (page 405).
406 Appendix D Off-net dialing plan configur ation example Figure 125 Off-net dialing plan example - call scenario. Pro visioning Main office At the main office Call Ser v er , the follo wing is provisioned: • A C1 = 1, and AC2 = 2 >LD86 REQ PRT CUST 0 FEAT ESN MXLC 50 .
Provisioning 407 >LD 117 => PRT ZACB 1 ______________________________________________________ | | | Access Code Behavior | | Zone |State|--------------------------------| | ||||| Dialed | New | .
408 Appendix D Off-net dialing plan configur ation example CLTP INTL RLI 1 SDRR NONE ITEI NONE NRS In the NRS database, a Numbering Plan entr y that associates the SPN 101 with the Branch Office endpoint is provisioned.
Call example 409 Branch Office At the MG 1000B Small System Controller , the f ollowing is pro visioned: • DMI = 12 with DEL = 3 to remov e the ZDP digits added in the main office >LD86 REQ PRT.
410 Appendix D Off-net dialing plan configur ation example Main office At the main office Call Ser ver: 1. The call is recognized as originating from a Branch User in Zone 1. 2. Based on the ZACB proper ty , the Call Ser ver recogniz es that the call has been dialed with AC1, and that z one-based digit manipulation must be perf or med.
411 List of terms CDP Coordinated Dialing Plan. Under the recommended Coordinated Dialing Plan, the Branch User ID can be an e xtension (f or example , 4567).
412 List of ter ms same conference e ven though they are using diff erent videoconferencing applications. Although most videoconf erencing vendors hav e announced that their products conf or m to H.323, it is too ear ly to say whether such adherence actually results in interoperability .
List of ter ms 413 IP addresses to unique IP addresses bef ore sending out pack ets. NA T is practical when only a fe w users in a domain need to communicate outside of the domain at the same time. NCS Shor t for Network Connection Ser ver . It provides a TPS interface to the NRS, allowing the TPS to query the NRS using the UNIStim protocol.
414 List of ter ms routing The process of selecting the correct path for pack ets transmitted between IP networks by using software-based algorithms. Each pack et is processed by the algorithm to deter mine its destination. SIP Shor t for Session Initiation Protocol.
List of ter ms 415 of voice streams . The voice gatew ay software can run on an 8- or 32-por t Media Card or the 24-por t ITG-P card. Within the MG 1000B Core, both of these cards register the voice channels to the MG 1000B Small System Controller when they are configured.
416 List of ter ms Nor tel Communication Server 1000 Branch Office Installation and Commissioning NN43001-314 01.02 Standard Release 5.0 20 June 2007 Copyright © 2007, Nor tel Networks .
.
Nor tel Communication Server 1000 Branch Office Installation and Commissioning Copyright © 2007, Nortel Networks All Rights Reser v ed. Publication: NN43001-314 Document status: Standard Document version: 01.02 Document date: 20 June 2007 T o provide feedback or to report a problem with this document, go to w ww .
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Nortel Networks NN43001-314 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Nortel Networks NN43001-314 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Nortel Networks NN43001-314 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Nortel Networks NN43001-314 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Nortel Networks NN43001-314, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Nortel Networks NN43001-314.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Nortel Networks NN43001-314. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Nortel Networks NN43001-314 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
