When configuring Single Number Reach Remote Destination Profiles, is the best practice to configure the profile with the same device pool, CSS, etc as the user's physical handset, or treat it differently? (e.g. Separate Device Pool. etc)
All my RDP's are built exactly like the desk phone, mainly for simplicity of CSS/partition routing and device pool organization. This is also because I want the Remote Destination to egress the same trunk as the users desk phone. The onyl other scenario I might consider is if I wanted to have the Remote Destination call act differently than treating it like a simultaneous call forward.
I am confused about RONA. I am looking at Precision Queue Interval report that I run at the end of the day to get daily totals. One queue has 110 calls offered, 34 RONA, 76 Handled, and 0 abandoned. Are RONA calls considered handle...
(view in My Videos)
This event had place on Thursday 22, October 2020 at 10hrs PDT
Contact Center call flows are fundamental to the successful implementation and support of Customer Voice Portal (CVP) and IP Interactive Voice Response (IP IVR) deplo...
there is a lot of evolution on Hybrid services for On-Premises CUCM/BE6k solution.
These kind of services allow customers to continue operate with on-premises Cisco Collab model and at same time get amazing features from the Webex cloud.&...
Customer received error in the morning that they could not record sessions because the storage was full. After they deleted approximately 40 recordings, and tried to record again in the afternoon - they still received the error: Webex Recorder...