Avaya Support Forums  

Go Back   Avaya Support Forums > Contact Center Applications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 02-28-2012, 02:04 PM
sfitzg sfitzg is offline
Guru
 
Join Date: Jul 2010
Location: Auckland, New Zealand
Posts: 190
sfitzg has 10 reputation points
Default AACC 6.2 Hotdesking on Avaya CM

I am trying to configure hotdesking. Based on administration documentation I should be assigning terminals to workstations and addresses to terminals in the CCT Administration tools.

My problem is that my only option when creating a terminal is 'Knowledge worker" where I understand I should be selecting "Agent". I am guessing the default service provider is not correct but all documentation I can find on the service provider related to CS1K not CM.

Can someone give me a hint as to what I need to do to get the foundation in place for hot desking on an AACC/CM environment.


Thanks

Simon

Last edited by sfitzg; 02-28-2012 at 04:12 PM.
Reply With Quote
  #2  
Old 02-29-2012, 02:51 AM
phemming phemming is offline
Guru
 
Join Date: Jun 2010
Location: Birmingham,UK
Posts: 150
phemming has 10 reputation points
Default

Simon,

The service provider IP is the CCMS server IP address (as for CS1K)
For AACC SIP sites the only configuration in CCT admin is the Provider ID, all the rest is taken care of by configuring (and associating the agent) in Contact Centre Management

For SIP AACC you don't configure hotdesking, as the agent can only be associated with 1 SIP URI (e.g. sip:1234@mydsipdomain.com). The hotdesking aspect is taken care of by the agent logging into phone next to whichever workstation they log in to AAAD from.

Agent is really a term for CS1K POS ID (Key 0) in the terminal context.

Paul
Reply With Quote
  #3  
Old 02-29-2012, 11:22 AM
sfitzg sfitzg is offline
Guru
 
Join Date: Jul 2010
Location: Auckland, New Zealand
Posts: 190
sfitzg has 10 reputation points
Default

Thanks,

That clarifies it. Reading the documentation I thought there may have been smoke and mirrors that modified the SIP URI in a hot desking environment. This simplifies it.

Simon
Reply With Quote
  #4  
Old 08-10-2012, 03:41 PM
aapawan123 aapawan123 is offline
Hot Shot
 
Join Date: Jan 2011
Posts: 18
aapawan123 has 10 reputation points
Default

Hi Simon,

Looking at hotdisking in AACC SIP enviornment. Based on the response, AACC SIP enviornment will not work on hotdisking?
Reply With Quote
  #5  
Old 08-13-2012, 04:33 AM
stphnwd's Avatar
stphnwd stphnwd is offline
Brainiac
.
 
Join Date: Jan 2011
Location: USA
Posts: 52
stphnwd has 10 reputation points
Default

@aapawan123 - Hot desking does not need to be "enabled" in AACC SIP. As it does in AACC AML.

As phemming stated:
"For SIP AACC you don't configure hotdesking, as the agent can only be associated with 1 SIP URI (e.g. sip:1234@mydsipdomain.com). The hotdesking aspect is taken care of by the agent logging into phone next to whichever workstation they log in to AAAD from."
Reply With Quote
Reply

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 07:14 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.