Ok so I was not able to get the actual line in use from core show
channels anymore.
So I thought I would bit the bullet and just monitor events since that
seemed like the thing
to do. After doing that I mad a call.
Event: Newchannel
Privilege: call,all
Channel: DAHDI/i4/317XXX
Ok so I was not able to get the actual line in use from core show
channels anymore.
So I thought I would bit the bullet and just monitor events since
that
seemed like the thing
to do. After doing that I mad a call.
Event: Newchannel
Privilege: call,all
Channel: DAHDI/i4/317XXX
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
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
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
Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] asterisk 11 and DAHDI/i4
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
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
You should just cache the AMI DAHDIChannel event information in your
program.
If you really must you could use the CLI command pri show channels.
However, it is not intended to be repeatedly run for performance
reasons. It blocks processing of ISDN messages while it is running.
I am not
Discussion
Subject: Re: [asterisk-users] asterisk 11 and DAHDI/i4
You should just cache the AMI DAHDIChannel event information in your
program.
If you really must you could use the CLI command pri show channels.
However, it is not intended to be repeatedly run for performance
reasons. It blocks
You should just cache the AMI DAHDIChannel event information in your
program.
If you really must you could use the CLI command pri show channels.
However, it is not intended to be repeatedly run for performance
reasons. It blocks processing of ISDN messages while it is running.
I am not
IMO the local channel call should be the lowest overhead option available.
What about:
Action: Command
Command: dahdi show channels
I can just look to see if Extension has anything for the Chan I am
interested in?
is
On 12/20/2012 01:00 PM, Jerry Geis wrote:
IMO the local channel call should be the lowest overhead option available.
What about:
Action: Command
Command: dahdi show channels
I can just look to see if Extension has
I have a little dialplan context now...
[check-chanisavail]
exten = s,1,ChanIsAvail(${agi_channel})
exten = s,n,System(/bin/echo ${AVAILCHAN} /tmp/${agi_file})
exten = s,n,Hangup()
and a call file:
Channel: Local/s@check-chanisavail/n
Context: check-chanisavail
Extension: s
Priority: 1
: Thursday, December 20, 2012 1:56 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] asterisk 11 and DAHDI/i4
I have a little dialplan context now...
[check-chanisavail]
exten = s,1,ChanIsAvail(${agi_channel}) exten = s,n,System(/bin/echo
${AVAILCHAN} /tmp
Just for grins, do you have a softphone like xlite that you can try the
outgoing call on? I think it's an outgoing issue, not a polycom one.
I do not have a softphone. I have a yealink VP-2009 and same behavior.
Jerry
--
_
In 1.4.43 I would see things from core show channels like
DAHDI/18/x
for line 18
in Asterisk 11 its
DAHDI/i4/
How do I get the line number back?
Jerry
--
_
-- Bandwidth and Colocation Provided by
In 1.4.43 I would see things from core show channels like
DAHDI/18/x
for line 18
in Asterisk 11 its
DAHDI/i4/
How do I get the line number back?
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
17 matches
Mail list logo
