Is it possible to make the telco send an busy signal when an incoming call are supposed to dial a group which has all lines busy? Since I will get many public phonenumbers into my E1 (from telco), it will be sliced up into a few groups. There might be channels availible in the E1, but not on the other side of Asterisk (the office side).
Hi,> -----Original Message----- > Is it possible to make the telco send an busy signal when an > incoming call are supposed to dial a group which has all lines busy? > Since I will get many public phonenumbers into my E1 (from > telco), it will be sliced up into a few groups. There might > be channels availible in the E1, but not on the other side of > Asterisk (the office side).You can set a PRI_CAUSE variable. See http://www.voip-info.org/tiki-index.php?page=Asterisk%20variable%20PRI_CAUSE Florian
Florian Overkamp wrote:> Hi, > > >>-----Original Message----- >>Is it possible to make the telco send an busy signal when an >>incoming call are supposed to dial a group which has all lines busy? >>Since I will get many public phonenumbers into my E1 (from >>telco), it will be sliced up into a few groups. There might >>be channels availible in the E1, but not on the other side of >>Asterisk (the office side). > > > You can set a PRI_CAUSE variable. See > http://www.voip-info.org/tiki-index.php?page=Asterisk%20variable%20PRI_CAUSEThis only works in CVS-HEAD. For production use just run Busy() in the dialplan.
Hi,> -----Original Message----- > > You can set a PRI_CAUSE variable. See > > > http://www.voip-info.org/tiki-index.php?page=Asterisk%20variab > le%20PRI_CAUSE > > This only works in CVS-HEAD. For production use just run Busy() in > the dialplan.Actually, we use this on 1.0.3 with BRI-STUFF. Florian
On Tue, 25 Jan 2005, Eric Wieling wrote:> Florian Overkamp wrote: > > You can set a PRI_CAUSE variable. See > > http://www.voip-info.org/tiki-index.php?page=Asterisk%20variable%20PRI_CAUSE > > This only works in CVS-HEAD. For production use just run Busy() in > the dialplan.It was added to Asterisk 2003/11/05, so it should be in _all_ 1.0 releases. Peter
On Tue, 25 Jan 2005, Eric Wieling wrote:>> You can set a PRI_CAUSE variable. See >> http://www.voip-info.org/tiki-index.php?page=Asterisk%20variable%20PRI_CAUSE > > This only works in CVS-HEAD. For production use just run Busy() in the > dialplan.No, PRI_CAUSE works great at least in 1.0.2, probably in the earlier 1.0 releases too. Busy() may play a busy tone to the caller instead of signalling busy so using PRI_CAUSE is much better in PRI or BRI environment. exten => 123437,1,Dial(Zap/g2/37,26,tg) exten => 123437,2,GotoIf($[${DIALSTATUS} = BUSY]?110:3) exten => 123437,3,Answer exten => 123437,4,Wait(1) exten => 123437,5,Voicemail(su21) exten => 123437,6,Hangup exten => 123437,110,SetVar(PRI_CAUSE=17) exten => 123437,111,Hangup -- Regards, Tobias J?nsson, Lund SE
On Tue, 25 Jan 2005, Tobias J?nsson wrote:> No, PRI_CAUSE works great at least in 1.0.2, probably in the earlier 1.0 > releases too. Busy() may play a busy tone to the caller instead of > signalling busy so using PRI_CAUSE is much better in PRI or BRI > environment.The behaviour of Busy() and Congestion() can be changed with the "priindication" setting in zapata.conf. The options are "inband" (default) or "outofband". This only affects the two applications mentioned above. Peter
On Tue, 25 Jan 2005, Peter Svensson wrote:> On Tue, 25 Jan 2005, Tobias J?nsson wrote: > >> No, PRI_CAUSE works great at least in 1.0.2, probably in the earlier >> 1.0 releases too. Busy() may play a busy tone to the caller instead of >> signalling busy so using PRI_CAUSE is much better in PRI or BRI >> environment. > > The behaviour of Busy() and Congestion() can be changed with the > "priindication" setting in zapata.conf. The options are "inband" > (default) or "outofband". This only affects the two applications > mentioned above.Thank you for that information. I have now updated the wiki of zapata.conf. -- Regards, Tobias J?nsson, Lund SE
On Wed, 26 Jan 2005, Tobias J?nsson wrote:> On Tue, 25 Jan 2005, Peter Svensson wrote: > > On Tue, 25 Jan 2005, Tobias J?nsson wrote: > >> No, PRI_CAUSE works great at least in 1.0.2, probably in the earlier > >> 1.0 releases too. Busy() may play a busy tone to the caller instead of > >> signalling busy so using PRI_CAUSE is much better in PRI or BRI > >> environment. > > > > The behaviour of Busy() and Congestion() can be changed with the > > "priindication" setting in zapata.conf. The options are "inband" > > (default) or "outofband". This only affects the two applications > > mentioned above. > > Thank you for that information. I have now updated the wiki of > zapata.conf.Still, like you said, it is better to explicitly set the PRI_CAUSE variable to the desired value. Isdn gives the user the ability to express problems etc in a detailed fashion. Might as wll use it. :) Peter