✎ en:custom_development_guide:apis:javascript:agent_group_checkin_checkout [asterCC, hosted call center solution based asterisk]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Agent group (queue) login/logout ======

  *Function:
<code>queueActionCJI(type, usertype, user, orgidentity, list, pwdtype, password, deviceexten, pushevent, callbackFuc)</code>

  *Description:
<code>Agent login to one or several agents group </code>

  *Parameters:

^Params	^Type ^Description ^
|type|String|1(login) / 2(logout)|
|usertype|String|agent / account|
|user|String|Agent No. or Username|
|orgidentity|String|The identity string of the team|
|list|String|Put a string combine with agentgroup id, end with a comma, if you don’t put the list, it will login/logout from all agent group the agent belongs to|
|pwdtype|String|Use plaintext or md5 password for agent or account|
|password|String|password|
|deviceexten|String|Do not need to fill in. After checking in, use this extension at your desk|
|pushevent|String|If need send a agent event,  yes / no(default)|
|callbackFuc|String|callback function|

<code>A valid list format example: agentgroupid1,agentgroupid2,......agentgroupidn,</code>

  *Return Format:
<code>{code:code,message:message}</code>

  *Type of the Return Value:JSON
  *Return Values:

^Value ^Description ^
|<code>{code:1,message:message}</code>|<code>{code:Successful seating group,message:group id: results of enforcement}{code:1, message:1:success,2:NotChecked}</code>|
|<code>{code:2,message:message}</code>|<code>{code:Failed,message:Messages}</code>|
|<code>{code:3,message:message}</code>|<code>{code:Failed,message:group id: results of enforcement}{code:3,message: 1:NotChecked,2:NotFoundGroup}</code>|

Messages:  
  * **success** checkin/check out success
  * **CheckedIn** Already checked in
  * **NotInGroup** Agent doesn't belong to the group
  * **NotFoundGroup** Agent group doesn't exist
  * **NotChecked**  Agent is not checked in