Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 149
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2
January 1998
Responding to Alarms and Errors
Page 5-19 Fiber Fault Isolation Procedure
5
nAfter replacing an SNI circuit pack, clear alarms by executing test
board UUCSSlong clear for all alarmed EXP-INTF circuit packs.
Wait 5 minutes for any SNI-BD or SNI-PEER alarms to clear. (You
can speed this process with clear firmware counters [a-pnc |
b-pnc] for the PNC that was repaired).
nExit this...](http://img.usermanuals.tech/thumb/3002/85165/w64_definity-ecs-r6-maintenance-for-r6r_d-148.png "Page 149
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2
January 1998
Responding to Alarms and Errors
Page 5-19 Fiber Fault Isolation Procedure
5
nAfter replacing an SNI circuit pack, clear alarms by executing test
board UUCSSlong clear for all alarmed EXP-INTF circuit packs.
Wait 5 minutes for any SNI-BD or SNI-PEER alarms to clear. (You
can speed this process with clear firmware counters [a-pnc |
b-pnc] for the PNC that was repaired).
nExit this...")
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-21 Fiber Fault Isolation Procedure 5 distances up to 4900 feet (1493 m) and 9823B is used for distances up to 25,000 feet (7620 m)). If No Ê Is a DS1 CONV administered on the fiber-link? If no, follow normal escalation procedures. If Yes Ê Is there an SNI-BD 513 alarmed error (display errors for category pnc)? If yes, replace cabling between the SNI circuit pack and the DS1C circuit pack. If the alarm persists, replace the DS1C and the SNI circuit packs. Go back to step 4. If No Ê If the connected circuit pack is an EXP-INTF, did test 238 fail? If yes, replace cabling between the EXP-INTF circuit pack and the DS1C circuit pack. If test 238 continues to fail, replace the DS1C and the EXP-INTF circuit packs. Go back to step 4. If No Ê Busyout and test board UUCSS long for both DS1C circuit packs and note all test failures and aborts. Ê Did the test return Board not inserted for the near-end circuit pack (nearest the SPE), or for the far-end circuit pack in a simplex PNC? If so, replace the cabling between the DS1C circuit pack and the SNI or EXP-INTF circuit pack. Wait 1 minute and retest. If the board is still not inserted, replace the DS1C circuit pack and the EXP-INTF or SNI connected to it. Go back to step 4. If No Ê Check to see if any of the CSU devices are looped back. Busyout and test ds1-facility UUCSS external-loop for each DS1 facility.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-22 Fiber Fault Isolation Procedure 5 The tests should fail. If any test passes, the facility is looped back, and the loopback should be removed. If the DS1C Complex has only one DS1 facility, this test cannot be executed at the far-end circuit pack (farthest from the SPE). Ê Did test 788 pass and test 789 fail? If yes, replace the DS1C and lightwave transceiver (if present) at the other end of the DS1C complex. (See Figure 5-4 and Figure 5-5.) Go back to step 4. If No Ê Did test 788 fail or abort and test 789 fail or abort? If yes, execute test ds1-facility UUCSS long command for each administered and equipped DS1 facility. If No Ê Did test 797 fail? If yes, run the test ds1-facility UUCSS external-loopback command for each administered and equipped DS1 facility. This test requires manually altering the external connections of the DS1 facility. Place the loopbacks at as many points as your CSU capabilities will allow (see Figure 5-5 ). nIf test 799 fails at LB1, problem is with DS1C #1, CSU #1, or the connections in between. nIf test 799 passes at LB1 and fails at LB2, the problem is with CSU #1. nIf test 799 passes at LB1 and at LB2, the problem is with the DS1 facility, CSU #2, connections to CSU #2, or DS1C #2. SNI/EI Manual Loop Back Procedure Use this procedure to isolate a fault in the cables or lightwave transceivers of SNI/EI links. (Do not use this procedure on a connection with a DS1C as an endpoint.) By performing the loopback at both endpoints and, if applicable, at the cross-connect field, the failure point can be identified. If both endpoints pass, but the link remains inactive (with the boards not busied out), the fault should lie in the cabling in between. If the test passes at a transceiver, but fails at the cross-connect field, the cable or connectors in between are at fault.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-23 Fiber Fault Isolation Procedure 5 A short optical fiber jumper with connectors is required for this procedure. If the link uses metallic cable, the metallic connector must be removed from the back of the carrier, and a lightwave transceiver connected in its place. 1. Note the condition of the yellow LED on the circuit pack. 2. Busyout the circuit pack. 3. Disconnect the transmit and receive fiber pair from the lightwave transceiver on the back of the circuit pack. Note which is the transmit fiber and which is the receive fiber for proper re-connection at the end of this procedure. 4. Connect the transmit and receive jacks of the lightwave transceiver with the jumper cable. NOTE: Make sure that the total length of the fiber jumper cable does not exceed the maximum length recommended for the fiber link connections between cabinets. Otherwise, test results may be influenced by violation of connectivity guidelines. 5. At the front of the cabinet, observe the yellow LED on the looped back circuit pack. nIf the yellow LED flashes once per second, the circuit pack or transceiver should be replaced. nIf the yellow LED flashes five times per second, the circuit pack or its lightwave transceiver may need replacement. This condition may also be due to a faulty system clock on the port network (for an EI) or the switch node carrier (for an SNI). nIf the yellow LED was flashing before starting this procedure, and it is now either solid on or solid off, this circuit pack and its lightwave transceiver are functioning properly. 6. Replace the faulty component(s) and reconnect the original cables in their correct positions. Be sure to use a lightwave transceiver that matches the one at the opposite end. 7. Release the circuit pack. Loopback Tests Run for Fiber Fault Isolation Procedure Figure 5-5 shows the loopbacks performed on the SNI circuit pack for test 756 and test 757. Test 756 reports the result of the off-board loopback; test 757 reports the result of the on-board loopback. Test 756 and test 757 can run individually or as part of the test board UUCSS long command for an SNI circuit pack. Test 242 can be run as part of the test board UUCSS long command for an Expansion Interface circuit pack. Besides testing on-board components, this test
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-24 Fiber Fault Isolation Procedure 5 is helpful for isolating problems between a circuit pack and the lightwave transceiver. The loopback shown in this diagram shows only part what test 242 does. If no lightwave transceiver is connected to the Expansion Interface circuit pack, an on-board loopback is performed on the Expansion Interface circuit pack. For more information about test 242, see the ‘‘ EXP-INTF (Expansion Interface Circuit Pack)’’ section in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. Figure 5-4. Fiber Fault Isolation Tests If DS1Cs exist on the fiber link (check with list fiber-link), then additional DS1CONV loopback tests can be run to further isolate the problem. The loopback tests are shown in Figure 5-5 . For more information about loopback tests 788 and 789, see the ‘‘ DS1 CONV-BD’’ section in Chapter 9, ‘‘Maintenance Object Repair Procedures’’. For more information about DS1 facility loopback tests 797 and 799, see the ‘‘ DS1-FAC (DS1 Facility)’’ section. Figure 5-5. DS1 CONV Loopbacks Tone Clock Tone DetectorTest #242 ®ber-optic cableTDM BUSback skin of cabinet lightwave transceivers TN753 Switch Node Interface Test #757 Test #756 TN570 Expansion Interface back skin of cabinet Test #989 (framing)Test #238 (framing) Tests 788, 780, 797, and 799 start here: . . . . . . . . . . . . . . . . . . . Test 797 loops at internal interface for the DS1 facility Test 789 loops here Test 788 loops here lightwave transceiver DS1 Facility CSU 2DS1C 2 CSU 1 DS1C 1Test 799 LB 1Test 799 LB 2
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-25 Fiber Fault Isolation Procedure 5 Table 5-2 shows the pin assignments for the cable used to connect the TN574 DS1 CONV circuit pack to DS1 facilities. Table 5-2. DS1 Interface Cable Connectors Lead Desig.50-Pin Connector Pin15-Pin Connector Color Pin Color Plug 04 Facility D Line In LID 38 W-BL 11 W-BL Facility D Line In LID* 13 BL-W 03 BL-W Facility D Line Out LOD 39 W-O 09 W-O Facility D Line Out LOD* 14 O-W 01 O-W Plug 03 Facility C Line In LIC 41 W-G 11 W-G Facility C Line In LIC* 16 G-W 03 G-W Facility C Line Out LOC 42 W-BR 09 W-BR Facility C Line Out LOC* 17 BR-W 01 BR-W Plug 02 Facility B Line In LIB 44 W-S 11 W-S Facility B Line In LIB* 19 S-W 03 S-W Facility B Line Out LOB 45 R-BL 09 R-BL Facility B Line Out LOB* 20 BL-R 01 BL-R Plug 01 Facility A Line In LIA 47 R-O 11 R-O Facility A Line In LIA* 22 O-R 03 O-R Facility A Line Out LOA 48 R-G 09 R-G Facility A Line Out LOA* 23 G-R 01 G-R
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-26 Multimedia Call Handling (MMCH) 5 Multimedia Call Handling (MMCH) Enhancements Expansion Services Module The Expansion Services Module (ESM) provides T.120 data sharing capability on a MMCH multipoint H.320 video conference. Each conference participant must have endpoints administered and a personal computer with the H.320 video application installed. The DEFINITY ECS must have the expansion service module installed. Figure 5-6. Typical ESM connections Figure Notes !CAUTION: The TN2207 circuit pack is the only pack allowing connection of an ESM to the DEFINITY ECS switch. Troubleshooting Before troubleshooting any problems associated with the DEFINITY MMCH, always be sure that the endpoint is operating correctly (audio, video, and data) by making point-to-point test calls. If possible, make the test calls over the 1. Port B Y-cable connector to a TN787 Multimedia Interface (MMI) circuit pack 2. Port A Y-cable connector to a TN2207 PRI circuit pack 3. 25-pair Y-cable 4. 356A adapter5. D8W cord connected to 356A adapter port 1 6. Expansion Service Module (ESM) 7. Port B on compatible primary rate interface (PRI) card cydf012 RPY 100697 12 4 53 6 7
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-27 Multimedia Call Handling (MMCH) 5 network to test the connectivity and routing of network calls from the endpoint. This eliminates problems such as disconnected audio or video cables and network troubles. 64 Kbps Calls Terminate but Far End Receives 56 Kbps Indication Description Some 2x64 Kbps conferences on the DEFINITY MMCH do not establish because of framing, audio, or video problems. For calls that are routed in the network through a Lucent Technologies/LEC interface, the originating equipment may launch a 64 Kbps call attempt, and the far end receives either a 56 Kbps or 64 Kbps indication. If the far end receives a 64 Kbps indication, the call may have used 56 Kbps facilities. If so, the call may exhibit any of the following conditions: nNo handshaking in one direction or both (call disconnects after timeouts) nCall connects, but audio or video is corrupted (audio noise or no video) nCall succeeds without disruption (this is the least likely since one endpoint must be aware that the call is really 56 Kbps to connect) If any of the above conditions occur, then 64 Kbps calls from the site are blocked. Solution Administer the conference for connection at 56 Kbps. Calls Terminate with No Audio Description To support endpoints that do not support Multipoint Command Conference (MCC), the DEFINITY MMCH changes its capability set and initiates a capability set exchange with the endpoint when the Selected Communications Mode (SCM) changes. If the endpoint does not follow the SCM audio mode, the MCU may include the endpoint as a secondary (audio only) endpoint. If the endpoint sends an unknown or unsupported audio mode, then the TN788B decoder port mutes the endpoint from the conference. The user may hear the conference but may not be heard by other parties in the conference. Solution 1. Use the Status Conference x form and check the Audio Mode field for the current operating mode of the conference.
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-28 Multimedia Call Handling (MMCH) 5 2.Another indication of the audio modes is in the “Incoming Mode Commands from Endpoint and Outgoing Commands from MMI” on page 3 of the Status Conference x Endpoint y form. Check the Audio fields under the Mode Commands/Communication Modes section of the form. Some Parties Cannot Be Heard by Others (Audio Subsetting) Description Problems where varying subsets of the conference hear different things may have problems with the various summing resources/groups that are in use. Traditionally theses faults are caused by the SPE not cleaning up the connections properly. Isolation and diagnosis should focus on the VC resources in use by that conference. Solution 1. Use the status conference command to list the VC resources in use by this conference. Try a hot replacement of any VC boards in use, which refreshes the VC translations and move all of the audio connections to different VC ports. 2. If the problem still exists, try dropping the conference and then bringing the conference back up again. Not only does this refresh VC translations, but uses different timeslots as well. 3. If the problem still exists, suspect a hardware problem. If practical, wait for the DEFINITY MMCH to be idle (no active conferences), and then check the circuit packs for active (yellow) LEDs. If any of these are unexpected, such as on a VC board, try replacing the board and then bringing the conference up again. Calls Terminate with No Video Description Generally, loss of video can be divided into 2 types. The first occurs when the DEFINITY MMCH switches to the endpoint, but nobody sees them. The receivers see either “black” video or a frozen image of the previous speaker depending on the codec of the manufacturer. The type occurs when the DEFINITY MMCH does not switch to an endpoint. Solution In the first type described above, wiring problems, power to the camera, or video encoder circuit pack problems in the codec are typical causes. In the second type, no video from an endpoint typically occurs because it is not a valid video source. This can be checked by looking at page 1 of the Status Conference x Endpoint y Vid form under the Capability section. In this section, a
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-29 Multimedia Call Handling (MMCH) 5 “y” or “c” suggests that the endpoint has video. An “e” means ept has not declared any video capability in cap set, “n” is audio only, and “blank” means audio add-on. Also check page 1 of the Status Conference x Endpoint y Vs form for indication of the video state for the endpoint values. Calls Terminate Correctly but Are Unstable A number of conditions will lead to some or all endpoints having stability problems during the course of a conference. A lack of stability from an endpoint is noticeable by a lack of a video switching while the party is the only talker or excessive disconnects from that endpoint. Synchronization Generally, the most common problem is a mismatch in synchronization sources between the endpoint and the DEFINITY MMCH. This typically causes low-level (Px64) handshake problems that can trigger the endpoint/MMCH to disconnect the call. The MCCH’s timers are set to sufficiently high values so that, normally, the endpoint will timeout and disconnect first. If installed in a customer network, it is a good idea to perform an audit of the path synchronization is being supplied. If there are different clock sources between endpoints and the DEFINITY MMCH, some problems are sure to occur. The severity of these problems can range from a handshake failure every few seconds to one per day. Depending on the type of endpoint, this can cause the endpoint to disconnect or just freeze video until the main problem is resolved. Specifically, PictureTel System 4000 endpoints seem to be the most sensitive to instability. The Lucent Technologies Vistium also disconnects fairly infrequently. Last, the CLI Rembrandt II VP freezes video and waits for framing to be recovered. Network Configuration Concerns with Synchronization When auditing a network for synchronization, avoid unnecessary hops. Thus, a switch providing star-configuration synchronization is preferred over a daisy-chain configuration. Additionally, if there are DEFINITY PBXs that have EPNs, synchronization should be provided to sub nodes from the same port network through which the PBX receives its synchronization. Passing synchronization through the PBX Expansion Interface adds an unnecessary hop to the path and creates another potential point of failure. Expansion Interface Duplication If a customer’s network uses PBX EPNs with duplicated Expansion Interfaces, scheduled switching of the Expansion Interface links should be disabled on the PBX via change system-parameters maintenance. When scheduled maintenance runs and switches the links, there is a brief corruption of the data path. If endpoints have active calls when the switch occurs, this corruption of the data path causes Px64 handshake problems, which lead to the endpoints losing
DEFINITY Enterprise Communications Server Release 6 Maintenance for R6r Volumes 1 & 2 555-230-126 Issue 2 January 1998 Responding to Alarms and Errors Page 5-30 Multimedia Call Handling (MMCH) 5 video source status, and sometimes disconnecting as described above. Disabling the EI switching is in the customer’s best interest to prevent the disruption of the Px64 data stream. The customer will get the same level of alarm indications and maintenance on the EI links, regardless of the status of scheduled switching. PRI D-Channel Backup A somewhat unlikely source of call stability problems occur where the translations for PRI D-channel Backup between two non-MCU switches were incorrect. As an example, on switch A, DS1 1A10 was designated as the primary source, and on switch B, the corresponding DS1 was designated as the secondary source. When scheduled maintenance was run on the switch that had an active standby D-channel, an audit disconnected some calls using the link. The problem was corrected when the the D-channel primary/secondary assignments matched. Processor Duplication on the PBX Do not enable the PI link switch on scheduled maintenance. This can cause link stability problems on the Accunet Bandwidth Controller (ABC). Voice-Activated Switching Problems Voice-activated switching on the DEFINITY MMCH does not follow the loudest talker. The MMCH queues all speaking parties and selects a new video broadcaster (the second-oldest speaking party) when the oldest speaking party has stopped talking. The new broadcaster will see the last speaker as its video. The system can also “learn” about the noise coming from an endpoint to help prevent false switches, adapting both to noise level and repetitive sounds such as a fan. This adaptation occurs over approximately 10 seconds. No Switching, Full Motion Video If a room is excessively noisy, the DEFINITY MMCH may receive sufficient audio signal to conclude that there is a speaker present. Use the Status Conference x form to determine if the MMCH thinks an endpoint is talking. The MMCH sets the Ts field to t for each endpoint if there is voice energy detected. This endpoint may have to mute when nobody at the site is speaking to allow the conference to proceed normally. Remind the customer that it may be necessary to mute if a side conversation is going on in the background, just as one would do in an audio conference. If the system does not switch broadcasters even after the current broadcaster has muted, check the conference administration using the display conference X command to ensure that the conference is in voice-activated mode. Also verify that parties who were speaking are valid video sources as described in the “Calls Terminate with No Video ” section above. The See-Me feature (MCV) can also cause VAS to “lock-up.” An endpoint can activate MCV to force their site to become the broadcaster. If they do not disable the feature when finished, the system remains in this mode indefinitely.