This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
en:custom_development_guide:apis:javascript:call [2016/09/07 03:08] liuxl created |
en:custom_development_guide:apis:javascript:call [2018/12/27 06:39] (current) donnie |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| *Function: | *Function: | ||
| - | <code>makeCallCJI(targetdn, targettype, agentgroupid, usertype, user, orgidentity, pwdtype, password, modeltype, model_id, userdata, callbackFuc)</code> | + | <code>makeCallCJI(targetdn, targettype, agentgroupid, usertype, user, orgidentity, pwdtype, password, modeltype, model_id, userdata, callbackFuc, agentexten, callerid, callername, trunkidentity, cidtype)</code> |
| *Description: | *Description: | ||
| Line 22: | Line 22: | ||
| |userdata|String|user data, only valid when modeltype= Campaign, say you put “customer_id=109&pwd=asdfg” here, when you receive the call events, you will get userdata=’customer_id=109&pwd=asdfg’| | |userdata|String|user data, only valid when modeltype= Campaign, say you put “customer_id=109&pwd=asdfg” here, when you receive the call events, you will get userdata=’customer_id=109&pwd=asdfg’| | ||
| |callbackFuc|String|callback function| | |callbackFuc|String|callback function| | ||
| + | |agentexten|String|optional, if you put this, system will bind the exten to agent before dial| | ||
| + | |callerid|String|optional, callerId number| | ||
| + | |callername|String|optional, callerId name| | ||
| + | |trunkidentity|String|optional, server will use this trunk to dial if you put trunk identity string| | ||
| + | |cidtype|String|optional, 0 means use callerId above, 1 means use trunk callerId, 2 means use device callerId| | ||
| *Return Format: | *Return Format: | ||
| - | <code>{code:code,message:message} | + | <code>{code:code,message:message}</code> |
| - | Return Type:JSON</code> | + | |
| + | *Return Type:JSON | ||
| *Return Values: | *Return Values: | ||