Issues with Auto Attendant WAV file uploads.

[Egghead2]

Hi All,

Hopefully I can get some direction on this problem.

I have an issue with uploading any WAV files to an AA via Director from a few remote PCs.

Scenario
========

I have 2 client PC's (supposedly identical SOE builds)...

For the successful PC when trying to upload a WAV file to AA on the server via Director, a Wireshark trace shows the following;

File Transfer Protocol (FTP)
PORT 10,1,5,37,236,92\r\n
Request command: PORT
Request arg: 10,1,5,37,236,92
Active IP address: 10.1.5.37 (10.1.5.37)
Active port: 60508

File Transfer Protocol (FTP)
200 PORT command successful.\r\n
Response code: Command okay (200)
Response arg: PORT command successful.



But for a failed PC trying to upload the same WAV, Wireshark trace shows the following:-

File Transfer Protocol (FTP)
PORT 127,0,0,1,247,151\r\n <---------------- Local host IP address inserted
Request command: PORT
Request arg: 127,0,0,1,247,151
Active IP address: 127.0.0.1 (127.0.0.1)
Active port: 63383
Active IP NAT: True <---------------- Looks like NATing is occurring somewhere on PC.

501 Server cannot accept argument.\r\n
Response code: Syntax error in parameters or arguments (501)
Response arg: Server cannot accept argument.

The end user has verified that there is no NAT on the failed PC, and each PC is SOE build identical.

I have nearly exhausted all avenues to resolve.
Any ideas would be much appreciated.

 

[jamie2]

Maybe a dumb question, but are you trying to upload the same exact .wav file on both PC's? The .wav's have a certain format....

 

[Egghead2]

Hi jamie2

Yes the file is the same. The only difference in each scenario is the end user PC's, which apparently have the same SOE software build on each.
Also I forgot to mention that the Wireshark trace is taken from each PC NIC port.
The end users have also done some further testing with logging different users into each PC and it seems that the fault is PC specific rather than user profile specific.