Updated on 2023-09-27 GMT+08:00

Modifying a File Server

Scenario

This interface is invoked to modify a file server. It can be used before importing an outbound call data file from the server.

Usage Description

  • Prerequisites
    • The corresponding AK/SK authentication permission is available.
    • You have applied for a developer account.
    • A file server is available.
  • Precautions
    • After a request is received, the server needs to return a 200 response. Other responses indicate that the writeback fails.
    • If the IP address needs to be changed, the password must be transferred.
    • The username can contain a maximum of 30 characters and cannot contain the following special characters: `~!@#$ %^&*()+=|{}'":;<>/?.\[]!
    • The password must be a string of 8 to 80 characters.

Method

This interface supports only the POST method.

URI

https://ip:port/rest/isales/v1/openapi/campaigns/{vdnId}/file/{serverId}/updateServer

In the URL, ip indicates the IP address of the CC-iSales server, and port indicates the HTTPS port number of the CC-iSales server.

Table 1 Parameters in the URL

No.

Parameter

Type

Mandatory or Not

Description

1

vdnId

Integer

Yes

VDN ID.

The value is an integer ranging from 1 to 9999.

2

serverId

String

Yes

File server ID.

Request Description

Table 2 Request header parameters

No.

Parameter

Type

Mandatory or Not

Description

1

Content-Type

String

Yes

The value is fixed to application/json; charset=UTF-8.

2

Authorization

String

Yes

For details about the generation mode, see C2 Monitoring, System Outbound Call, CDR, and Knowledge Base Interface Authentication.

Table 3 Request body parameters

No.

Parameter

Type

Mandatory or Not

Description

1

serverInfo

Object

Yes

File server information.

2

userName

String

Yes

Username.

3

serverPwd

String

No

Service password, which is transferred in plaintext and stored in ciphertext on the backend. This parameter is mandatory when the value of serviceInfo.IP is different from the original IP address.

serverInfo

No.

Parameter

Type

Mandatory or Not

Description

1

ip

String

Yes

File server IP address.

2

port

String

Yes

Port number.

3

filePath

String

Yes

Default file server path, for example, /home/sftp.

Response Description

Table 4 Response body parameters

No.

Parameter

Type

Description

1

resultCode

String

Error code. The value 0200000 indicates success, and other values indicate failure.

For details, see Table 5.

2

resultDesc

String

Description.

3

returnCode

String

Error code. The value 0200000 indicates success, and other values indicate failure.

For details, see Table 5.

4

returnDesc

String

Description.

Triggered Event

None

Error Codes

Table 5 Error code description

No.

Error Code

Description

1

0200001

Parameter error. For details about the error, see resultDesc.

2

0200006

The server configuration does not exist.

2

0200033

The outbound call data does not exist.

3

0200034

The substatus does not match the business result.

4

02000001

Empty parameter.

5

02000002

The parameter contains invalid characters.

6

02000003

The parameter length cannot exceed the maximum length.

7

02000004

The parameter length cannot be less than the minimum length.

8

02000005

The parameter length must be within the specified range.

9

02000006

Incorrect parameter type.

10

02000007

Incorrect parameter value.

11

02000008

Parameter conversion error. Check the request parameters.

12

02000009

Incorrect parameter combination. Check the request parameters.

13

02000010

The hour and minute parameters must be set at the same time.

14

02000011

The number of parameters cannot exceed the specified number.

Example

  • The following provides an example of the request body of this interface:
    {
        "userName":"WANGWU",
        "serverInfo":{
            "ip":"5.9.11.11",
            "port":"22",
            "filePath":"/home/sftp"
        },
    	  "serverPwd":"******"
    }
  • The following provides an example of the response body of this interface:
    {
    	"returnCode": "0200000",
    	"resultCode": "0200000",
    	"resultDesc": "success",
    	"returnDesc": "success"
    }