Incorrect parsing of hostname and port parameters from MCTR output

In some case (ca. in every second run) the hostname and port parameters from the output of the main controller is not parsed properly, therefore the sh command starting the HC is invalid. For example: Erroneous case:

...
Using configuration file: /home/enikdim/Eclipse_workspaces/Generic_AutoLT/Generic_AutoLT/AutoLT_new.cfg
MC@seroius02093: Listening on TCP port 37773.
MC information:
...

sh -c ssh $TTCN_HOST "setenv TTCN3_LICENSE_FILE $HOME/.TTCNv3/license.dat; cd /home/enikdim/Eclipse_workspaces/Generic_AutoLT/Generic_AutoLT/bin; ./../AutoLT MC seroius02093";

Working case:

...
Using configuration file: /home/enikdim/Eclipse_workspaces/Generic_AutoLT/Generic_AutoLT/AutoLT_new.cfg
MC@seroius02093: Listening on TCP port 43216.
MC information:
...

sh -c ssh $TTCN_HOST "setenv TTCN3_LICENSE_FILE $HOME/.TTCNv3/license.dat; cd /home/enikdim/Eclipse_workspaces/Generic_AutoLT/Generic_AutoLT/bin; ./../AutoLT seroius02093 43216";