I am trying to enable TRANSFER for DAHDI in my chan_dahdi.conf file but I’m still getting this…

[code]asterisk-ss7*CLI> core show channeltypes
Type Description Devicestate Indications Transfer

USTM UNISTIM Channel Driver no yes no
Phone Standard Linux Telephony API Driver no yes no
Console OSS Console Channel Driver no yes no
Agent Call Agent Proxy Channel yes yes no
DAHDI DAHDI Telephony Driver w/PRI & SS7 yes yes no
Bridge Bridge Interaction Channel no no no
Local Local Proxy Channel Driver yes yes no
Skinny Skinny Client Control Protocol (Skinny) yes yes no
SIP Session Initiation Protocol (SIP) yes yes yes
MulticastR Multicast RTP Paging Channel Driver no no no
IAX2 Inter Asterisk eXchange Driver (Ver 2) yes yes yes

11 channel drivers registered.
asterisk-ss7*CLI> core show channeltype dahdi
– Info about channel driver: DAHDI –
Device State: yes
Indication: yes
Transfer : no
Capabilities: 0x4c (ulaw|alaw|slin)
Digit Begin: yes
Digit End: yes
Send HTML : no
Image Support: no
Text Support: yes[/code]

Any ideas?

That output displays static characteristics of the channel drier and in the case of transfer, it relates to whether or not the Transfer dialplan application is supported, i.e. whether it is possible to get the remote side to transfer the call so as to completely remove Asterisk from it.

transfer in chan_dahdi.conf relates to the ability to honour transfer requests arriving over the wire, which would result in a reconfiguration of the call within Asterisk, without affecting the remote system.

Which of these are you trying to do?

Working on the first option… I see in the libss7 that RLT is supported with the Nortel DMS. I have incoming calls from the DMS via DAHDI that we want to release back to the DMS. I’ve been looking into trying to make changes to the code to get this working.