Displaying 7 results from an estimated 7 matches for "sohosi".
Did you mean:
sohost
2005 Sep 13
0
PRI zap channels not cleared when no match in context for dialed number on inbound call
Could some out there with a PRI check and see if this problem shows up
on your system?
The test is to dial a number routed to * via a PRI where there is no
match in the dial plan for the dialed number.
Asterisk will reject the call, but "show zap channels" still shows the
channel assigned to the number that was dialed under the extensions
column.
The channel WILL answer another call,
2005 Sep 13
1
PRI zap channels not cleared whennomatchincontext for dialed number on inbound call
I tried that, you have to ANSWER before you can clear it, which is not a
good idea...
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-
> bounces@lists.digium.com] On Behalf Of Alexander Lopez
> Sent: Tuesday, September 13, 2005 9:27 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: RE: [Asterisk-Users]
2005 Sep 13
0
PRI zap channels not cleared when no match incontext for dialed number on inbound call
I se what you are talking about I an able to reproduce!!!
However your PRI may be in a Round-Robin picking order, that would cycle
through all of the channels until it reaches an end and then it repeats.
I set our PRI to first available hunting instead of RR and it will use
the same channel over and over again regardless if the call exists.
If anything it's a feature!!!
Unassigned DID will
2005 Sep 13
0
PRI zap channels not cleared when no matchincontext for dialed number on inbound call
But it does indicated that a variable is staying assigned that should
not be, which could have other impact over time???
The behavior is very different for c call where there is a dialplan
match for the dialed number, when the call completes the channel
extension variable is cleared.
If you do not mind please ad a bug note that you experienced the same
thing! The bug marshals think I am nuts.
2005 Sep 13
0
PRI zap channels not cleared when nomatchincontext for dialed number on inbound call
Yeah the "variable stays there" because the channel is never up to be
cleared. If you do something like
exten => _X.,1,Wait(1)
exten => _X.,2,Hangup
You will see the same behavior. Can you confirm??
I am running CVS from about a week ago...
Alex
> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com
>
2010 Apr 15
0
Asterisk-Addons 1.4.11, 1.6.0.5, 1.6.1.3, and 1.6.2.1 Now Available
The Asterisk Development Team has announced releases of Asterisk-Addons version
1.4.11, 1.6.0.5, 1.6.1.3, and 1.6.2.1. These releases are available for
immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/
These releases resolve several issues reported by the community:
* Fix reading samples from format_mp3 after ast_seekstream/ast_tellstream.
(Closes issue #15224.
2010 Apr 15
0
Asterisk-Addons 1.4.11, 1.6.0.5, 1.6.1.3, and 1.6.2.1 Now Available
The Asterisk Development Team has announced releases of Asterisk-Addons version
1.4.11, 1.6.0.5, 1.6.1.3, and 1.6.2.1. These releases are available for
immediate download at http://downloads.asterisk.org/pub/telephony/asterisk/
These releases resolve several issues reported by the community:
* Fix reading samples from format_mp3 after ast_seekstream/ast_tellstream.
(Closes issue #15224.