Can gfal2 indicate the origin of errors (source/destination) when using GridFTP?

An indication of the origin of an error would be very useful in FTS transfer debugging.

{{Tue Jul 12 10:36:33 2016 INFO bytes: 44040192, avg KB/sec:195, inst KB/sec:102, elapsed:225
Tue Jul 12 10:36:35 2016 ERROR TRANSFER globus_ftp_client: the server responded with an error 500 Command failed. : Handle not in the proper state
Tue Jul 12 10:36:35 2016 WARNING Recoverable error: [70] TRANSFER globus_ftp_client: the server responded with an error 500 Command failed. : Handle not in the proper state
Tue Jul 12 10:36:35 2016 INFO Report FAILED back to the server
Tue Jul 12 10:36:35 2016 INFO Send monitoring complete message
Tue Jul 12 10:36:35 2016 INFO Complete message content: CO

{"$a$":"2016-07-12-0832__eospublicftp.cern.ch__xdpmhn01.tsy.cern.ch__346061487__9c4aaeb4-4803-11e6-be6f-02163e00f00c","$b$":"fts3-pilot.cern.ch","$c$":"","$d$":"","$e$":"dteam","$f$":"gsiftp://eospublicftp.cern.ch/eos/ftstest/more_1GB/testFile_more_1GB365","$g$":"gsiftp://xdpmhn01.tsy.cern.ch/dpm/tsy.cern.ch/home/dteam/more_1GB/testFile_more_1GB365","$h$":"eospublicftp.cern.ch","$i$":"xdpmhn01.tsy.cern.ch","$j$":"","$k$":"","$l$":"gsiftp://eospublicftp.cern.ch__gsiftp://xdpmhn01.tsy.cern.ch","$m$":"1468312364569","$n$":"","$o$":"","$p$":"","$q$":"","$r$":"","$s$":"10800","$t$":"1800","$u$":"500","$v$":"TRANSFER","$w$":"TRANSFER","$x$":"COMMUNICATION_ERROR_ON_SEND","$y$":"Error","$z$":"","$0$":"4","$1$":"0","$2$":"0","$3$":"0","$4$":"1712324608","$5$":"","$6$":"","$7$":"","$8$":"","$9$":"","$10$":"","$11$":"TRANSFER globus_ftp_client: the server responded with an error 500 Command failed. : Handle not in the proper state ","$12$":"1468312364433.000000","$13$":"1468312595966.000000","$14$":"urlcopy","$15$":"/DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=ftssuite/CN=737188/CN=Robot: fts3 testsuite","$16$":null,"$17$":null,"$18$":"0","$19$":"0","$20$":"false","$21$":"UNKNOWN","$22$":"1"}

Tue Jul 12 10:36:36 2016 INFO Closing the log stream}}