Tadeu's Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
# Asterisk: DAHDI with X100P Clone (Ambient MD3200)

## Preamble

I've recently came across a very cheap internal dial-up modem on Mercado Livre. It cost me the equivalent of about five American Dollars. Upon further research (before buying it, obviously), I've found little to no information on the Ambient MD3200 chipset, but I found out it could be used as a X100P/X101P card on Asterisk, thus providing my server with an FXO port. 

Albeit POTS is on it's sunset as an ubiquitous technology, this was cheap enough to convince me to play a bit with that technology, since I still got a log of POTS or POTS-compatible gear around. But information on DAHDI configuration is a bit harder to come by, those days. It can be found, fragmented through dozens of forum posts, but there's no tutorial explaining the whole process. 

Initially, I've decided to use Freewitch, but `mod_freetdm`, albeit still somewhat maintained, lives outside of the source tree and the documentation is not exactly good. I wasn't able to compile and get it running on Freeswitch. So I decided on Asterisk. 

Asterisk has excellent support on DAHDI. Zapata Telephony Project, or Zaptel, was written by Jim Dixon a long time ago, incubated by the Asterisk community. Now, Sangoma keeps maintaining it, even though both digital and analogue trunk lines are becoming nearly extinct animals, with the onset of SIP technology, now prevalent. 
## Setup Overview

Gear: 
  * i7-3770
  * 16 GB of RAM
  * Proxmox v8

My first idea was to do a PCI passthrough of that card to a virtual machine. That would provide optimal isolation and keep both the kernel module and Asterisk fairly isolated from the host. Unfortunately, this dumb board was sharing it's IRQ with SMBus. Some PCI hardware can deal with this, this card couldn't. So I decided on installing the DAHDI modules directly onto the host. Not ideal, but it is what it is. 

Then I decided to run Asterisk inside a LXC container, passing through the device descriptors to the container. Despite that, we **do not** need to make it privileged. 

## The Actual Process

### Kernel module

First, clone the project repository somewhere. 

```bash
git clone https://github.com/asterisk/dahdi-linux
```

Or, if you're not crazy, get latest release tarball [here](https://github.com/asterisk/dahdi-linux/releases). 

On Proxmox, once you have `build-essentials` and standard compilation tools, installing it should be as easy as doing this: 

```bash
apt install pve-headers # kernel headers
make
make install
```

This will install the modules. But you'll still have to make sure `wcfxo` gets the card, not `netjet`. By default, the card binds to it, and the easiest way of getting rid of it is restarting the machine. Just make sure you got a file inside `/etc/modprobe.d/` containing the following: 

```
blacklist netjet
```

Once rebooted, the card should be bound to `wcfxo`. Something you can confirm with `lspci -nnk` command: 

```
$ lspci -nnk
[...]
04:00.0 Communication controller [0780]: Tiger Jet Network Inc. / ICP DAS Tiger3XX Modem/ISDN interface [e159:0001]
        Subsystem: Intel Corporation Digium X100P/X101P analogue PSTN FXO interface [8086:0003]
        Kernel driver in use: wcfxo
        Kernel modules: netjet, wcfxo
[...]
```

Why is it detected as an ISDN card? No idea. Probably because some ISDN cards do use the same chip. But this driver does nothing to us. The card isn't ISDN and this driver doesn't even allow us to use this card as a dial-up modem. Since ISDN died long before traditional landlines, this driver seems to be a relic of the past and wouldn't be surprising if it got removed soon. It's fairly obscure and, if there's any detailed documentation on it, it's lost in the mists of time. 

**Either way**, now we have a X100P clone card added to the system. Check endpoints at `/dev/dahdi` and `/sys/class/dahdi` to confirm it's working. That's about it for the host. Some of those devices will get bound to a LXC container. 


### Asterisk on LXC

You may use any Linux of your choice, I guess. Though I suppose the easiest route is to use any standard RPM or DEB-based distro. As per my default behaviour, I went with Debian. Particularly Bookworm, the currently stable version. 

Make sure you're passing on the correct devices to the container: 
```
/dev/dahdi/chan/001/001
/dev/dahdi/channel
/dev/dahdi/ctl
/dev/dahdi/pseudo
/dev/dahdi/timer
```

It goes in the resource tab at PVE, like this: 

{{ :telephony:pve_dahdi.png?400 | }}

Install `dahdi-tools`: 

```bash
apt install dahdi-tools
```

This will allow you to generate configuration and run tests to confirm the card is working, and will save an incredible amount of time, if it's not, because next steps are a bit of an involved process. 

I've followed those instructions, for the largest part: 
https://docs.rockylinux.org/guides/communications/asterisk_installation/#asterisk-configuration

FIXME **WIP**

((https://www.helviojunior.com.br/voip/installing-x100p-asterisk/))
((https://community.asterisk.org/t/asterisk-dahdi-linux-version-compatibility/99080))
((https://community.asterisk.org/t/getting-started-with-dahdi-asterisk-dahdi-show-channels-shows-nothing/75118))
((https://community.asterisk.org/t/dahdi-and-x100p/31344/2))
((https://suporte.aligera.com.br/support/solutions/articles/35000001900-instalac%C3%A3o-do-driver-dahdi-aligera))
Tadeu's Wiki

User Tools

Site Tools

Page Tools
