<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<blockquote type="cite">
<pre wrap="">From: "Imran Ahmed" <a class="moz-txt-link-rfc2396E"
href="mailto:codentest@gmail.com"><codentest@gmail.com></a>
Subject: Re: [asterisk-dev] Re: How to busy out PRI channels?
To: "Asterisk Developers Mailing List" <a class="moz-txt-link-rfc2396E"
href="mailto:asterisk-dev@lists.digium.com"><asterisk-dev@lists.digium.com></a>
Message-ID:
<a class="moz-txt-link-rfc2396E"
href="mailto:f929a6640610261959q7863f681ob728668478e7f90e@mail.gmail.com"><f929a6640610261959q7863f681ob728668478e7f90e@mail.gmail.com></a>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 10/26/06, Tony Mountifield <a class="moz-txt-link-rfc2396E"
href="mailto:tony@softins.clara.co.uk"><tony@softins.clara.co.uk></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> </span>In article <a
class="moz-txt-link-rfc2396E"
href="mailto:p06240505c166811e91a3@loligo.com"><p06240505c166811e91a3@loligo.com></a>,
<span class="moz-txt-citetags">> </span>John Todd <a
class="moz-txt-link-rfc2396E" href="mailto:jtodd@loligo.com"><jtodd@loligo.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> > </span>At 2:30 PM +0000 2006/10/26, Tony Mountifield wrote:
</pre>
<blockquote type="cite">
<pre wrap=""><span class="moz-txt-citetags">> > ></span>
<span class="moz-txt-citetags">> > ></span>Anyway, that's two replies approving of the feature, but none yet from
<span class="moz-txt-citetags">> > ></span>anyone with any hints about accomplishing it. Perhaps when folks have
<span class="moz-txt-citetags">> > ></span>finished at Astricon....
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">> ></span>
<span class="moz-txt-citetags">> > </span>Actualy, there has been sidebar discussion here at Astricon (was it
<span class="moz-txt-citetags">> > </span>in session or in the hall or at dinner? I have no idea.) about what
<span class="moz-txt-citetags">> > </span>to do for this. Mark Vince and I have noted that this is is for some
<span class="moz-txt-citetags">> > </span>reason on everyone's midn, and possibly with the appropriate bribes
<span class="moz-txt-citetags">> > </span>or caffeine in the CodeZone it may get done, or at least discussed in
<span class="moz-txt-citetags">> > </span>more detail. I would suggest that if anyone on the list who is not
<span class="moz-txt-citetags">> > </span>at Astricon has any code to contribute that this would be a great
<span class="moz-txt-citetags">> > </span>time to throw some ingredients in while the chefs are looking at this
<span class="moz-txt-citetags">> > </span>particular pot.
<span class="moz-txt-citetags">> ></span>
<span class="moz-txt-citetags">> > </span>The problem set seems to be:
<span class="moz-txt-citetags">> > </span> - how do you [busy,un-busy] channels out from a "live" system without
<span class="moz-txt-citetags">> > </span> re-loading zaptel? Should it be CLI only, or should there also be
<span class="moz-txt-citetags">> > </span> something that is possible from within the dialplan and/or AMI?
<span class="moz-txt-citetags">> > </span> - how do you display the status of channels?
<span class="moz-txt-citetags">> > </span> - how do you distinguish if the other side has busied a channel out?
</pre>
</blockquote>
<pre wrap=""><span class="moz-txt-citetags">></span>
<span class="moz-txt-citetags">> </span>John, thanks for the reply - good to know the issue is being talked
<span class="moz-txt-citetags">> </span>about over there! I'd love to contribute code, but currently don't know
<span class="moz-txt-citetags">> </span>enough about libpri etc. to come up with any. I'd be interested to hear
<span class="moz-txt-citetags">> </span>the thoughts of someone like Matt Frederickson on this issue.
</pre>
</blockquote>
<pre wrap=""><!---->
Matthew Frederickson is probably the right person to answer these question:
Is it possible to not acknowledge new setup requests (letting the
request time out) and still be able to continue existing calls on a
pri, without the pri line going into an alarm.
If so, will the telco switch re route the new calls to another pri on
the trunk group or indicate busy? Also does this behavior change with
switch type?
If the pri does not go into alarm, then libpri code can be changed to
accomodate such requests, which will allow us to bring down a pri line
without disrupting a calls during peak usage time, any comments?
Regards,
Imran.</pre>
</blockquote>
We had the same issue a few years ago on a callingcard platform. C7 and
R2 signalling allowed us to open/backbusy channels but we found no
direct support for this in ISDN.<br>
Our workaround was to dial a non-existing number on the channels that
should be busy. The CO would then try to release the channels after the
call reject - we did then delay the ack of the release to keep the
channel busy. It was possible to hang-on the the release for approx 180
seconds without any problems. The fake backbusy then had to redial the
number again to keep the line busy. If we were holding the ack for more
than 180 seconds then the channel went in to some error state which
sometimes required a link reset to get it operational again. All other
calls on the same trunk were always un-affected by our fake
backbusy. This was implemented on a platform using Aculab linecards.<br>
Just my 2 cents and experience on this issue.<br>
Freddi <br>
<br>
<br>
</body>
</html>