Hello, i have this problem : i phone person B . *if i hang up,* i have this "h" extension : exten => h,1,AGI(ende.agi) *if the person B hangs up* , i have this "h" extension : exten => h,1, DeadAGI(ende.agi) The problem is, i do not know where hangs up the first . How kann i combine AGI and DeadAGI in one programm ? Thank you -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100429/7753467b/attachment.htm
Hello, i have this problem : i phone person B . *if i hang up*, i have this "h" extension : exten => h,1,AGI(ende.agi) *if the person B hangs up* , i have this "h" extension : exten => h,1, DeadAGI(ende.agi) The problem is, i do not know where hangs up the first . How kann i combine AGI and DeadAGI in one programm ? Thank you -- Mit freundlichen Gruessen. Redouane -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100429/bd79a83a/attachment.htm
Redouane Zerargui wrote:> Hello, i have this problem : > i phone person B . > _/*if i hang up*/_, i have this "h" extension : exten => h,1,AGI(ende.agi) > _/*if the person B hangs up*/_ , i have this "h" extension : exten => > h,1,DeadAGI(ende.agi) > > The problem is, i do not know where hangs up the first . How kann i > combine AGI and DeadAGI in one programm ? > Thank you > > -- > Mit freundlichen Gruessen. > RedouaneHi It is irrelevant who hangs up, you want to just use DeadAGI in the h extension Ish -- Ishfaq Malik Software Developer PackNet Ltd Office: 0161 660 3062
> It is irrelevant who hangs up, you want to just use DeadAGI in the h > extensionI wish that would be the case, but at least on 1.4 I see: [Apr 30 14:59:38] -- Executing [h at master-route:1] DeadAGI(...) in new stack [Apr 30 14:59:38] WARNING[27845]: res_agi.c:2160 deadagi_exec: Running DeadAGI on a live channel will cause problems, please use AGI The good news is, we run tens of thousands of calls every day through this box and about half of them spit out this warning, but it never caused any problems for over a year. Thus this warning is probably safe to ignore. Luki
On 4/30/2010 6:03 PM, Luki wrote:>> It is irrelevant who hangs up, you want to just use DeadAGI in the h >> extension >> > I wish that would be the case, but at least on 1.4 I see: > > [Apr 30 14:59:38] -- Executing [h at master-route:1] DeadAGI(...) in new stack > [Apr 30 14:59:38] WARNING[27845]: res_agi.c:2160 deadagi_exec: Running > DeadAGI on a live channel will cause problems, please use AGI > > The good news is, we run tens of thousands of calls every day through > this box and about half of them spit out this warning, but it never > caused any problems for over a year. Thus this warning is probably > safe to ignore. > > Luki > >Agreed. We run DeadAGI for a considerable number of calls since it has the ability to run post-hangup cleanup no matter which side hangs up (unlike AGI). We see this warning constantly, and ignore it... constantly. N.
Hi Luki: ? 2010?05?01? 06:03, Luki ??:> The good news is, we run tens of thousands of calls every day through > this box and about half of them spit out this warning, but it never > caused any problems for over a year. Thus this warning is probably > safe to ignore.We run tens of thousands of call every day too. Call is controlled by AGI , and the asterisk version is 1.2.24. I find memory leak in asterisk. After serveral weeks, the memory used by asterisk will reach 1.2 GB or higher. Each time I have to restart to asterisk, and the memory leak will repeat. I wonder if you have the memory leak problem? Which version asterisk you use? Thanks for reply. Regards, Chen Xueqin
> We run tens of thousands of call every day too. Call is controlled > by AGI , and the asterisk version is 1.2.24. I find memory leak in > asterisk. After serveral weeks, the memory used by asterisk will reach > 1.2 GB or higher. Each time I have to restart to asterisk, and the > memory leak will repeat. > > I wonder if you have the memory leak problem? Which version asterisk you > use? Thanks for reply.No, no memory leak here. Memory usage: 58 MB after: System uptime: 25 weeks, 5 days, 12 hours, 39 minutes, 52 seconds. Asterisk version 1.4.23.1 (with about 25 custom, in-house patches). This particular box only handles signaling from a dozen static peers. No registration, no media (directrtpsetup=yes), no NAT, no transcoding, no MOH... but it does use realtime for SIP and IAX, and AGI and DeadAGI for routing. Luki
CHEN XUEQIN wrote:> Hi Luki: > > ? 2010?05?01? 06:03, Luki ??: > > >> The good news is, we run tens of thousands of calls every day through >> this box and about half of them spit out this warning, but it never >> caused any problems for over a year. Thus this warning is probably >> safe to ignore. >> > > > > We run tens of thousands of call every day too. Call is controlled > by AGI , and the asterisk version is 1.2.24. I find memory leak in > asterisk. After serveral weeks, the memory used by asterisk will reach > 1.2 GB or higher. Each time I have to restart to asterisk, and the memory > leak will repeat. > > I wonder if you have the memory leak problem? Which version asterisk you > use? Thanks for reply. > > > Regards, > Chen Xueqin > >Did you really mean 1.2.24? or was that a typo? You probably should, at the least up to the last version of 1.2, or, 1.2 Luddites not withstanding, move to a late 1.4 version If all else fails, automatically reboot once a week at some quiet time JMO John Novack -- Dog is my co-pilot
On Sat, 1 May 2010, SIP wrote: [snip]> We run DeadAGI for a considerable number of calls since it has the > ability to run post-hangup cleanup no matter which side hangs up (unlike > AGI).[snip] When a channel hangs up, Asterisk sends a SIGHUP signal to the AGI. If the AGI did not establish a handler for the SIGHUP, the AGI exits. If the AGI established a handler, the AGI can choose to ignore the signal or execute appropriate code -- like clean up files, write a CDR to the database, etc. If the AGI is started when the channel is "live," you should use agi() and catch signals appropriately. If the AGI is started when the channel is "dead," you should use deadagi(). -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com Voice: +1-760-468-3867 PST Newline Fax: +1-760-731-3000