The only other thing that comes to mind is that .call files are very sensitive to whitespace; you may have unintentially padded the .call file with whitespace or tabs that it does not like.
The attached .call file works on my 1.0.9 server. Maybe it can give you some insight. -----Original Message----- From: Lee [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 19, 2006 2:45 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: SPAM-LOW: Re: [asterisk-users] .Call files do not seem to wo rk Colin Anderson wrote: > If you are using Windows to generate the .call files, make sure they are in > Unix format (LF only at EOL, not CR+LF) - Notepad makes bad Unix files. Use > Crimson Editor www.crimsoneditor.com to make the file, and click Document > > File Format > Unix Format. > > I ran into this same problem, and it turns out my Asterisk install would not > use Windows-formatted text files, it would just ignore them and delete them. > > Hi Colin, Thanks for responding. I've run into the problem elsewhere myself. Alas, I wrote the call file using nano on the linux box through ssh/putty. -- Warm Regards, Lee _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
614.call
Description: Binary data
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
