With respect, whilst using 5 digits reduces the possibility of a clash it is still just a kludge!... rather than doing it properly and checking against existing sessions!
Our licence only allows us to run 6.3 and we can't afford to upgrade especially as it does all we need.
We neatly circumvent the issue by always appending a letter to the code after the client has connected!
Please could you reconsider this.
Scenario: A support assistant creates a new session to enable him to remotely resolve an issue for a customer. The session is automatically created with a randomly assigned session code, however by chance the new session code is a duplicate of an existing session code and so the customer is connected to an existing session (which is currently parked). As there are no warnings or checks the support assistant will only know that for some unknown reason his customer has been unable to connect to the newly created session and the customer is left frustrated and unhappy because despite following instructions to the letter he is unable to receive remote support.
Clearly this behavior in both unintentional and unexpected.
According to wikipedia "A software bug is s an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways". Most IT professionals, myself included, would concur with that definition so how can you can classify this as not a bug when it clearly is?
John Feeney-Howells. BSc, CEng, CISP
Customer support service by UserEcho