Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-24-2018, 11:29 AM
crodie crodie is offline
Aspiring Member
 
Join Date: Apr 2018
Posts: 2
crodie has 10 reputation points
Default Programming COR for Service Observing

We are using a CM 7. I want to setup a separate COR for each department so that the supervisor can only observe their respective ACD agents and not ACD agents from other departments. Any suggestions would be greatly appreciated.
Reply With Quote
  #2  
Old 05-01-2018, 11:55 AM
hurdk hurdk is offline
Brainiac
 
Join Date: Oct 2015
Posts: 64
hurdk has 11 reputation points
Default

Assign a COR where service observance is set as can be for the users to observe and then a COR where it is set as can be the observer for whoever will be observing.

CLASS OF RESTRICTION

COR Number: 1
COR Description: Example

FRL: 0 APLT? y
Can Be Service Observed? n Calling Party Restriction: none
Can Be A Service Observer? n Called Party Restriction: none
Time of Day Chart: 1 Forced Entry of Account Codes? n
Priority Queuing? n Direct Agent Calling? n
Restriction Override: none Facility Access Trunk Test? n
Restricted Call List? n Can Change Coverage? n

Access to MCT? y Fully Restricted Service? n
Group II Category For MFC: 7 Hear VDN of Origin Annc.? n
Send ANI for MFE? n
MF ANI Prefix: Automatic Charge Display? n
Hear System Music on Hold? y PASTE (Display PBX Data on Phone)? n
Can Be Picked Up By Directed Call Pickup? n
Can Use Directed Call Pickup? n
Group Controlled Restriction: inactive


Using the settings of yes or no you can assign users to these COR's to allow it.
Reply With Quote
  #3  
Old 05-10-2018, 04:00 AM
hunte99 hunte99 is offline
Member
 
Join Date: Aug 2017
Location: United Kingdom
Posts: 7
hunte99 has 11 reputation points
Default

Quote:
Originally Posted by hurdk View Post
Assign a COR where service observance is set as can be for the users to observe and then a COR where it is set as can be the observer for whoever will be observing.

CLASS OF RESTRICTION

COR Number: 1
COR Description: Example

FRL: 0 APLT? y
Can Be Service Observed? n Calling Party Restriction: none
Can Be A Service Observer? n Called Party Restriction: none
Time of Day Chart: 1 Forced Entry of Account Codes? n
Priority Queuing? n Direct Agent Calling? n
Restriction Override: none Facility Access Trunk Test? n
Restricted Call List? n Can Change Coverage? n

Access to MCT? y Fully Restricted Service? n
Group II Category For MFC: 7 Hear VDN of Origin Annc.? n
Send ANI for MFE? n
MF ANI Prefix: Automatic Charge Display? n
Hear System Music on Hold? y PASTE (Display PBX Data on Phone)? n
Can Be Picked Up By Directed Call Pickup? n
Can Use Directed Call Pickup? n
Group Controlled Restriction: inactive


Using the settings of yes or no you can assign users to these COR's to allow it.
I'd like to add that while this answer is correct in terms of how to set a particular COR to be observed or observable, it doesn't solve the problem that the OP specified - which is restricting either which COR or which extensions should be observable.

I'm afraid that there is no mechanism within any CM version which supports this requirement. Some call recording products and quality monitoring products will allow you to listen live to calls and they tend to have much more robust permission structures. If you have either of those, I'd encourage you to check into those.
__________________
Consultant and Director at Grey Space - Avaya Contact Centre Specialists

https://www.grey-space.com

https://www.linkedin.com/company/teamgreyspace/
Reply With Quote
Reply

Tags
cor, service observe

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 12:13 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.