Colin Anderson
2006-Dec-19 12:56 UTC
SPAM-LOW: Re: [asterisk-users] .Call files do not seem to wo rk
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. -----Original Message----- From: Lee [mailto:lee@datatrakpos.com] Sent: Tuesday, December 19, 2006 11:58 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: SPAM-LOW: Re: [asterisk-users] .Call files do not seem to work Tzafrir Cohen wrote:> On Tue, Dec 19, 2006 at 12:44:39PM -0500, Lee wrote: >>> In the CLI: >>> >>> sip show peer axVoice >>> show dialplan main_menu >>> set verbose 3 >>> >>> >>> Then drop the call file >>> >>> What is the CLI trace of the above? >>> >> Hi, thanks for responding. Please see the output below. >> >> Please note that moving a call file into /var/spool/asterisk/outgoing >> did not produce any CLI output. The file was copied correctly, I >> believe and not present in the /outgoing directory when I checked with a >> simple ls command. >> >> # cp lee.call test.call >> # mv test.call /var/spool/asterisk/outgoing > > Are both the current directory and /var/spool/asterisk/outgoing on the > same filesystem? If not, a 'mv' is implemented through a copy. > > Anyway, you left out the CLI output of dropping trhe file. > > Can Asterisk read that file? Write to it? >Hi, As I mentioned above, the action of dropping a .call into the /outgoing directory did not produce any CLI output. I did this through 2 putty sessions. The first, we setup to watch the CLI output and the second was to use the commandline to move the .call into the /outgoing directory. Asterisk must be doing *something* with the file (if just deleting it) because if I check the /outgoing directory after I move the file, there is no file there. It's deleted. -- 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
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