Config file parsers frequently "read until end of line" where end of line is a CR or LF. No CR or LF, no last line read. I think that bug was fixed fairly recently in Asterisk.
Other software has similar issues in the past. Nitesh Divecha wrote: > Thanks Eric, > > It solved the problem by having a blank line... I wonder why we need a > blank line... > > Cheers, > Nitesh > > > > Eric "ManxPower" Wieling wrote: >> Make sure you have a blank line at the end of your .call file. >> >> Nitesh Divecha wrote: >> >>> Hello All, >>> >>> Something strange I found that my .call file is running twice... >>> Just after 60 sec it will run again, without any application invoking it. >>> >>> This is my .call file: - >>> ================= >>> Channel: SIP/xo-out/19097773456 >>> Callerid: 9097773456 >>> MaxRetries: 3 >>> RetryTime: 30 >>> WaitTime: 15 >>> Context: custom-900 >>> Extension: 900 >>> Priority: 1 >>> >>> I am running Asterisk 1.2.18 on CentOS 4.5. >>> >>> Anyone can help? >>> >>> Cheers, >>> Nitesh >>> >>> _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
