Summary: | ASTERISK-18060: Playback in h exten triggers a null pointer in sip_setoptions resulting in a crash | ||
Reporter: | Neil Cadman (cadey) | Labels: | |
Date Opened: | 2011-06-23 07:54:52 | Date Closed: | 2011-07-20 12:41:44 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | |
Versions: | 1.8.4 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | CentOS 5.6 | Attachments: | ( 0) backtrace.txt |
Description: | Using the following Dial plan on a standard configure/make/install causes asterisk to crash when you perform an attended Xfer between channels. 8001 phones 8002, 8002 Attended Transfers 8001 to 8000 [Default] exten => _8XXX,1,Macro(ToDDI,${EXTEN}) [Hangup] exten => 1,1 Playback(beep) exten => 1,n Playback(beep) exten => 1,n Playback(beep) exten => 1,n Playback(beep) [macro-ToDDI] ;======================================================= ;==== Call extension and redirect to mail box if needed ;======================================================= exten => s,1,Dial(SIP/${ARG1}, 10, tTF(Hangup^1^1)) exten => s,n, Goto(s-$DIALSTATUS},1) ; the u in the VoiceMail tells the mailbox to play the unavaliable message exten => s-NOANSWER,1,Voicemail(${ARG1}@OBTamVM,u) exten => s-NOANSWER,n,Hangup() ; the b in the VoiceMail tells the mailbox to play the busy message exten => s-BUSY,1,Voicemail(${ARG1}@OBTamVM,b) exten => s-BUSY,n,Hangup() ; the u in the VoiceMail tells the mailbox to play the unavaliable message exten => _s-.,1,Voicemail(${ARG1}@OBTamVM,u) exten => _s-.,n,Hangup() exten => h,1,Goto(Hangup,1,1) | ||
Comments: | By: Neil Cadman (cadey) 2011-06-23 07:56:10.668-0500 Core crash log By: Gregory Hinton Nietsky (irroot) 2011-06-23 08:18:19.299-0500 The problem here is using playback in h exten stream file trigers a null pointer in sip_setoptions. should null pointer be checked or should playback not be allowed in h and bail if the channel is dying c all of the above ... happy to do it By: Richard Mudgett (rmudgett) 2011-06-23 10:19:45.312-0500 This is probably no longer a problem. The 1.8 branch has a fix that should avoid this. Please test. By: Leif Madsen (lmadsen) 2011-07-20 12:41:44.743-0500 I'm going to close this based on Richards update. If this is still an issue please request this issue be reopened. Thanks! |