Defining Callsigns

[Kent Kasten 868422]

I have a question when it comes to selecting or using call signs as part of the [positions] area of the ESE file. The debate is over how ES sees and uses call signs. For example, its possible that if a controller signed on with CHI_1A_APP which is [Mod - Happy Thoughts]igned to 133.620, that another controller can also sign on with CHI_2A_APP with the same frequency then both controllers would be in control of the same airspace, so long as both are properly defined in the ESE and settings file.

 

So my question becomes, can ES take a generic position definition such as CHI_APP and allow other undefined positions such as CHI_1A_APP or CHI_2A_APP to be recognized by ignoring the middle portion of the identifier (e.g. _1A or _2A)? If so, how is it done?

 

Thanks.

Kent

[Gergely Csernak]

Kent,

 

All ES clients are running individually. The are not communicating to each other to decide who is responsible for a sector and who is not. That way there is a way for such mistakes when both clients think that an airspace belongs to them. ES identifies positions by callsign prefix, postfix and frequency. So if you hace CHI prefix, APP postfix then all CHI_APP, CHI_1A_APP, CHI_2A_APP will be [Mod - Happy Thoughts]igned to that position.

[Kent Kasten 868422]

Thanks for the info.

 

Kent

[Michael Pike]

Just for info, we have several cases where the centre characters in the call sign are used to differentiate sectors. EGLL_N_APP and EGLL_S_APP are two different positions; but they have different frequencies so ES handles that correctly as well.