Step 2 - Bind queue extension to user account

The configuration of the attendant console must be updated to have the queue extension registered by the device when the attendant logs onto the console.

The procedure below applies when configuring unmanaged devices using the embedded administration module. Similar options are available when working with managed devices under the supervision of the TSS service.

1) Connect to the attendant console administration from your preferred Internet navigator and log onto the device with administration privileges ;

2) From the main menu, navigate to the Account management / Users screen and select the user account created for the attendant – i.e. John Smith ;

5) Press Add new button to open the Line Edition form ; fill in the form as per the table below and commit the changes

Field	Value	Comment
Type	Secondary
Line subscription state	Subscribed	Opens / closes the queue
Priority	None
Call events dispatching	Off
Queue Type	Queue	Declares the line as queue
Queue Auto Hold Delay	Custom	This option instructs the system to put on hold in-bound calls without any manual actions of the attendant. This is mandatory for having call appearances queued by the attendant console and displayed on the queue slots.
Incoming Auto accept delay	Off	This option instructs the system to accept in-bound calls without any manual actions of the attendant.
Hold Auto forward delay	Custom	This option defines the retention period of calls in the queue. For example, if a call is still present in the queue after 60 seconds, the console forwards it automatically to the forwarding target.
Hold Auto forward target	(Target extension)
SIP DisplayName SIP Extension SIP Password SIP Digest SIP Domain	(SIP credentials associated to the queue extension)	These values must be obtained from the voice & IT administrator or can be fetched out of the CUCM configuration using the Configuration Fetch tool in User Edition form. SIP DisplayName is used to identify on which queue a call is hosted.