DAHDI ISDN channel names will not allow device state to work. (Interim solution.)
authorRichard Mudgett <rmudgett@digium.com>
Mon, 2 Nov 2009 17:34:22 +0000 (17:34 +0000)
committerRichard Mudgett <rmudgett@digium.com>
Mon, 2 Nov 2009 17:34:22 +0000 (17:34 +0000)
commit6406f39594b3baf8fe9d518550f748431ec81c79
treed196854b76b89353606f0e429a0bf9b3dbc3474d
parent14a8c042cd04d0a77b1bcab87701ff6aaf1b2f4f
DAHDI ISDN channel names will not allow device state to work.  (Interim solution.)

Since ISDN works like SIP and not analog ports in regard to devices, the
device state based on the ISDN channel number could not work.  This has
not been an issue until the advent of PTMP NT mode.  Previously, ISDN
lines were used as trunks and did not have to keep track of specific
devices.

As an interim solution until device states are properly implemented, the
channel name is being changed to the following format to use the generic
device state support:
DAHDI/i<span>/<number>[:<subaddress>]-<sequence-number>

Dialplan hints would thus be:
exten => xxx,hint,DAHDI/i2/5551212

This will work with the following restrictions:
*  The number of devices/phones cannot exceed the number of B channels.
(i.e., BRI has 2)
*  Each device/phone can only have one number.  No shared MSN's.
*  The phones/devices probably should not use subaddressing.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@226882 65c4cc65-6c06-0410-ace0-fbb531ad65f3
UPGRADE.txt
channels/chan_dahdi.c
channels/sig_pri.c
channels/sig_pri.h