Check to see if there are far-end block errors. If so, the problem exists with the receive lead on the local end. Contact the TAC for more assistance. Run the show controller e1 EXEC command after each step to check if the controller exhibits any errors. Check to see if the line is in loopback mode from the show controller e1 output.
A received remote alarm means there is an alarm occurring on the line upstream of the equipment connected to the port. Check the linecoding setting on the remote-end equipment. Contact your service provider for the correct settings. Correct any misconfigurations as necessary.
To create a loopback plug, see the section "Performing Hardware Loopback Plug Test," earlier in the chapter. Connect the E1 line to a different port. Perform a hardware loop test as described in the section "Performing Hardware loopback Plug Test". If the problem does not persist, then the fault lies with the one port. The show controller e1 EXEC command provides error messages that can be used to troubleshoot problems. To see if the error counters are increasing, execute the show controller e1 command repeatedly.
The presence of slips on E1 lines indicates a clocking problem. Note: If there are multiple E1s in an access server, only one can be the primary, while the other E1s derive the clock from the primary. In that case, verify that the E1 line designated as the primary clock source is configured correctly. If the interface is not using PPP, then use the encapsulation ppp command in the interface configuration mode to correct it.
When troubleshooting a PRI, you need to determine if the E1 is running cleanly on both ends. If Layer 1 problems have been resolved as described above, consider Layer 2 and Layer 3 problems. Also verify that the E1 is not administratively down. Use the no shutdown command to bring the E1 controller up. Use the debug isdn q command to verify that Layer 2 is stable. The debug isdn q command displays data link layer Layer 2 access procedures that are taking place at the router on the D-channel.
Verify that Layer 2 is stable. If Layer 2 does not appear to be stable, see "Troubleshooting E1 Error Events," earlier in this chapter. If not use the encapsulation ppp command to set encapsulation. Contents Introduction. Troubleshooting Using the show interfaces serial Command. Serial Lines: show interfaces serial Status Line Conditions.
Detailed Information on the show interfaces serial Command. Troubleshooting Using the show controller t1 Command. Troubleshooting Using the show controller e1 Command. Serial x is up, line protocol is up. This is the proper status line condition. No action required.
Serial x is down, line protocol is down DTE mode. Typically indicates that the router is not sensing a CD signal that is, CD is not active. Verify that you are using the proper cable and interface see your hardware installation documentation. Insert a breakout box and check all control leads. Contact your leased-line or other carrier service to see if there is a problem.
Swap faulty parts. If you suspect faulty router hardware, change the serial line to another port. If the connection comes up, the previously connected interface has a problem.
Serial x is up, line protocol is down DTE mode. Put the modem, CSU, or DSU in local loopback mode and use the show interfaces serial command to see if the line protocol comes up. If the line protocol comes up, a telephone company problem or a failed remote router is the likely problem. Verify all cabling. Use the show controllers EXEC command to determine which cable is attached to which interface. Enable the debug serial interface EXEC command. If the line protocol does not come up in local loopback mode and if the output of the debug serial interface EXEC command shows that the keepalive counter is not incrementing, a router hardware problem is likely.
Swap router interface hardware. If the line protocol comes up and the keepalive counter increments, the problem is not in the local router.
If you suspect faulty router hardware, change the serial line to an unused port. Serial x is up, line protocol is down DCE mode. Add the clockrate interface configuration command on the serial interface.
Syntax: clock rate bps Syntax Description: bps -Desired clock rate in bits per second: , , , , , , , , , , , , , , , , , , or See the section "Inverting the Transmit Clock," later in this chapter. Verify that the correct cable is being used. If the line protocol is still down, there is a possible hardware failure or cabling problem.
Insert a breakout box and observe leads. Replace faulty parts as necessary. Serial x is up, line protocol is up looped.
A loop exists in the circuit. The sequence number in the keepalive packet changes to a random number when a loop is initially detected.
If the same random number is returned over the link, a loop exists. Use the show running-config privileged EXEC command to look for any loopback interface configuration command entries. If you find a loopback interface configuration command entry, use the no loopback interface configuration command to remove the loop. If they are, disable manual loopback. If the line protocol comes up, no other action is needed.
If the CSU or DSU is not configured in manual loopback mode, contact the leased-line or other carrier service for line troubleshooting assistance.
Serial x is up, line protocol is down disabled. Troubleshoot the line with a serial analyzer and breakout box. If the problem continues, it is likely that there is a hardware problem. If the problem does not continue, it is likely that there is a telephone company problem. Serial x is administratively down, line protocol is down.
Router configuration includes the shutdown interface configuration command Duplicate IP address. Check the router configuration for the shutdown command. Use the no shutdown interface configuration command to remove the shutdown command. If there are duplicate addresses, resolve the conflict by changing one of the IP addresses.
Input rate to serial interface exceeds bandwidth available on serial link. Minimize periodic broadcast traffic such as routing and SAP updates by using access lists or by other means. For example, to increase the delay between SAP updates, use the ipx sap-interval interface configuration command. Increase the output hold queue size in small increments for instance, 25 percent , using the hold-queue out interface configuration command.
On affected interfaces, turn off fast switching for heavily used protocols. For example, to turn off IP fast switching, enter the no ip route-cache interface configuration command. For the command syntax for other protocols, consult the Cisco IOS configuration guides and command references. Implement priority queuing on slower serial links by configuring priority lists. For information on configuring priority lists, see the Cisco IOS configuration guides and command references.
Input rate exceeds the capacity of the router or input queues exceed the size of output queues. Increase the output queue size on common destination interfaces for the interface that is dropping packets.
Use the hold-queue out interface configuration command. Increase these queues by small increments for instance, 25percent until you no longer see drops in the show interfaces output.
Reduce the input queue size, using the hold-queue in interface configuration command, to force input drops to become output drops. Output drops have less impact on the performance of the router than do input drops. The default input hold queue is 75 packets. Use a serial analyzer to isolate the source of the input errors. If you detect errors, it is likely that there is a hardware problem or a clock mismatch in a device that is external to the router.
Use the loopback and ping tests to isolate the specific problem source. Look for patterns. For example, if errors occur at a consistent interval, they could be related to a periodic function such as the sending of routing updates. Ensure that the line is clean enough for transmission requirements. Shield the cable if necessary. Make sure the cable is within the recommended length-no more than 50 feet Ensure that all devices are properly configured for a common line clock.
Contact your leased-line or other carrier service and have it perform integrity tests on the line. A framing error occurs when a packet does not end on an 8-bit byte boundary for one of the following reasons: Noisy serial line Improperly designed cable; serial cable is too long; the cable from the CSU or DSU to the router is not shielded SCTE mode is not enabled on the DSU; the CSU line clock is incorrectly configured; one of the clocks is configured for local clocking Ones density problem on T1 link incorrect framing or coding specification.
Make certain you are using the correct cable. Ensure that all devices are properly configured to use a common line clock. Aborts indicate an illegal sequence of one bits more than seven in a row.
Make certain the cable is within the recommended length-no more than 50 feet Ensure that all connections are good. Check the hardware at both ends of the link. Lower data rates and see if aborts decrease. Use local and remote loopback tests to determine where aborts are occurring.
See the section "Special Serial Line Tests," later in this chapter. When interface resets are occurring, examine other fields of the show interfaces serial command output to determine the source of the problem. Assuming that an increase in interface resets is being recorded, examine the following fields: If there is a high number of output drops in the show interfaces serial output, see the section "Serial Lines: Increasing Output Drops on Serial Link," earlier in this chapter.
Check the carrier transitions field in the show interfaces serial display. If carrier transitions are high while interface resets are being registered, the problem is likely to be a bad link or bad CSU or DSU. Contact your leased-line or carrier service and swap faulty equipment as necessary. Examine the input errors field in the show interfaces serial display. Contact your leased-line or other carrier service and swap faulty equipment as necessary.
The following problems can result in this symptom: Line interruptions due to an external source such as physical separation of cabling, red or yellow T1 alarms, or lightning striking somewhere along the network Faulty switch, DSU, or router hardware. Check hardware at both ends of the link.
Attach a breakout box or a serial analyzer and test to determine source of problems. If an analyzer or breakout box is unable to identify any external problems, check the router hardware. Determine if the CSUs at both ends agree on the clock source local or line. If the CSUs do not agree, configure them so that they do. Usually the line is the source. If SCTE is not enabled on both ends of the connection, enable it. Make sure that ones density is maintained.
Check with your leased-line provider for information on its framing and coding schemes. If your carrier service uses AMI coding, either invert the transmit clock on both sides of the link or run the DSU in bit-stuff mode.
Cable to router is out of specification. If the cable is longer than 50 feet If the cable is unshielded, replace it with shielded cable. Indicates whether the interface hardware is currently active carrier detect is present or whether it has been taken down by an administrator.
Indicates whether the software processes that handle the line protocol consider the line usable that is, keepalives are successful or whether it has been taken down by an administrator.
Specifies the internet address and subnet mask. Maximum transmission unit of the interface. Indicates the value of the bandwidth parameter that has been configured for the interface in kilobits per second.
The bandwidth parameter is used to compute IGRP metrics only. If the interface is attached to a serial line with a line speed that does not match the default or for T1 and 56 for a standard synchronous serial line , use the bandwidth command to specify the correct line speed for this serial line. Delay of the interface in microseconds. Encapsulation method assigned to the interface. Indicates whether loopback is set.
Indicates whether keepalives are set. Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed. Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
Number of hours, minutes, and seconds or never since the interface was last reset because of a transmission that took too long. When the number of hours in any of the last fields exceeds 24, the number of days and hours is printed. If that field overflows, asterisks are printed. Output queue, drops input queue, drops. Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets because the queue is full. Average number of bits and packets transmitted per second in the past five minutes.
The five-minute input and output rates should be used only as an approximation of traffic per second during a given five-minute period.
These rates are exponentially weighted averages with a time constant of five minutes. A period of four time constants must pass before the average will be within 2 percent of the instantaneous rate of a uniform stream of traffic over that period.
Total number of error-free packets received by the system. Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system. Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events. Total number of broadcast or multicast packets received by the interface.
Enters voice-card configuration mode for the network module on which you want to enable DSP-farm services. This is a known non-service-impacting limitation and does not affect any other behavior. You can record the call by sending a copy of the media streams to the recording server.
When you send a copy of the media streams to the recording server, the TDM gateway acts a session recording client, which uses SIP protocol to communicate the recording metadata with the recording server. This call instance that is created between the recording client and recording server is called the recording session. The recording metadata contains the description of the communication session along with the participants of the call and details of the media streams. The recording session comprises of two media streams forked by DSP, one is the near-end stream that enters into the analog phone, and the other far-end stream that is sent to the IP cloud IP phone in the diagram below.
As the Media Recording feature supports a feature based license, in addition to the existing UC license, you must register to the Smart Licensing portal. Once the feature is registered and the associated license request is granted by the license server, the license is maintained on the gateway. The granted licenses then can be assigned on a per call basis to a analog call that have media recording feature. The media recording session is initiated when a pre-configured set of rules is approved on the telephony leg.
These rules include recording license availability and the recording feature configuration. It is provisioned under the POTS dial-peer which reflects the telephony leg of a call. There are three different basic TDM gateway usecases that can be considered for media recording:. As there is no VoIP component present for this call, you should use the no local-bypass CLI configuration under voice-card so that a VoIP leg is introduced to help facilitate media recording for the call.
Time-division Multiplexing TDM media recording is not supported for the following calls:. Supports limited to basic call scenario for analog endpoints with SIP call control signaling. Multiple destinations recording is not supported.
Current support is limited to one recording server destination per call. Specifies either the prefix or the full E. This is a dummy dial pattern which is not utilized in the actual call routing. Specifies a network-specific address for a dial peer. Keyword and argument are as follows: ipv4: destination address --IP address of the dial peer, in this format: xxx. To enable the voice-port recording license, use the media-recording licenses command in the voice service mode. After you enter the configuration, a static license request is raised and a license request is sent to the server.
The system looks for the license. To view the media recording configuration enabled on dial-peer and media recording license configuration under the global voice service pots mode, use the show voice media-recording command as shown in this example:.
Installing the Cisco Network Interface Module. Configuration guides for different voice and video applications, H. Table 1. Supports 2 channel groups per port. The Ad Hoc and Meet-Me conferencing features are supported a conference can be either of these types : Ad Hoc—The person controlling the conference presses the telephone conference button and adds callers one by one.
Meet-Me—Participants call in to a central number and are joined in a single conference. Participants whose end devices use different codec types are joined in a single conference; no additional transcoding resource is needed.
Table 2. The Cisco Unified Border Element provides the following network-to-network interconnect capabilities: Session Management: Real-time session setup and tear-down services, call admission control, ensuring QoS, routing of calls if an error occurs, statistics, and billing.
Interworking: H. For information on how the H. Dynamic prompts are formed by the underlying system assembling smaller audio prompts and playing them out in sequence. The script uses an API command with a notation form to instruct the system what to play. The underlying system then assembles a sequence of URLs, based on the language selected and audio file locations configured, and plays them in sequence.
These audio files are assembled dynamically by the underlying system and played as a prompt based on the selected language and prompt file locations.
Enables privileged EXEC mode. Enter your password if prompted. Specifies T1 or E1 connectivity for the network interface module. Optional Removes the previous configuration. Exits the card configuration mode and returns to global configuration mode. Boots the router with the configuration for the newly selected card type. Enters controller configuration mode for the network interface module. Valid values for slot is 0, subslot is 1 to 3, and port is 0 or 1. Note When using linecode AMI, we recommend that you select 56 kbps as the speed or make sure that the channel groups created do not contain all the timeslots.
See step The options are as follows: internal—Sets the controller framer as the clock master. Sets the line termination on an E1 controller. Sets the loopback method for testing the interface. Options are: diagnostic —Loops the transmit signal back to receive. Loss values are: 0db When you use the cablelength short command, specify the length as follows: for cable lengths from 0 to feet for cable lengths from to feet for cable lengths from to feet for cable lengths from to feet for cable lengths from to feet for cable lengths from to feet There is no default cable length.
For T1, values are as follows: channel-group-number is from 0 to Default value of speed for T1 is 64 kbps. Configuration of speed is optional. For E1, values are as follows: channel-group-number is from 0 to Default value of speed for E1 is 64 kbps.
The interval time is from 1 to 14, minutes. Router show running-config Building configuration Current configuration : bytes! Enters voice card interface configuration mode. Specify the slot location using a value from 0 to 5.
Note All medium-complexity codecs are supported in high-complexity codecs. This procedure to change codec complexity applies only to T1 and E1 controllers. This procedure is not valid for analog voice ports. Exits voice card configuration mode and returns to global configuration mode. Specifies a frame type. Specifies a line encoding for a controller. Note The group numbers for controller groups must be unique. Enters voice port configuration mode and specifies the voice port.
For T1, timeslots range from 1 to 24 23rd channel is the D channel For E1, timeslots range from 1 to 31 15th channel is the D channel Note The isdn incoming-voice voice command is not required for interface serial interface configuration. Default is without the keyword voice-dsp. Router sh run Building configuration Enables DSP-farm services for the voice card. Loopback testing is a very effective way to isolate a failing T1 or E1. The basic idea behind loopback testing is:. The components you should try to eliminate as problematic include the VWIC card and port and the cable run up to the SmartJack.
A very common capability provided by a SmartJack is loopback, where the signal from the telco is transmitted back to the telco. Telcos consider everything connected to the inside of the SmartJack as the local loop and consider all local loop equipment the responsibility of the customer.
This figure illustrates a SmartJack. Note : Soft loopback is intrusive and will impact service. Soft loopback does not require any hardware changes or re-configuration, as shown in this figure. Note : Hard loopback tests are intrusive and will impact service. In a hard loopback, a special loopback plug is used in order to loop the traffic from the T1 port back into the T1 port. This figure illustrates the setup for hard loopback. ISDN Layer1 can be tested. If the VWIC is working correctly, the show controller t1 command produces output similar to that shown in this example:.
ISDN Layer 2 can be partially tested. Instead, you see this type of output:. This is expected. For the ISDN interface to work, one side must be configured as a protocol network, and the other side as a protocol user. However, this is not possible since there is only one interface with the loopback. One advantage of this approach however, is that no configuration change is required on the Cisco IOS software. The only procedure is:. Use the show controller t1 command in order to verify that the T1 controller comes up, and use the debug isdn q9 21 command in order to verify the flow of Q.
ISDN Layer 3 is, of course, not possible. The other approach, test as an IP interface, is also known as "test as a data T1. Therefore, only testing as an IP interface is possible.
Once the configuration steps are complete, perform ICMP pings:. Check the interface counters in order to verify that the count for 'packets input' and 'packets output' increments. Note : Perform an extended ping in order to test for possible flapping conditions. Once you determine that the VWIC is working correctly, use this procedure to test and eliminate the cable run to the telco demarc as the source of problems:.
If the ICMP pings are successful, the test is succesful, which indicates that the cable is fine. If there are cuts or other damages to the cable run, you see that the T1 controller stays down, caused by the loss of signal LOS :.
Note : Non-zero line and path code violations do not necessarily indicate problems with the cable.
0コメント