I'm having an issue with my recorder retention policies not storing recordings in the specified location.

For each of our customers that record calls, we configure the retention policy so that if it matches that customer's workgroup(s) the recording should be stored at
\\<storagepath>\customername\

Down toward the bottom of our retention policies, we have a default storage location \\<storagepath>\ that acts as a catch-all.

The issue is that all of the recordings are being stored at the default location and not honoring the path specified in the retention policy for each individual customer.
This shouldn't happen since recorder policies are applied in the order in which they are configured.

I can't find any indication as to why this is happening in the recorderserver logs, so I figured it'd be worth reaching out here for help before submitting a case.

Anyone else experienced this?

Recorder policies process from top to bottom and all matches are processed unless you specifically put in a "Stop processing more policies" action.

So, if you have your policies set up in this order:

1. Customer A retention location
2. Customer B retention location
3. Default retention location

I'm having an issue with my recorder retention policies not storing recordings in the specified location.

For each of our customers that record calls, we configure the retention policy so that if it matches that customer's workgroup(s) the recording should be stored at
\\<storagepath>\customername\

Down toward the bottom of our retention policies, we have a default storage location \\<storagepath>\ that acts as a catch-all.

The issue is that all of the recordings are being stored at the default location and not honoring the path specified in the retention policy for each individual customer.
This shouldn't happen since recorder policies are applied in the order in which they are configured.

I can't find any indication as to why this is happening in the recorderserver logs, so I figured it'd be worth reaching out here for help before submitting a case.

Anyone else experienced this?

So, if I understand correctly, the order should be:

1. Default location
2. Customer A unique location
3. Customer B unique location

Is that what you're saying?

Thanks for the prompt response!

Recorder policies process from top to bottom and all matches are processed unless you specifically put in a "Stop processing more policies" action.

So, if you have your policies set up in this order:

1. Customer A retention location
2. Customer B retention location
3. Default retention location

I'm having an issue with my recorder retention policies not storing recordings in the specified location.

For each of our customers that record calls, we configure the retention policy so that if it matches that customer's workgroup(s) the recording should be stored at
\\<storagepath>\customername\

Down toward the bottom of our retention policies, we have a default storage location \\<storagepath>\ that acts as a catch-all.

The issue is that all of the recordings are being stored at the default location and not honoring the path specified in the retention policy for each individual customer.
This shouldn't happen since recorder policies are applied in the order in which they are configured.

I can't find any indication as to why this is happening in the recorderserver logs, so I figured it'd be worth reaching out here for help before submitting a case.

Anyone else experienced this?

So, if I understand correctly, the order should be:

1. Default location
2. Customer A unique location
3. Customer B unique location

Is that what you're saying?

Thanks for the prompt response!

Recorder policies process from top to bottom and all matches are processed unless you specifically put in a "Stop processing more policies" action.

So, if you have your policies set up in this order:

1. Customer A retention location
2. Customer B retention location
3. Default retention location

I'm having an issue with my recorder retention policies not storing recordings in the specified location.

For each of our customers that record calls, we configure the retention policy so that if it matches that customer's workgroup(s) the recording should be stored at
\\<storagepath>\customername\

Down toward the bottom of our retention policies, we have a default storage location \\<storagepath>\ that acts as a catch-all.

The issue is that all of the recordings are being stored at the default location and not honoring the path specified in the retention policy for each individual customer.
This shouldn't happen since recorder policies are applied in the order in which they are configured.

I can't find any indication as to why this is happening in the recorderserver logs, so I figured it'd be worth reaching out here for help before submitting a case.

Anyone else experienced this?