rkasprow

We just installed two TN-2501AP VAL boards (2 locations) and I'm having a little bit of a FTP issue. The board accepts FTP connections from the Voice Over LAN Manager software (java app) and is apparently the method of file (.wav) transfer.

You can FTP also via Windows command line FTP IF you enable the file system and login on the board through the following command > enable filesystem board 03B04 login user password

It appears that when you use the VAL manager, it starts AND stops the file system on the board. Meaning, I can connect to and from the VAL board with the login I enabled UNTILL I use the VAL manager. When the VAL Manager is used, the file system is disabled and command line FTP fails unless you enable the file system again with the above command.

As I said, command line FTP (Windows) works without a problem but any GUI based FTP connects but fails to retrieve the files in the directory when asked for a listing. This was verified with three different GUI based FTP clients. This one I can't figure out. The files are there but the FTP clients cannot see them. When I do a permissions check, R, W & E are all disabled and cannot be enabled due to incorrect permission levels.

Here's what we are trying to do. We have a client within the call center that updates an announcement 3 times daily (or more during failure) via a console enabled phone. This leaves us open to "fat fingering" and overwritting announcements that shouldn't be. Our solution is the VAL board and FTP from an automated process, probably cronned CMS. With the file system being enabled and disabled frequently, an automated process will fail UNLESS I can automate the enable filesystem.

The embeded FTP client / server is:
220 VxWorks (5.4) FTP server ready

Command line FTP output:
C:\>ftp xxx.xxx.1xx.110
Connected to xxx.xxx.1xx.110.
220 VxWorks (5.4) FTP server ready
User (10.236.152.110:(none)):

History commands:
7/16 8:18 IP user1 enab filesystem board 03B04 logi
7/16 8:18 IP user1 disa filesystem board 03B04

Does anyone have suggestions on FTP'ing with a GUI based FTP client and or enabling the filesystem permanantly? The obvious would be to stop using the LAN Manager but ....

ahays

I'm sorry but I think I missed something. Why is it that the "client within the call center" cannot use VAL Manager?

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

PBXtech.info

 

rkasprow

Sorry, we have a business client in our call center (we're an out sourcer) that has the need to update the announcements. The location in question has 10+ "clients". The client would be considered who we're taking calls for, in the call center.

ahays

... and what's the problem with using VAL Manager to accomplish this? It was created to do exactly what you're describing ... move (FTP) files to and from the TN2501. Is there something I'm missing? Is VAL Manager not working for you?

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

rkasprow

The VAL manager works but we need to "automate" the upload of files via FTP and CMS (crontab).

The scenario:
1: Helpdesk technician records the network status message (via Windows PC)
2: Technician drops the .wav file onto a shared drive
3: CMS, via crontab grabs the file and pushes it to the 2501 via FTP

The status message is recorded three times daily under normal circumstances and at a higher frequency during outages (sometimes 10-20 times) until problems clear.

I cannot give access via LAN Manager to the Technician to upload the file, too risky.

The above scenario works in theory but fails when the LAN Manager enables and disables the filesystem on the board unless you manually enable the filesystem after each use of the L.M.

The graphical GUI would be nice instead of the command line. Again, it should work and I cannot understand how one works but not the other. I can put files on the board with the GUI but I can't see it. When I command line FTP into it, the file is there. Any ideas on why the GUI wouldn't display the files, they are not hidden. It is possibly a permissions issue but it boggles me why the command line has proper permissions while the GUI does not when using the exact same user / pass combo.

Make sense?

ahays

Sounds like you need a custom script to enable the file system. There are several terminal programs that emulate AT&T 4410 that can accomplish this ... Procomm Plus and Zoc being two of them. Perhaps the Technician can, as a part of the process, launch a terminal script that enables the file system and then drops the file onto the specific shared drive. This is the only way that I can think of to automate the process while giving extremely limited access to the Technician. It isn't the prettiest of ideas, but it might work for you.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

PBXtech.info

 

fataldata

I have a small problem. So rarely do I use the val board and ftp that I cannot find how to attach the uploaded file to my annoucement extension? The files are there as confirmed by a directory listing in ftp. Now how do i activate them?
I have tried creating a new announcement extension and named it the same as my uploaded file(without the .wav extension), this has not worked however. Do I need to create the extension prior to uploading the file?

__________________
Systems In Use:
S8700 CM3.0 and S8710 CM3.1.1

ahays

The filename will match the announcement name in "change announcements" except the .wav is assumed.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

fataldata

Thanks,
My problem must be something else then. Filenames match, I just wonder if there is an order. Like create the extension, record a placeholder announcement with a handset then upload a wav with the same name as the announcement with ftp. I've tried this with no success. I think the problem may be the wav file I am uploading. I've checked the encoding though and it seems fine. My biggest clue is the small file size when compared to other announcements. I'll let you know what happens.
Thanks again.

__________________
Systems In Use:
S8700 CM3.0 and S8710 CM3.1.1

ahays

Checked case sensitive names? No spaces?

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

nexSIP

make sure your .wav file is set to U-Law 8k 16bit. Correction 8bit not 16bit

If should give you an error if it does not upload properly.

__________________
http://www.nexsip.com
Communicate Openly and Freely

ahays

Correction/Clarification to the above file requirements from the manual (What’s New for Release 9.5, 555-233-418, Issue 1, July 2001):

In order to be compatible with the TN2501AP circuit pack and the DEFINITY system, announcement recordings must have the following parameters:

* CCITT A-Law or CCITT mu-Law companding format (do not use PCM)
* 8kHz sample rate
* 8-bit resolution (bits per sample)
* Mono (channels = 1)

Announcements that are recorded in this format occupy 8K Bytes per second of file space. For example, a 10-second announcement creates an 80KB wave file.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

nexSIP

my bad, I just looked at my VAL files and they were 8bit.

__________________
http://www.nexsip.com
Communicate Openly and Freely

fataldata

Problem resolved,
I wasn't paying attention and was sending the wav files in ascii mode in ftp. This caused the size discrepancy that I mentioned. My 8KB files were only showing up as 58 byte files on the val board. Thanks everyone for your help.

__________________
Systems In Use:
S8700 CM3.0 and S8710 CM3.1.1