| Summary: | ASTERISK-00358: Spaces after extension number cause error for Dial | ||
| Reporter: | sdolloff (sdolloff) | Labels: | |
| Date Opened: | 2003-10-07 13:22:06 | Date Closed: | 2004-09-25 02:49:15 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | exten => 256 ,1 ,Dial(SIP/256,20) causes an error while exten => 256,1,Dial(SIP/256,20) does not. File pbx.c, Line 1153 (pbx_extension_helper): No application ' Dial' for extension (default, 256, 1) | ||
| Comments: | By: Brian West (bkw918) 2003-10-07 19:52:12 exten => 256 ,1 ,Dial(SIP/256,20) <-- isn't valid while: exten => 256,1,Dial(SIP/256,20) does not. <-- is valid. The key is no spaces. By: John Todd (jtodd) 2003-10-19 20:12:13 So, is this a request to make it so that Asterisk does not care about spaces in the wrong places in a dialplan? I'm not sure I'm clear on the reason for this note. Asterisk currently uses spaces only between comparitors and values, and between the first three elements of each line ("exten => 1,1,NoOp") By: sdolloff (sdolloff) 2003-10-20 09:11:41 I am new to asterisk and the individual on IRC that helped me figure out what was wrong asked me to submit a bug report on it. I guess the behavior was just unexpected from a newbie perspective. By: Brian West (bkw918) 2003-11-22 16:18:00.000-0600 Should this be closed? or should we think about making asterisk a bit loose on the extensions.conf parsing? I vote for not doing that. By: Brian West (bkw918) 2003-11-23 16:22:10.000-0600 Fixed in CVS | ||