An ASO Slave Manager represents one ASO slave process in the SPO. A slave does not necessarily always have a connection to an actual ASO. (ASOs can time out and be stopped. The ASO process will exit to release resources but the ASO Slave Manager will continue to be active.) When calls are queued to a slave and there is no active ASO slave process, a new ASO will be started automatically so long as there were no previous errors in the ASO.

Each slave is assigned an identifier when it is created. This identifier is unique for the lifetime of the SPO process.