238 - Move ParkNPage Snap-in Functions into Native CM Feature Set
in progress
Tom Lynn
Breeze Call Park and Page Snap-in has been announced end of Sale, but the service it provides is still useful and my enterprise relies heavily on its automatic park slot allocation capability. A small call center answering for hundreds of locations needs automatic selection of call park extensions from a pool that is ISOLATED to the site location.
Reference End of Sale notice at https://support.avaya.com/css/public/documents/101084077
IAUG
The volunteer team discussed this at length with Avaya. Although the snap-in is end of sale, it is not end of support. Avaya recognizes the value of the feature for customers. It is now targeted for inclusion in Aura 10.3 in 2025, and support will not go away before that time. The volunteer team is scheduled to follow up in 3Q25.
Avaya Responses
in progress
High priority for 2024.
RC
Avaya Responses: That's great to hear! I think this is a long lacking feature within CM.
Avaya Responses
under review
RC
Many of our IPO and Nortel customers have expressed a similar desire. Not for CPNP by name, but asking for many of the CPNP features. Just standard park slots without confusing FACs etc would be great.
CPNP built in to CM would be a wonderful value add, especially for customers who want off other systems.