Help Center/ Customer Engagement Center/ API Reference/ Intelligent Module Interface Reference/ Dialog Interfaces (V2)/ Packet Capture and Recording Interface Invoked in the Dialog (inaction=7)
Updated on 2025-11-13 GMT+08:00
View PDF
Share

Packet Capture and Recording Interface Invoked in the Dialog (inaction=7)

When sending a request to the ODFS for the first time, the access party first requests the ODFS to enable VoiceCyber recording. Whether the ODFS sends an enabling request to VoiceCyber is determined during the flow release. This feature applies only to the intelligent IVR service on the network where the packet capture system (such as VoiceCyber) is connected.

inparams

Parameter

Type

Position

Mandatory

Description

call_id

String

Body

No

Unique call ID, which is the same as the value of userid and is used by the flow.

The value can contain a maximum of 64 characters.

call_sor_id

String

Body

No

Subscriber ID. (In the voice navigation and voice outbound call scenarios, the subscriber number is transferred. In other interaction scenarios, the subscriber ID is transferred.)

The value can contain a maximum of 64 characters.

call_dst_id

String

Body

Yes

Access ID.

1. In the voice navigation scenario, this parameter is set to the flow access code.

2. In the voice outbound call survey scenario, this parameter is set to the flow access code.

3. In other interaction scenarios, this parameter is set to the access ID.

The value can contain a maximum of 20 characters.

real_callee

String

Body

No

Called number for accessing the IVR. This parameter is valid in the voice navigation scenario.

The value can contain a maximum of 32 characters.

cti_callid

String

Body

No (special field in the voice navigation scenario)

Call ID of the CTI to which a call is connected, which is transferred by Huawei IVR. In other scenarios, this parameter is left empty.

The value can contain a maximum of 32 characters.

auth_token

String

Body

Yes

Authorization information, which is the token value returned by the access control system.

Request Example

{
    "userid": "1528780879-9581",
    "inaction": 7,
    "inparams": {
        "call_id": "1528780879-9581",
        "call_sor_id": "13500000001",
        "call_dst_id": "10086", 
        "auth_token":"eyJhbGciOiJSUzI1NiJ9.eyJpYXQiOjE1MzgwMzg5MzUsImV4cCI6MTUzODA0MjUzNSwian"
    }
}

After receiving the request in which the value of inaction is 7, the ODFS determines whether to send a request for starting recording or a packet capture session to the packet capture and recording system (for example, VoiceCyber) based on the flow configuration. Then, the ODFS sends a response to the IVR.

outparams (outaction=7: Successfully Starting and Interconnecting with the Packet Capture System)

Response Example

{
    "ret": "0",
    "userid": "16128422559300717ed3bf958dca2d0cda6c1",
    "outaction": "7",
    "outparams": {}
}
Parent topic: Dialog Interfaces (V2)