Archived Post

The provided text snippet appears to be a discussion on Avaya coverage paths configuration. It seems that the topic revolves around the correct implementation of next path functionality in coverage paths. To provide a suitable answer, we'll need to summarize the key points from the snippet.

Key Points:

• The conversation is centered around configuring coverage paths to ensure proper call routing.
• The user "ToxicMyst" has created two coverage paths, 100 and 101, with specific criteria for each path.
• However, when no one picks up a call in path 100, it doesn't automatically route the call to path 101 as expected.

Possible Solutions:

• A possible solution suggested by "AvayaTier3" is to set the All inside/outside criteria to 'y' for path 101. This ensures that when the first path doesn't cover the call, the next path will.
• Another approach mentioned by "mikeydidit" involves using SAC/DND (Selective Call Answering/Do Not Disturb) to make the next path work. By setting SAC 'n' on the first path and 'y' on the second path, you can activate it to go to the second path.

Related Threads:

• There are several related threads discussing similar issues with Avaya coverage paths.
• Some of these threads include questions about SMDR reporting, CM coverage issues, attendant coverage to VDN, and coverage answer.

To provide a comprehensive answer, we would need more information about the specific configuration details. However, based on the provided snippet, it seems that setting the All inside/outside criteria or using SAC/DND could be viable solutions for ensuring proper next path functionality in Avaya coverage paths.