This question has now been fixed -- it was an internal error not related to easylink that was causing the problem therefore I cleared the question text as it is irrelevant in this case.
Thanks,
Roy