See this thread: <
http://permalink.gmane.org/gmane.comp.voip.sipx.devel/10591>
Scott writes:
"In general, it's not a good idea to make the correct operation of a sipXecs feature depend on the administrator having correctly set up the configuration of some other system (witness all the trouble we've had with DNS and DHCP). In this case, allowing an optional directory path would seem to add some flexibility that would reduce the need for external configuration (essentially, that path needs to be configured either in the ftp server or in our system anyway, so I think it's better if it's in ours)."
Please note that sipXconfig should not try to create remote directory. If it does not exist we should treat it as an error condition.
XCF-2044is:1. connect on the ftp server with the supplied username/password
2.upload the backups in the path exposed by the supplied username/password in directories created with names based on the current time/date (the same name format as for local backup)
Based on Scott suggestion this has to be changed into:
1. connect on the ftp server with the supplied username/password
2. on the ftp server - in the path exposed by the supplied username/password 'cd' to directory specified by sipXconfig
If that fails, stop (and log the error)
3.upload the backups in this directory in directories created with names based on the current time/date (the same name
format as for local backup)