Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:custom_development_guide:apis:http:hangup [2017/12/12 11:05]
127.0.0.1 external edit
en:custom_development_guide:apis:http:hangup [2018/12/29 17:03] (current)
donnie
Line 2: Line 2:
  
   *Reques String:   *Reques String:
-<​code>​EVENT=HANGUP&​uniqueid=uniqueid&​pwdtype=pwdtype&​password=password&​usertype=usertype&​user=user&​orgidentity=orgidentity</​code>​+<​code>​EVENT=HANGUP&​uniqueid=uniqueid&​targetagent=targetagent&​target=target&​pwdtype=pwdtype&​password=password&​usertype=usertype&​user=user&​orgidentity=orgidentity</​code>​
  
   *Description:​   *Description:​
Line 12: Line 12:
 |EVENT|String|HANGUP| |EVENT|String|HANGUP|
 |uniqueid|String|the uniqueid of the calls you want to hangup, end with a comma| |uniqueid|String|the uniqueid of the calls you want to hangup, end with a comma|
-|targetagent|String|目标坐席工号,要操作哪个坐席的通话。uniqueid为空时,此项必填。uniqueid不为空时,此项可为空。如果挂断监听,强插,密语中的坐席组长(target=groupadmin),此处需要填写被监听,强插,密语的坐席工号。如2227组长监听1986,欲挂断2227,此处需要填写1986。+|targetagent|String|If you don't have uniqueId, you need to put agent number. If you want to hangup group admin who is in spy, barge-in or whisper, put agent number, such as, group admin 2227 is spying agent 1986, put 1986 here if you need to hangup ​2227.
-|target|String|挂机对象(channel,​agent,​caller,​consult,​all),​channel必须传uniqueid,挂断相应uniqueid的通话,​agent挂断目标坐席通话,​caller挂断客户,​consult如果传了uniqueid 则只挂uniqueid 相应的咨询方,如果没传,就按从旧到新的顺序挂断所有咨询方的通话,​all挂断目标坐席相关所有通话,如果被监听,强插,同时挂断组长通话,​groupadmin当目标坐席被监听,强插,密语时,用于挂断组长的通话,即结束组长的监听,强插,密语状态。|+|target|String|hangup target:(channel,​agent,​caller,​consult,​all),​uniqueId is required if you want to hangup a channel|
 |pwdtype|String|Use plaintext or md5 password for agent or account| |pwdtype|String|Use plaintext or md5 password for agent or account|
 |password|String|password| |password|String|password|
Line 22: Line 22:
   *uniqueid example:   *uniqueid example:
     *Hangup one party: uniqueid,     *Hangup one party: uniqueid,
-    *Hnagup: ​        ​uniqueid1, uniqueid2,​…uniqueidN,​+    *Hnagup:​uniqueid1,​ uniqueid2,​…uniqueidN,​
  
   *Return Format:   *Return Format:
Line 31: Line 31:
  
 ^Value ^Description ^ ^Value ^Description ^
-|<​code>​|Return|1|Return|message</​code>​|<​code>​|Retuen|成功|Retuen|信息描述 +|<​code>​|Return|1|Return|message</​code>​|<​code>​|Retuen|succeed|Retuen|message: 
-uniqueid不为空时,message为每个uniqueid执行挂断的结果,举例+When uniqueid ​is not empty, ​message ​gives result for each uniqueid, ex:
 |Retuen|1|Retuen|4781:​success,​4782:​failed |Retuen|1|Retuen|4781:​success,​4782:​failed
-success代表挂断成功 
-failed代表挂断失败 
 </​code>​| </​code>​|
 |<​code>​|Return|2|Return|message</​code>​|<​code>​Failed||Messages</​code>​| |<​code>​|Return|2|Return|message</​code>​|<​code>​Failed||Messages</​code>​|
en/custom_development_guide/apis/http/hangup.txt · Last modified: 2018/12/29 17:03 by donnie
Recent changes RSS feed Debian Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki