bruce bruce
2010-Aug-10 16:51 UTC
[asterisk-users] How to determine which party hangup the call? cause of Hang-up needed.
Hi Everyone Asterisk 1.4.33 is running with Sangoma/Dahdi for analogue lines to Bell Canada. User claims that call hangup without any interferance to the phone set. Is there ANYWAY to find out which party hang-up the call or if the call was cut-off due to other reasons? I checked the *"asteriskcdrb"* table and it's pretty much useless in this case as it only logs the duration and other properties but not cause of the Hangup. /var/log/asterisk/full [Jul 10 10:37:02] VERBOSE[29366] logger.c: == Manager 'admin' logged off from 127.0.0.1 [Jul 10 10:37:09] VERBOSE[29348] logger.c: -- Executing [h at macro-dialout-trunk:1] Macro("SIP/1007-0000069a", "hangupcall|") in new stack [Jul 10 10:37:09] VERBOSE[29348] logger.c: -- Executing [s at macro-hangupcall:1] GotoIf("SIP/1007-0000069a", "1?skiprg") in new stack [Jul 10 10:37:09] VERBOSE[29348] logger.c: -- Goto (macro-hangupcall,s,4) Thanks, Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100810/c9c19e7c/attachment.htm
Philipp von Klitzing
2010-Aug-10 18:41 UTC
[asterisk-users] Re: How to determine which party hangup the call? cause of Hang-up needed.
Hi!> Is there ANYWAY to find out which party hang-up the call or if the call > was cut-off due to other reasons?The only way - apart from putting DAHDI or SIP into debug mode - I can think of is to use the 'g' option of Dial(): If the remote side hangs up then 'g' will come into effect; if the local side hangs up this will not happen. But don't ask me what happens if Asterisk in between the two (as B2BUA man-in-the-middle) decides to to hang up... is it in this case acting "on behalf" of one of the two call legs? In general: It would be a great help if Asterisk provided an easy way to get at this information, i.e. who was it that hung up a call. Philipp
Faisal Hanif
2010-Aug-11 04:33 UTC
[asterisk-users] How to determine which party hangup the call? cause of Hang-up needed.
read the value of var ${HANGUPCAUSE} next line to dial command. Regards, Faisal Hanif /VoIP Manager /**Vopium A/S On 8/10/2010 9:51 PM, bruce bruce wrote:> > Hi Everyone > > Asterisk 1.4.33 is running with Sangoma/Dahdi for analogue lines to > Bell Canada. > > User claims that call hangup without any interferance to the phone set. > > Is there ANYWAY to find out which party hang-up the call or if the > call was cut-off due to other reasons? > > I checked the *"asteriskcdrb"* table and it's pretty much useless in > this case as it only logs the duration and other properties but not > cause of the Hangup. > > > /var/log/asterisk/full > > [Jul 10 10:37:02] VERBOSE[29366] logger.c: == Manager 'admin' logged > off from 127.0.0.1 > [Jul 10 10:37:09] VERBOSE[29348] logger.c: -- Executing > [h at macro-dialout-trunk:1] Macro("SIP/1007-0000069a", "hangupcall|") in > new stack > [Jul 10 10:37:09] VERBOSE[29348] logger.c: -- Executing > [s at macro-hangupcall:1] GotoIf("SIP/1007-0000069a", "1?skiprg") in new > stack > [Jul 10 10:37:09] VERBOSE[29348] logger.c: -- Goto > (macro-hangupcall,s,4) > > > Thanks, > > Bruce >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100811/56ac9744/attachment.htm
Philipp von Klitzing
2010-Aug-11 05:16 UTC
[asterisk-users] Re: How to determine which party hangup the call? cause of Hang-up needed.
> read the value of var ${HANGUPCAUSE} next line to dial command.So how can you be sure this has been populated by PRI and not by SIP? This will not tell you which side hung up. Philipp
Faisal Hanif
2010-Aug-11 05:45 UTC
[asterisk-users] How to determine which party hangup the call? cause of Hang-up needed.
If Caller party hangups next to dial line wil not be executed but control will hit to h extension of fame context but if Called party hangups next to dial ine will be executed. Faisal Hanif On 8/11/2010 10:16 AM, Philipp von Klitzing wrote:>> read the value of var ${HANGUPCAUSE} next line to dial command. > So how can you be sure this has been populated by PRI and not by SIP? > This will not tell you which side hung up. > > Philipp > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100811/29a38c3f/attachment.htm