Releasing a Co-browsing Connection
Function
This interface is invoked by a third party to release a co-browsing connection.
Interface Prototype
|
Method |
POST |
|
|---|---|---|
|
URL |
https://{IP address}:{Port number}/service-cloud/rest/webadapter/v1/connectionInfo/releaseConnection |
{IP address}:{Port number} indicates the IP address and port number of the NSLB exposed externally. |
|
Parameter |
Mandatory or Not |
Type |
Default Value |
Description |
|---|---|---|---|---|
|
Content-Type |
Yes |
String |
None |
The value is fixed at application/json; charset=UTF-8. |
|
Cookie |
Yes |
String |
None |
During page integration, the CC-Messaging writes the value of ccmessaging-token to browser cookies through the request response. When invoking this interface independently, ensure that the cookie in the request header contains ccmessaging-token=xxx, where xxx indicates the value of ccmessaging-token. |
Request Parameters
|
Parameter |
Mandatory or Not |
Type |
Description |
|---|---|---|---|
|
callId |
Yes |
String |
Call ID. |
Response Parameters
|
Parameter |
Mandatory or Not |
Type |
Description |
|---|---|---|---|
|
retCode |
Yes |
String |
Interface response code. The value 0 indicates success. |
|
retMsg |
No |
String |
Interface description. |
Example
- Request
POST /service-cloud/rest/webadapter/v1/connectionInfo/releaseConnection host: 10.10.10.2:18446 connection: Keep-Alive x-forwarded-for: 10.10.10.3, 10.10.10.4 x-real-ip: 10.10.10.5 content-length: 401 remote-host: 10.10.10.6 user-agent: java/socket content-type: application/json; charset=utf-8 cookie: JSESSION*****#*#*****3 ccmessaging-token: ******** accept: */* { "callId":"xx" } - Response
{ "retCode":"0" }
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot