Session Info

[avc859587618170]

These feels like a very basic question so I'll apologize ahead of time. Can anyone tell me what the intent is of the session. Meaning, if I have an application that is going to be monitoring multiple stations and agents for events, as well as answer/make calls, do I create just 1 Application session and use that session info for all the things it's doing? Or should I create a separate session for each "person" for instance? Does anyone have a best practices?

Thanks for any insight!

[jtb1]

one session will work fine and it is the best practice - assuming all the activity is related to a single AES. While multiple sessions will also work, you are just adding overhead to the application and AES, and making the application logs messier. Separate sessions would be required if the application was connecting to more than one AES - however you really only need one session per AES - all the monitoring and requests can be done within that session.

The point of a session is to tie certain allocated objects to something that is maintained with a keep alive mechanism. If the keep alive fails, then after a timeout the objects are released. More specifically device monitors consume resources in Communication Manager, and they create a certain amount of workload. If there is no longer an application 'out there' listening for the events created by a monitor (i.e. the keep alive has failed), the monitors can and should be released.

[avc859587618170]

That is good to know Martin! Thanks as always!!