asterisk users - Dec 2006 - SPAM-LOW: Re: .Call files do not seem to wo rk

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:lee@datatrakpos.com]
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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 614.call
Type: application/octet-stream
Size: 159 bytes
Desc: not available
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20061219/700ba54f/614.obj

Colin Anderson wrote:
> 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. 
Looking at your file, there are tabs between the pairname/separator and 
the actual value.  The example on the wiki didn't see to use tabs and I 
guess that was it because it's working now...kinda.

Good eye and thanks to everyone else of the help.


-- 

Warm Regards,

Lee