> This was a change in v1.8 and is documented in the v1.8 UPGRADE.txt > file: > > * The PRI channels in chan_dahdi can no longer change the channel > name if a > different B channel is selected during call negotiation. To > prevent using > the channel name to infer what B channel a call is using and to > avoid name > collisions, the channel name format is changed. > The new channel naming for PRI channels is: > DAHDI/i<span>/<number>[:<subaddress>]-<sequence-number> > > * Added CHANNEL(dahdi_span), CHANNEL(dahdi_channel), and > CHANNEL(dahdi_type) > so the dialplan can determine the B channel currently in use by the > channel. > Use CHANNEL(no_media_path) to determine if the channel even has a B > channel. > > * Added AMI event DAHDIChannel to associate a DAHDI channel with an > Asterisk > channel so AMI applications can passively determine the B channel > currently > in use. Calls with "no-media" as the DAHDIChannel do not have an > associated > B channel. No-media calls are either on hold or call-waiting. > ok - can I use a different method of doing my check to see if a line > is available by > using the AMI call ExtensionState or ChanIsAvail? > > Doing > Action: ExtensionState > Parameters: DAHDI/1 > > says Error > Message: Extension not specified
It is Action: ExtensionState Exten: 5551212 Context: fubar This will return the status of the dialplan exten hint. > and > Action: Command > Command: ChanIsAvail > Parameters: DAHDI/1 > > says Error > No such command "ChanIsAvail" ChanIsAvail is a dialplan application not a CLI command. It also will not work for what you want in this case. > I'm clearly missing something? Quite possibly. :) Richard -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users