Skip to content
Phone Guides

Asterisk analogue gateways and DAHDI

Identify the physical connection before selecting configuration. An analogue telephone, an analogue network line and a SIP trunk are different interfaces. A connector that fits is not evidence that the electrical role or signalling matches.

Source-reviewed, 19 October 2026. Prepared from the cited documentation. No analogue hardware or DAHDI installation has been independently tested by Phone Guides. Scope: connection roles and review method; no exact device, firmware or operating-system compatibility claim is made.

Match the port roles

An FXS port supplies the telephone-side service used by an analogue telephone; an FXO port connects to the line-side service. Verify the exact manufacturer's port descriptions and permitted connections before connecting equipment. Equipment intended for one role should not be treated as interchangeable with the other.

Arrangement Where configuration responsibility sits
Analogue telephone through a SIP adapter Adapter's analogue settings and its SIP account
Analogue line through a SIP gateway Gateway's line signalling and its Asterisk trunk
Local telephony hardware using DAHDI Hardware/driver setup plus Asterisk channel configuration
SIP carrier only PJSIP/carrier configuration; no analogue port is implied

Do not install DAHDI solely because an external SIP gateway has analogue ports. Document whether Asterisk sees that device through SIP or through local telephony hardware.

Verify the hardware and software combination

The official DAHDI documentation entry links the Asterisk channel-driver subjects. The DAHDI Linux repository is an upstream source for its driver project. Neither establishes that an arbitrary card, kernel and package combination is supported.

Record exact card/gateway model, port/module type, firmware, driver, operating-system kernel and Asterisk version. Use the hardware vendor's current instructions for that combination. Historical card names and installation commands in archived books are historical references until matched to current support evidence.

For local DAHDI hardware, check each layer separately. On Linux, DAHDI's /proc/dahdi entries show spans and channels registered with the kernel driver. The DAHDI tools lsdahdi output can show whether channels have been configured, while Asterisk's dahdi show channels reports channels visible to the running PBX. These views answer different questions:

Observation Boundary to investigate
Expected span is absent from /proc/dahdi Device, kernel module, driver and span registration
Span appears but channel signalling is not configured DAHDI configuration and the selected hardware's line/framing requirements
Channel is configured in DAHDI but absent from Asterisk's channel list Asterisk module loading and the channel driver's configuration
Channel is available but calls fail or do not release Signalling mode, line supervision, port role and exact connected service

These commands and files apply to Linux DAHDI hardware, not to a SIP gateway that Asterisk reaches over PJSIP. The upstream DAHDI Linux interface notes describe /proc/dahdi; the DAHDI tools project documents its tools and startup configuration. Check the installed CLI help because channel commands depend on the relevant Asterisk module being loaded.

Treat regional settings as a set

Check the relevant line/telephone settings: tone definitions, ringing, impedance, caller-ID method and disconnect supervision. Values depend on the device and connected service. A call answering once does not establish correct ringing, identity or release behaviour.

For a gateway, keep its analogue-side settings separate from SIP trunk identity and routing. Avoid duplicating number manipulation across both systems without documenting the order.

Diagnose each direction

Record incoming ringing, outgoing seizure, answer, two-way audio, caller identity, DTMF and hangup separately. If a line stays occupied, inspect disconnect detection rather than increasing unrelated SIP timers. For echo or level complaints, establish the exact analogue leg and supported adjustment procedure before changing settings.

Fax and non-voice equipment need their own evidence. Use fax and T.38; ordinary telephone audio does not prove fax reliability or suitability for alarms, lifts or other specialised services.

Reader checks

On your exact equipment, check calls in both directions and hangup by each party. Include busy, unanswered and disconnected-line conditions, caller-ID presentation and digit entry. Preserve the original settings and recovery method. Describe results with the port, firmware and service scope so another reader can tell whether the evidence applies.

Return to Asterisk documentation.