AudioCodes MediaPack MP-11 Series Troubleshooting Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Gateway
  5. MP-11
  6. Troubleshooting manual

AudioCodes MediaPack MP-11 Series Troubleshooting Manual

Cpe
Hide thumbs Also See for MediaPack MP-11 Series:
Table of Contents

Advertisement

Quick Links

See also: User Manual , Installation Manual
CPE Troubleshooting Guide
Document #: LTRT-57601
January 2009

Advertisement

Table of Contents
loading

Related Manuals for AudioCodes MediaPack MP-11 Series

Summary of Contents for AudioCodes MediaPack MP-11 Series

  • Page 1 CPE Troubleshooting Guide Document #: LTRT-57601 January 2009...

  • Page 3: Table Of Contents

    Troubleshooting Guide Contents Contents   Introduction ......................7   IP Connectivity ....................9     2.1  I Cannot Access Web or Ping the Device ..............9  2.2  How Do I Ping a Network Entity from the Device ........... 10    TDM (PSTN) Connectivity ................
  • Page 4 MediaPack, Mediant 1000, Mediant 2000 Fax and Modem ....................51     8.1  Why Do Fax Sessions Fail ..................51  Call Transfer...................... 55     9.1  Why Does PBX Terminate Call Transfer by the FXO Device ......... 55  9.2  Why Can't I Transfer a Call Between FXS Interfaces ..........56 ...

  • Page 5: Weee Eu Directive

    IPmedia, Mediant, MediaPack, MP-MLQ, NetCoder, Netrake, Nuera, Open Solutions Network, OSN, Stretto, 3GX, TrunkPack, VoicePacketizer, VoIPerfect, What's Inside Matters, Your Gateway To VoIP, are trademarks or registered trademarks of AudioCodes Limited. All other products or trademarks are property of their respective owners.
  • Page 6 MediaPack, Mediant 1000, Mediant 2000 Reader’s Notes Troubleshooting Guide Document #: LTRT-57601...

  • Page 7: Introduction

    Introduction This guide is intended to assist you in troubleshooting various problems that may arise in your network environment in which AudioCodes' VoIP gateway (hereafter referred to as device) is deployed. This guide includes troubleshooting concerning the following AudioCodes SIP CPE devices:...
  • Page 8 MediaPack, Mediant 1000, Mediant 2000 Reader’s Notes Troubleshooting Guide Document #: LTRT-57601...

  • Page 9: Ip Connectivity

    Troubleshooting Guide 2. IP Connectivity IP Connectivity This section discusses troubleshooting for IP connectivity problems: ''I Cannot Access Web or Ping the Device'' on page ''How Do I Ping a Network Entity from the Device'' on page I Cannot Access Web or Ping the Device Table 2-1: No Web Access or Ping to the Device Troubleshooting Possible Cause Solution...

  • Page 10: How Do I Ping A Network Entity From The Device

    MediaPack, Mediant 1000, Mediant 2000 Possible Cause Solution The IP address assigned to the Discover the device's IP address: The simplest method device is not suitable for your is to start the Wireshark application (refer to ''Wireshark network environment, or the Network Sniffer'' on page 69), reset the device and wait device's IP address is unknown for it to startup.
  • Page 11 Troubleshooting Guide 2. IP Connectivity In the 'Command-Line' field, enter the following command: ping [IP address of the remote destination] For example, ping 10.33.2.34. Wait several seconds and then enter the following command: show ping The following information is displayed: ping 10.33.2.34 Ping process started for address 10.33.2.34.
  • Page 12 MediaPack, Mediant 1000, Mediant 2000 Reader’s Notes Troubleshooting Guide Document #: LTRT-57601...

  • Page 13: Tdm (Pstn) Connectivity

    Troubleshooting Guide 3. TDM (PSTN) Connectivity TDM (PSTN) Connectivity This section discusses troubleshooting for TDM (PSTN) connectivity: ''How Do I Clear Trunk Alarms'' on page ''How Do I Check a Trunk's Physical Integrity'' on page ''How Do I Check for E1/T1 Clock Slips'' on page ''How Do I Switch Between E1 and T1 Trunk Protocol Types'' on page ''Why Can't I Stop an Active Trunk'' on page How Do I Clear Trunk Alarms...
  • Page 14 Framing method on the PBX/PSTN. If the D-channel alarm isn’t cleared, contact the AudioCodes Technical Support team and provide them with the ini file of the device and a PSTN trace (refer to ''CLI Debug Recording'' on page 72).

  • Page 15: How Do I Check A Trunk's Physical Integrity

    Troubleshooting Guide 3. TDM (PSTN) Connectivity How Do I Check a Trunk's Physical Integrity To check the trunks physical integrity (no hardware problem), perform the following test: Use a crossover RJ-48 cable to make a loop between two active Trunks on the device. In the Web interface's ‘Trunk Settings’...

  • Page 16: How Do I Switch Between E1 And T1 Trunk Protocol Types

    MediaPack, Mediant 1000, Mediant 2000 Below is an example of the CLI output when using these commands: pstn CAS/ PHysical/ PstnCOmmon/ /PStn> physical IsdnGetDChannelStatus PstnQueryTrunkStatus PstnSendAlarm PstnLoopCommands PstnGetPerformanceMonitoring PstnStoPPerformanceMonitoring PstnStarTPerformanceMonitoring /PStn/PHysical> PstnGetPerformanceMonitoring 0 0 TrunkId = 0 Interval = 0 How Do I Switch Between E1 and T1 Trunk Protocol Types To switch from E1 to T1 (or vice versa):...

  • Page 17: Why Can't I Stop An Active Trunk

    Troubleshooting Guide 3. TDM (PSTN) Connectivity Why Can't I Stop an Active Trunk Table 3-2: Active Trunk Can't be Stopped Troubleshooting Possible Cause Solution The Trunk provides the device's When the clock source is internal (i.e., the device receives clock. clock synchronization from a specific Trunk), you cannot stop this Trunk (assuming that the device is synchronized with the E1/T1 clock).
  • Page 18 MediaPack, Mediant 1000, Mediant 2000 For all Trunks, set the ini file parameter ClockMaster to 1 (or the corresponding Web interface parameter 'Clock Master ' to "Recovered"). This parameter determines the Tx clock source of the E1/T1 lines. Figure 3-2: Clock Synchronization from Device To use the recovered clock option: Set the ini file parameter TDMBusClockSource to 4 (or the corresponding Web interface parameter 'TDM Bus Clock Source' to "Network").

  • Page 19: Call Setup

    Troubleshooting Guide 4. Call Setup Call Setup This section discusses troubleshooting for call setup (or call establishment): ''How Do I Troubleshoot IP-to-Tel Call Setup'' on page ''How Do I Troubleshoot Tel-to-IP Call Setup'' on page How Do I Troubleshoot IP-to-Tel Call Setup This sections deals with troubleshooting for IP-to-Tel call setup: ''Initial IP-to-Tel Troubleshooting'' on page ''Advanced IP-to-Tel Troubleshooting for Digital Interfaces'' on page...

  • Page 20: Initial Ip-To-Tel Troubleshooting

    MediaPack, Mediant 1000, Mediant 2000 4.1.1 Initial IP-to-Tel Troubleshooting Table 4-1: Initial Troubleshooting for IP-to-Tel Call Setup Possible Cause Solution The ports/Trunks/B-channels Ensure that the ports, Trunks, or B-channels involved in the are not defined. call are defined (enabled) for the device. This is performed in the Web interface: For digital devices: 'Trunk Group Table' page (Web path SW Ver.
  • Page 21 Troubleshooting Guide 4. Call Setup Possible Cause Solution The device does not receive a If no SIP INVITE message is received from the remote UA, SIP INVITE message from the notify the problem to the remote UA. remote UA. To check whether the device receives SIP INVITE messages: Make an IP call to the device from the remote UA.
  • Page 22 MediaPack, Mediant 1000, Mediant 2000 Possible Cause Solution The remote peer is operating Verify that the SIP INVITE message received by the device behind NAT. contains the public IP address of the remote peer. If the remote peer uses an internal IP address, contact the Firewall/NAT server administrator to verify that the remote peer uses and declares its public IP address.

  • Page 23: Advanced Ip-To-Tel Troubleshooting For Digital Interfaces

    Ensure that the following Syslog message is displayed: pstn send --> PlaceCall: pstn send --> PlaceCall: Trunk: Trunk: message If the message doesn’t appear, contact AudioCodes Technical Support team and provide them with the following information: The device's ini file A debug-level 5 Syslog trace No response from the PBX.

  • Page 24: Advanced Ip-To-Tel Troubleshooting For Fxs Interfaces

    The phone is securely connected to the device's designated FXS port. The relevant channel LED is flashing. If the LED is not flashing, contact AudioCodes Technical Support team and provide the following information: The device's ini file A debug-level 5 Syslog trace...

  • Page 25: Advanced Ip-To-Tel Troubleshooting For Fxo Interfaces (1-Stage Dialing)

    If this message does not appear, ensure that the physical FXO trunk line is securely connected between the device and PBX. If this message still does not appear, send the Syslog trace and the device's ini file to AudioCodes Technical Support team. The device does not detect a In the Syslog, check if the following message appears: dial tone from the PBX.
  • Page 26 If it is set to 0, the device immediately sends 200 OK messages after the device completes dialing to the Tel side. If the problem persists despite all the previous troubleshooting, send the AudioCodes Technical Support team the following information: The device's ini file A Syslog trace...

  • Page 27: Advanced Ip-To-Tel Troubleshooting For Fxo Interfaces (2-Stage Dialing)

    If this message does not appear, ensure that the physical FXO trunk line is securely connected between the device and PBX. If this message still does not appear, send the Syslog trace and the device's ini file to AudioCodes Technical Support team. The FXO interface does not...

  • Page 28: How Do I Troubleshoot Tel-To-Ip Call Setup

    MediaPack, Mediant 1000, Mediant 2000 How Do I Troubleshoot Tel-to-IP Call Setup The sections deals with troubleshooting for Tel-to-IP call setup: ''How Do I Check Device (Tel-to-IP) Connectivity'' on page ''Initial Tel-to-IP Troubleshooting'' on page ''Advanced Tel-to-IP Troubleshooting for Digital interfaces'' on page ''Advanced Tel-to-IP Troubleshooting for FXO Interfaces'' on page ''Advanced Tel-to-IP Troubleshooting'' on page ''Why is there a Delay in Connecting a Call'' on page...
  • Page 29 Troubleshooting Guide 4. Call Setup Possible Cause Solution When a Proxy server isn’t used, the destination IP address must be defined in the Web interface's 'Tel to IP Routing' page (Web path SW Ver. 5.2: Protocol Management menu > Routing Tables submenu > Tel to IP Routing; Web path SW Ver.
  • Page 30 MediaPack, Mediant 1000, Mediant 2000 Possible Cause Solution The device is operating behind Verify that public IP address declared for the device NAT (a STUN server is appears in the SDP of the SIP INVITE message as available). assigned to the device by the STUN server. Verify that the device is enabled to use a STUN server ('Enable STUN' parameter) and that its' IP address ('STUN Server Primary IP and/or 'STUN Server...
  • Page 31 Troubleshooting Guide 4. Call Setup Possible Cause Solution International numbers - 9 for dialing tone, 011 is the Country Code, and then any number of digits for the local number ('x.'). Note: For BRI/PRI interfaces, the digitmap mechanism is applicable only when ISDN Overlap dialing is used (ISDNRxOverlap is set to 1).

  • Page 32: Advanced Tel-To-Ip Troubleshooting For Digital Interfaces

    MediaPack, Mediant 1000, Mediant 2000 4.2.2.3 Why No Response from Dialing Digits (DTMF) During a Call A common issue is that during an active call, you may be required to press digits (touch- tone dialing) such as in IVR applications, but no response occurs. For example, when accessing your voice mail you need to enter (press) the digits of your account number or PIN.
  • Page 33 Troubleshooting Guide 4. Call Setup Possible Cause Solution The PBX is configured to The device sends a SIP INVITE message only after the operate in overlap dialing while complete number is received from the PBX. The PBX should the device is configured to en- indicate that the whole number has been sent, by including bloc dialing.

  • Page 34: Advanced Tel-To-Ip Troubleshooting For Fxo Interfaces

    MediaPack, Mediant 1000, Mediant 2000 4.2.4 Advanced Tel-to-IP Troubleshooting for FXO Interfaces Table 4-10: Tel-to-IP Call Setup Troubleshooting - FXO Interfaces Possible Cause Solution The PSTN ringing signal from Verify that the physical PBX trunk line connection is correct, the PBX is not received by the by performing the following: device due to incorrect physical Enable Syslog.
  • Page 35 Troubleshooting Guide 4. Call Setup Possible Cause Solution The CPT file does not include a If you are not implementing Automatic Dialing, you should dial tone entry when Automatic hear a dial tone and then dial the destination number. Dialing is not used. Open the Syslog and verify that the following messages appear: 18:19:59.383: 10.15.6.1: NOTICE:...

  • Page 36: Advanced Tel-To-Ip Troubleshooting

    Tel side (telephone/PBX/PSTN). Send the Syslog Debug Level 5 trace and the device's ini file to AudioCodes Technical Support team. If the SIP INVITE message appears in the Syslog, verify that the IP address displayed in the “Outgoing SIP Message to“...
  • Page 37 Troubleshooting Guide 4. Call Setup Possible Cause Solution The device receives a SIP 415 If the response from the remote UA for the INVITE is "415 response from the remote IP Unsupported Media Type", then the media type contained in the INVITE request is not supported.
  • Page 38 MediaPack, Mediant 1000, Mediant 2000 Reader’s Notes Troubleshooting Guide Document #: LTRT-57601...

  • Page 39: Caller Id

    Troubleshooting Guide 5. Caller ID Caller ID This section discusses troubleshooting for caller ID: ''Why Doesn't the FXO Device Detect Caller ID'' on page ''Why Doesn't the Phone Detect Caller ID (FXS)'' on page ''Why Doesn't Digital Device Detect Tel-to-IP Caller ID'' on page ''Why Doesn't Digital Device Generate Caller ID to Tel'' on page Why Doesn't the FXO Device Detect Caller ID The troubleshooting information below is relevant to FXO devices that do not detect the...
  • Page 40 If the FXO device still does not detect the caller ID signal that is sent by the PBX, record the signal using the procedure below and send it to AudioCodes Technical Support (along with the ini file and a debug level 5 Syslog trace).

  • Page 41: Why Doesn't The Phone Detect Caller Id (Fxs)

    FXO Device Detect Caller ID'' on page for recording the caller ID signal sent by the PBX to the FXO) and send it to AudioCodes Technical Support (along with the ini file and a debug-level 5 Syslog trace). Version 5.2/5.4...

  • Page 42: Why Doesn't Digital Device Detect Tel-To-Ip Caller Id

    MediaPack, Mediant 1000, Mediant 2000 Why Doesn't Digital Device Detect Tel-to-IP Caller ID Table 5-3: Device Doesn't Detect Caller ID from PBX Troubleshooting Possible Cause Solution The device does not receive Verify that the device receives Caller ID and presentation Caller ID and presentation permission from the PBX.

  • Page 43: Voice Quality

    Troubleshooting Guide 6. Voice Quality Voice Quality This section discusses troubleshooting for voice quality: ''How Do I Troubleshoot Distorted Voice'' on page ''How Do I Troubleshoot Voice Echo'' on page ''How Do I Troubleshoot Voice Delay'' on page How Do I Troubleshoot Distorted Voice Table 6-1: Distorted Voice Troubleshooting Possible Cause Solution...

  • Page 44: How Do I Troubleshoot Voice Echo

    MediaPack, Mediant 1000, Mediant 2000 How Do I Troubleshoot Voice Echo Before you start debugging echo problems, you should first note that when the echo is heard by a user that is connected directly to the device – it does not indicate any problem on the device itself, the problem is in the echo canceller at the remote UA.
  • Page 45 None of the above If you have verified all the above solutions and still troubleshooting resolves the experience echo, send AudioCodes Technical Support the problem. following information and traces: Accurate and complete network diagram including all network components between the two end connections.

  • Page 46: How Do I Troubleshoot Voice Delay

    Entity from the Device'' on page 10. Delay caused by network Verify your network condition, by contacting your network condition. administrator. None of the above. If all the above is functioning properly, contact AudioCodes Technical Support team. Troubleshooting Guide Document #: LTRT-57601...

  • Page 47: Call Disconnect

    Troubleshooting Guide 7. Call Disconnect Call Disconnect This section discusses troubleshooting for call disconnect: ''Why Doesn't the FXO End a PBX/PSTN Call'' on page ''Why Do Calls Randomly Disconnect?'' on page ''Why Don't Calls Disconnect upon ISDN Disconnect Message'' on page ''Why Does the PBX/PSTN Disconnect IP-to-Tel Calls'' on page Why Doesn't the FXO End a PBX/PSTN Call A common issue is that a call from a PBX that is connected to the FXO device is not...
  • Page 48 MediaPack, Mediant 1000, Mediant 2000 Table 7-1: Unterminated PBX FXO Call Troubleshooting Possible Cause Solution The device is not correctly The following disconnection methods are supported: configured to identify the Detection of polarity reversal / current disconnect: disconnection signaling used by This is the recommended method.

  • Page 49: Why Do Calls Randomly Disconnect

    Troubleshooting Guide 7. Call Disconnect In the network trace, locate the RTP stream sent from the FXO, and then save the RTP payload on your PC as a *.pcm file, by clicking Save Payload (Statistics menu > RTP > Stream Analysis. (Note: Ensure that you select the ‘forward’ option.) Open the *.pcm file in a voice recording utility such as CoolEdit.

  • Page 50: Why Don't Calls Disconnect Upon Isdn Disconnect Message

    MediaPack, Mediant 1000, Mediant 2000 Why Don't Calls Disconnect Upon ISDN Disconnect Message Table 7-3: Calls Not Disconnected Upon Receipt of ISDN Disconnect Troubleshooting Possible Cause Solution The device is configured to By default, when the device receives a Disconnect message disconnect calls when a with Progress Indicator (PI) from the ISDN before a Connect Disconnect message is...

  • Page 51: Fax And Modem

    Troubleshooting Guide 8. Fax and Modem Fax and Modem This section discusses troubleshooting for fax and modem calls. Why Do Fax Sessions Fail Each fax session begins with a regular voice call setup process. Only after this voice channel has been successfully established does fax negotiation begin. Table 8-1: Fax Failure Troubleshooting Possible Cause Solution...

  • Page 52: Mediapack, Mediant 1000, Mediant

    MediaPack, Mediant 1000, Mediant 2000 Possible Cause Solution V34ModemTransportType = 2 BellModemTransportType = 2 Transparent - sends the fax signal in the current voice coder. Relevant parameters include the following: IsFaxUsed = 0 FaxTransportMode = 0 V21ModemTransportType = 0 V22ModemTransportType = 0 V23ModemTransportType = 0 V32ModemTransportType = 0 V34ModemTransportType = 0...
  • Page 53 FaxRelayRedundancyDepth. None of the above. If the problem is still present, contact AudioCodes Technical Support team and provide them with the following information: INI file...
  • Page 54 MediaPack, Mediant 1000, Mediant 2000 Reader’s Notes Troubleshooting Guide Document #: LTRT-57601...

  • Page 55: Call Transfer

    Troubleshooting Guide 9. Call Transfer Call Transfer This section discusses troubleshooting for call transfer: ''Why is a Call Transfer by the FXO Terminated'' on page ''Why Can't I Transfer a Call Between FXS Interfaces'' on page Why Does PBX Terminate Call Transfer by the FXO Device After receiving a SIP REFER message from the IP side (to initiate call transfer), the FXO device performs the following in chronological order:...

  • Page 56: Why Can't I Transfer A Call Between Fxs Interfaces

    MediaPack, Mediant 1000, Mediant 2000 Why Can't I Transfer a Call Between FXS Interfaces Troubleshooting for call transfer between FXS interfaces can include the following issues: The call disconnects between the initial call parties (e.g., A and B) when one of the parties (e.g., A) presses the Flash Hook button to try transfer the call to another party (e.g., C).

  • Page 57: Ip Voice Mail And Unified Messaging

    Troubleshooting Guide 10. IP Voice Mail and Unified Messaging IP Voice Mail and Unified Messaging This section deals with troubleshooting for IP voice mail and Unified Messaging: ''I Cannot Retrieve Voice Mail Messages'' on page ''Why Does IP Voice Mail Request My Extension Number for Retrieving Voice Mail'' on page ''I Cannot Leave Voice Mail Messages'' on page ''Message Waiting Indication Does Not Function'' on page...

  • Page 58: I Cannot Leave Voice Mail Messages

    MediaPack, Mediant 1000, Mediant 2000 10.3 I Cannot Leave Voice Mail Messages Table 10-3: Leaving Voice Mail Troubleshooting Possible Cause Solution There is no SIP Diversion Ensure that the voice mail interface is configured according header in the outgoing INVITE to your deployment, on the Web interface's 'Voice Mail message sent to the IP voice Setting' page (Web path SW Ver.

  • Page 59: Message Waiting Indication Does Not Function

    Troubleshooting Guide 10. IP Voice Mail and Unified Messaging 10.4 Message Waiting Indication Does Not Function Table 10-4: MWI for Voice Mail Troubleshooting Possible Cause Solution The IP voice mail system does Use Syslog or Wireshark to verify that the device receives not send SIP NOTIFY SIP NOTIFY messages from the IP voice mail system (for messages to the device.

  • Page 60: I Cannot Transfer Calls To Users In Unified Messaging

    MediaPack, Mediant 1000, Mediant 2000 10.5 I Cannot Transfer Calls to Users in Unified Messaging Table 10-5: Call Transfer for UM Troubleshooting Possible Cause Solution The PBX does not detect hook- Ensure that the following has been configured: flash signals when using DTMF LineTransferMode = 1.

  • Page 61: Common Web, Snmp And Ini File Issues

    It is protected by a password mechanism that is different from the password used to access the Web Interface. This password can be created by AudioCodes based on the device's IP address. However, there is no need to use the Complete ini file since it includes internal parameters that (if changed) can affect the normal functioning of the device.

  • Page 62: How Do I Obtain The Ini File Via Snmp

    MediaPack, Mediant 1000, Mediant 2000 11.5 How Do I Obtain the ini File Via SNMP It is not possible to obtain (Get) the ini file directly using SNMP. The only available method is to trigger the auto update mechanism (that uses an HTTP server, for example). The relevant parameters are located under cSysHTTPClient.

  • Page 63: How Do I Remove/Insert Mediant 1000 Modules Via Snmp

    Troubleshooting Guide 11. Common Web, SNMP and ini File Issues 11.9 How Do I Remove/Insert Mediant 1000 Modules Via SNMP The FRU (Field Replace Unit) via SNMP: To replace a module using SNMP: Remove the module, by performing the following: Set the acSysModuleFRUaction with fruOutOfServiceAction(2), where the instance refers to the corresponding module.

  • Page 64: 11.12 Why Doesn't Bootp Install On Windows Vista

    MediaPack, Mediant 1000, Mediant 2000 Close the window ‘Select Table Instance’. After the window is closed, the ‘set channelRowStatus’ screen appears. In the field ‘OID to Set’, select a new OID, and then in the field ‘Value to Set’, select option 5 (createandWait). After configuring the parameter of the new entry, set the channelRowStatus to 1 (Active).

  • Page 65: Traffic Debug Analysis

    AudioCodes plugins for For each Wireshark version there is a suitable set of recording does not match the AudioCodes plugins. Verify that you are using the correct Wireshark software version. plugins with your Wireshark software version: The plugins that are released with version 5.2 are relevant to Wireshark version 99.04.
  • Page 66 MediaPack, Mediant 1000, Mediant 2000 Reader’s Notes Troubleshooting Guide Document #: LTRT-57601...

  • Page 67: Debugging Procedures

    ''Wireshark Network Sniffer'' on page ''CLI Debug Recording'' on page 13.1 Case Reporting Procedures When reporting a problem to AudioCodes’ Technical Support department, the following information should be provided: Basic information (required for all types of problems): • Problem description (nature of failure, symptoms, call direction, etc.) •...

  • Page 68: Syslog

    Syslog server using IP/UDP protocol. This information is a collection of error, warning and system messages that record every internal operation of the device. You can use the supplied AudioCodes proprietary Syslog server "ACSyslog" (shown in the figure below) or any other third-party Syslog server for receiving Syslog messages.

  • Page 69: Wireshark Network Sniffer

    Troubleshooting Guide 13. Debugging Procedures Open the Web interface 'Advanced Parameters' page (Web path SW Ver. 5.2: Protocol Management menu > Advanced Parameters submenu > General Parameters; Web path SW Ver. 5.4 and later: Configuration tab > Protocol Configuration menu > SIP Advanced Parameters submenu >...
  • Page 70 MediaPack, Mediant 1000, Mediant 2000 Select the network interface that is currently being used by the PC - on the toolbar, click Interfaces, and then in the 'Capture Interfaces' dialog box, click the Options button corresponding to the network interface: Figure 13-4: Selecting Interface Currently used by the PC In the 'Capture Options' dialog box, select the desired display options: Figure 13-5: Configuring Wireshark Display Options...
  • Page 71 Troubleshooting Guide 13. Debugging Procedures Click Start. Figure 13-6: Captures Packets To view VoIP call flows, from the Statistics menu, choose VoIP Calls. You can view the statistics in graph format by clicking Graph. Figure 13-7: Viewing VoIP Call Flows Version 5.2/5.4 January 2009...
  • Page 72 MediaPack, Mediant 1000, Mediant 2000 To play G.711 RTP streams, click the Player button. Figure 13-8: Playing G.711 RTP Streams To analyze the RTP data stream and extract the audio (which can be played using programs such as CoolEdit) from the data packets (only for G.711), from the Statistics menu, point to RTP, and then choose Stream Analysis.

  • Page 73: Cli Debug Recording

    “ACDR” or “udp.port==925” to view the DR messages that are sent by the device. Notes: • The plugins for DR are per major AudioCodes release. The plug-ins that are released with version 5.4 are applicable to Wireshark version 99.06. The plugins that are released with version 5.6 are applicable to Wireshark version 99.08.
  • Page 74 MediaPack, Mediant 1000, Mediant 2000 Start a CLI management session: In your Web browser's URL field, append the suffix ‘FAE’ (case-sensitive) to the IP address of the device (e.g., http://10.1.229.17/FAE). The 'FAE' page is displayed. On the left pane, click the Cmd Shell button. Figure 13-10: Command Shell Page At the prompt, type DR to access the DebugRecording directory.
  • Page 75 Troubleshooting Guide 13. Debugging Procedures To capture DSP traces (internal DSP packets, RTP, RTCP, PCM, and T.38), at the prompt, type ANCT ALL-WITH-PCM 1. The next call on the device will be recorded. To capture IP traces (such as SCTP and HTTP messages), perform the following: At the prompt, type AIPTT n2h 132 a a (132 for SCTP).
  • Page 76 MediaPack, Mediant 1000, Mediant 2000 Reader’s Notes Troubleshooting Guide Document #: LTRT-57601...

  • Page 77: Management Utilities

    Troubleshooting Guide 14. Management Utilities Management Utilities This section discusses AudioCodes' proprietary management tools that can be used for debugging: ''CPTWizard'' on page ''BootP/TFTP Server'' on page 14.1 CPTWizard The Call Progress Tones Wizard (CPTWizard) is an AudioCodes proprietary application designed to facilitate the provisioning of FXO devices, by recording and analyzing Call Progress Tones (CPT) generated by any PBX or telephone network.
  • Page 78 MediaPack, Mediant 1000, Mediant 2000 The TFTP server is defined in the BootP/TFTP Server utility's 'Preferences' dialog box, as shown below: Figure 14-1: Defining TFTP and SW Files Troubleshooting Guide Document #: LTRT-57601...
  • Page 79 Troubleshooting Guide 14. Management Utilities The device to which you want to assign an IP address and load the software files is defined in the BootP/TFTP Server utility's 'Client Configuration' dialog box, as shown below. The device is defined by MAC address. Ensure that the 'Flash Burn' check box is selected in order to save the loaded firmware file (cmp) to the device's flash memory;...
  • Page 80 CPE Troubleshooting Guide www.audiocodes.com...

This manual is also suitable for:

Mediant 2000Mediant 1000Mediant 600Mediapack mp-124

Table of Contents