I know this topic came up many months back and some discussions were being had on how to do this within the Zaptel drivers. However, I'm looking for even a crude hack that someone has put together to get this done. We have PRI's and LD T1's that are load balanced on two boxes. The hunt order goes from box to box as far as the spans are concerned. There are times that I would like to busy one out so that calls gradually role to the new box and I can eventually take one out of service. What I was thinking is to create a script that I could tell the specific channels and it would go through and initiate zap calls to an empty meetme. Basically bridging all of the available zap channels on a given span together. Then the trick is monitoring the hangups so that it can initiate a subsequent call immediately following. Once all of the channels in a span have been bridged, I can then bring the box down. Nasty huh? Anyone have a better idea? Or do they have anything like this so I'm not putting it together? Thanks, -Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070926/b7f41ec8/attachment.htm
Very nasty indeed. Through my experience with PRI, the TelCo switchs are not that present to deal with. Your method will work, kind of. However, if the TelCo decides to send you a call during that split second of idle, how are you going to handle it. The best way is still to call your TelCo to take the span down. ________________________________ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Brian Roy Sent: Wednesday, September 26, 2007 3:54 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] How to "busy out" zap channels I know this topic came up many months back and some discussions were being had on how to do this within the Zaptel drivers. However, I'm looking for even a crude hack that someone has put together to get this done. We have PRI's and LD T1's that are load balanced on two boxes. The hunt order goes from box to box as far as the spans are concerned. There are times that I would like to busy one out so that calls gradually role to the new box and I can eventually take one out of service. What I was thinking is to create a script that I could tell the specific channels and it would go through and initiate zap calls to an empty meetme. Basically bridging all of the available zap channels on a given span together. Then the trick is monitoring the hangups so that it can initiate a subsequent call immediately following. Once all of the channels in a span have been bridged, I can then bring the box down. Nasty huh? Anyone have a better idea? Or do they have anything like this so I'm not putting it together? Thanks, -Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070926/1bf22b51/attachment.htm
Tomás Laureano Peralta Tormey
2007-Sep-27 04:54 UTC
[asterisk-users] How to "busy out" zap channels
Brian: Maybe the CLI command "stop gracefully" is what are you looking for. Basically, Asterisk will stop receiving incoming calls (of any channel type) and stop itself when all the current calls finish. I hope this help you. Best regards, Tom?s. 2007/9/26, Brian Roy <mister.roy at gmail.com>:> I know this topic came up many months back and some discussions were being > had on how to do this within the Zaptel drivers. However, I'm looking for > even a crude hack that someone has put together to get this done. > > We have PRI's and LD T1's that are load balanced on two boxes. The hunt > order goes from box to box as far as the spans are concerned. There are > times that I would like to busy one out so that calls gradually role to the > new box and I can eventually take one out of service. What I was thinking is > to create a script that I could tell the specific channels and it would go > through and initiate zap calls to an empty meetme. Basically bridging all of > the available zap channels on a given span together. Then the trick is > monitoring the hangups so that it can initiate a subsequent call immediately > following. Once all of the channels in a span have been bridged, I can then > bring the box down. Nasty huh? > > Anyone have a better idea? Or do they have anything like this so I'm not > putting it together? > > Thanks, > > -Brian >
On 9/26/07, Brian Roy <mister.roy at gmail.com> wrote:> > Anyone have a better idea? Or do they have anything like this so I'm not > putting it together? >If its PRI why don't you try: exten => 0000000000,1,Set(PRI_CAUSE=27) exten => 0000000000,2,Hangup Or cause code 17 17 = User Busy. The number dialed is busy and cannot receive any more calls. 27 = Destination Out-of-Order. This is a working number, but the span to the destination is not active or there is a problem sending messages to this destination.