detect and handle all possibilities of stream break down by remote server (ADS) in EMA
There could be a whole host of reasons why a stream may be closed by the ADS. Rather then trying to identify all possible combinations, it is better to try and understand the various elements of a status msg. Please see my reply to a previous similar question
As well as my reply, in the above post, also refer to Brian Sandri's recommendation of reading Appendix A of the ETA Developers Guide - the 'Item and Group State Decision Table' which provides recommendations on what actions an application should take (or not).
NOTE: It is not advised to make decisions based on any string values i.e. Status Text - as these are subject to change.