Integration of Asterisk with minicom DX-500 with ELF2-AE
There was a need for the integration of office PBX (Asterisk) and industrial PBX (Minikom DX-500).
The manufacturer of the DX-500, has a solution MSG-1 , but it did not fit into the framework of a limited budget.
It was decided to integrate through the channel E1, the benefit was just free.
I already had Asterisk integration projects for E1, and once they had the most severe dances with a tambourine around interrupts for the E1 interface boards, plus they limit the possibilities of virtualization, I really didn’t want to take this fee.
I have long wanted to try ELF2-AE from Novosibirsk Parabel.
Yes, everything turned out, ELF2-AE arrived,pleased with surprise with the rear location of the Ethernet and E1 ports.
I plugged in, set up, and everything started to happen almost immediately, here are the configs:
front view.
')
The device itself converts E1 to TDMoE protocol. So between asterisk and elf2 there should not be a router. I ran across mentions that the pier works within only one switch. It not so, at me vlan through 4 switches.
General settings:
Parameters E1:
where eth0 is an interface looking into one network / vlan c elf2
For a group of ports, enable “Wed” - the flag “collect numbers into the register” before generating them into the line
We expose the channel in the slave. In Master mode, she stubbornly did not want to work.
In this plan, the challenges 1XX, 2XX, 5XX go to group number 1
Important point:
You must specify the parameter 4 "Ng" - the number of digits of the dialing line, in my case, 3-digit numbers.
Also parameter 6 "" - the flag of the global prefix include (+):
The state should be “Open” if “Closed”, something went wrong ...
The manufacturer of the DX-500, has a solution MSG-1 , but it did not fit into the framework of a limited budget.
It was decided to integrate through the channel E1, the benefit was just free.
I already had Asterisk integration projects for E1, and once they had the most severe dances with a tambourine around interrupts for the E1 interface boards, plus they limit the possibilities of virtualization, I really didn’t want to take this fee.
I have long wanted to try ELF2-AE from Novosibirsk Parabel.
Results:
Yes, everything turned out, ELF2-AE arrived,
I plugged in, set up, and everything started to happen almost immediately, here are the configs:
ELF2
front view.')
The device itself converts E1 to TDMoE protocol. So between asterisk and elf2 there should not be a router. I ran across mentions that the pier works within only one switch. It not so, at me vlan through 4 switches.
General settings:
Parameters E1:
Dahdi
/etc/dahdi/system.conf dynamic=eth,eth0/00:55:55:55:55:00,31,0 alaw=1-15,17-31 bchan=1-15,17-31 dchan=16 loadzone = ru defaultzone = ru where eth0 is an interface looking into one network / vlan c elf2
/etc/asterisk/chan_dahdi.conf [channels] language=ru group=0 context=from-qsig signalling=pri_net switchtype=qsig channel => 1-15,17-31 DX-500 Settings
Group E1 channels into group â„–1
For a group of ports, enable “Wed” - the flag “collect numbers into the register” before generating them into the line
LAPD Protocol Settings (LAPD)
We expose the channel in the slave. In Master mode, she stubbornly did not want to work.
Parameters DSS1 (T DSS1)
Parameters of the DSS1 protocol. (T DSS1N)
Numbering Plan (map)
In this plan, the challenges 1XX, 2XX, 5XX go to group number 1
Important point:
You must specify the parameter 4 "Ng" - the number of digits of the dialing line, in my case, 3-digit numbers.
Also parameter 6 "" - the flag of the global prefix include (+):
Channel status (dch command)
The state should be “Open” if “Closed”, something went wrong ...
Source: https://habr.com/ru/post/228839/
All Articles