[asterisk-bugs] [Asterisk 0014704]: Using | symbol instead of ', 's in call file causes segfault when using RetryDial

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=14704 
====================================================================== 
Reported By:                ajfisher
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14704
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.7-rc1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-03-19 09:25 CDT
Last Modified:              2009-04-03 13:33 CDT
====================================================================== 
Summary:                    Using | symbol instead of ','s in call file causes
segfault when using RetryDial
Description: 
The following call file causes asterisk 1.6.0.6 to segfault.  NB. $NUMBER
isn't really a variable.  I've just sanitized.  Platform is 32bit Centos
5.2, but I think that's irrelevant.

Channel: SIP/provider/$NUMBER
RetryTime: 5
MaxRetries: 5
Context: default
Application: RetryDial
Data: please-wait|5|5|SIP/provider/$NUMBER|60
Account: testAccount

Using commas works as expected, but a segfault is an over reaction! :)
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-03 13:33 tilghman       Status                   ready for testing =>
closed
2009-04-03 13:33 tilghman       Resolution               open => suspended   
======================================================================