Loading... Please wait...

Categories

What details should I report to Digital Techniques Technical Support for troubleshooting telephony cards used with Asterisk?

What details should I report to Digital Techniques Technical Support for troubleshooting telephony cards used with Asterisk?

Product Family – Asterisk Cards

Q: I need technical assistance from Digital Techniques for my Digium telephony card in an Asterisk server. What information should I provide to Digital Techniques Technical Support?

A: Please provide the following details when reporting a Digital Techniques Technical Support case for your Digium telephony card used in an Asterisk server. If you have narrowed down the problem and can explain how you did so, you may omit irrelevant data collection. Not all information is necessary nor applicable for all symptoms.

For each issue related to undesired system behaviour (a symptom), Digital Techniques Technical Support seeks to understand the symptom in context, and to determine its cause within the part of the system where Digital Techniques can change the outcome (Digium telephony card, DAHDI driver, LibPRI, and Asterisk chan_dahdi or codec_dahdi).

Note: Before continuing, please make sure that you are using the current releases of AsteriskDAHDI, and LibPRI software.

1. Details common to all of Digium's Asterisk-related products

  • Asterisk software version. Please make sure that you are using the current release of a supported Asterisk version.
  • Describe the symptom, including the symptom as first observed by the end user, and the symptom as observed in DAHDI or Asterisk at first point of interaction with your Digium product.
  • What changed? Describe any recent changes to the Asterisk server configuration or network before the symptom was observed.
  • When did this symptom first occur?
  • Has it ever worked? If this is a new Asterisk server: Is it replacing an existing Asterisk server? Is it replacing or connecting to a legacy phone system?
  • Can you reproduce the symptom? If so, please list the steps you take.
  • Frequency of the symptom:
    • once
    • N times
    • intermittent
    • periodic, regular interval (e.g., once every 30 seconds; 2 of every 3 call attempts)
    • continuously (every time)
    • every time that event X happens
  • Describe the internal environment of the Asterisk server, especially any unique configuration, patches to Asterisk, or third-party software that interacts with Asterisk.
  • Describe the external environment: IP and telephony network connections to telecoms provider or other service provider, and to premises systems, such as legacy telephone system. Also, network management system, external call generator/distributor, or other system that interacts with the Asterisk server. Please provide a topology diagram in .JPG, .PNG, or .PDF format if available.
  • Describe the call path, including all inbound and outbound call legs: Where does each call originate? How does the call enter the Asterisk server? Where does the call go when it leaves the Asterisk server?

2. Details common to all Digium telephony cards

  • All details from item 1, above
  • DAHDI software version: Please make sure that you are using the current DAHDI release.
    • DAHDI-Linux software version, from output of dmesg or asterisk -rx 'dahdi show version'
    • DAHDI-Tools software version, from output of dahdi_cfg -h.
  • Linux kernel version: output of uname -a
  • Serial number and revision of the Digium interface cards, from the stickers (labels) on the cards
  • Serial number and revision of any Digium interface modules (FXO, FXS, VPM, etc.), from the stickers (labels) on the modules
  • autosupport output, because it collects DAHDI and Asterisk configuration files, and because it aggregates the output of several primary and secondary utilities, including:
    • dmesg
    • dahdi_hardware
    • lspci -vvvb
    • lsmod
    • dmidecode
    • ps aux / ps -ef
    • DAHDI module parameters
  • DAHDI device driver startup messages from dmesg; or with longer system uptime, DAHDI device driver startup messages from system log containing kernel messages (e.g., /var/log/messages)
  • DAHDI device driver debug messages ("debug=N", where N may be a bitmask) with timestamps, while the symptom is occurring
  • Asterisk full log with timestamps, while the symptom is occurring

For audio symptoms:

  • dahdi_monitor recordings

3. Details for digital telephony interface cards, and for digital ports on hybrid telephony cards

  • All details from items 1 and 2, above
  • LibPRI software version, from output of asterisk -rx 'pri show version'. Please make sure that you are using the current LibPRI release.
  • Results of patlooptest or patgen/pattest for 300 seconds, used as a pass/fail test to confirm normal operation or to demonstrate failure
  • Asterisk full log with timestamps, including output of "pri set debug on span N" (or "pri set debug 2 span N" if the span appears to be down) for span N, when an outbound call is attempted and when an inbound call is attempted

For Digium E1/T1 cards, see How do I run a pattern loopback test on a Digium E1/T1 card?

For the Digium B410P card and for the Digium HA8/HB8 cards with B400M BRI module, see Back-to-Back Pattern Test for BRI Adapters.

 4. Details for analog telephony interface cards, and for analog ports on hybrid telephony cards

  • All details from items 1 and 2, above

For FXO modules:

For FXS modules:

  • Describe the observable symptoms when an analog telephone is connected to the corresponding port(s).
  • Linux console output, dahdi_monitor recording, and description of symptoms
  • when relevant "fxstest" commands are run

5. To request replacement of a suspected-defective Digium telephony card (Return Materials Authorization, RMA)

See "How do I request an RMA from Digital Techniques?".

 

What's News

newsletter

Copyright 2017 Digital Techniques (Asia). 本网站所有权归北京迪特爱数码科技有限公司 All Rights Reserved.
 Sitemap | Bigcommerce Premium Themes by PSDCenter