...
Dgiium Digital card (Single, Dual , Quad or Octal span card)
Switchtype defined in chan_dahdi.conf, Currently the following Switchtype supports this feature
euroisdn
national
4ess
5ess,
dms100 (qsig is nonfunctional)
LibPRI 1.4.11.5 or greater.
| Info |
|---|
Note: With the dms100 switchtype, there must be one inbound call into Asterisk and one outbound call from Asterisk for 2BCT to work. All other switchtypes work OK regardless of whether calls are inbound or outbound, any combination can be used. |
Configuration
To enable: edit /etc/asterisk/chan_dahdi.conf, and ensure the following lines are above the channel definitions:
facilityenable = yes
transfer = yes
callwaiting=no
callwaitingcallerid=no
faxdetect=no
| Info |
|---|
Note: According to source code faxdetect should not have any effect on asterisk being able to initiate a 2 B-Channel Transfers, however that your initial configuration should have this set to no to guarantee to guarantee asterisk to not have any interest on the audio, once you have confirmed that asterisk initiates the transfer you can enable for further testing. See Limitations for more information |
Also, in your extension.conf, you need to to have DYNAMIC_FEATURES disabled, to Disable edit /etc/asterisk/extensions.conf and set DYNAMIC_FEATURES= in the general setting. You can also do it in the dial using using the following commands
exten => 1234567890,1,Set(DYNAMIC_FEATURES=)
exten => 1234567890,n,Dial(DAHDI/g0/987654321)
Limitations
Asterisk can only initiate a 2BCT when it has no interest audio of the call. This is the reason that you need to disable any feature that requires asterisk to listen to audio in order to perform actions (such as recordings, features codes, wait for caller ID information, etc )
Asterisk requires to be able to perform a native bridging with the DAHDI channels, you can confirm if asterisk is doing by native brigding by set the verbose level to 3 and attempt a transfer
...