Amazon Connect正在使用什么时间戳进行录制文件名?启动时间戳还是断开时间戳?

发布于 2025-01-22 00:42:40 字数 486 浏览 0 评论 0原文

众所周知,Amazon Connect记录了电话并将录音存储在S3存储桶上,我正在寻找可以用代码在代码中自己制作文件名的时间戳!

有两个时间戳,例如启动时间戳& ContactID_Timestamp_utc Eg 7BB75057-76AE-4EE7E-4E140-440-44AA1C5954B_20220418T06:44_UTC.WAV。

使用 使用SignedUrl获取S3的文件,但在少数情况下,由于S3上的一个sec的增量存储的文件差异为1秒,而且我无法获得文件表格S3。

例如,我的应用程序创建了文件名是:7BB75057-76AE-4E7E-A140-440-44A5954B_20220418T06:44_UTC.WAV。 -4E7E-A140-44A50CC5954B_20220418T06:45_UTC.WAV。

最后一件事可以在联系对象中使用此数据(时间戳)吗?所以我可以使用它。

As we know amazon connect record the calls and store the recordings on S3 bucket, I am looking for what timestamp I can use to make the filename by myself in my code!

There are two timestamps e.g. Initiation timestamp & Disconnect timestamp are being used while creating filenames with contactId_timestamp_UTC e.g. 7bb75057-76ae-4e7e-a140-44a50cc5954b_20220418T06:44_UTC.wav.

I have used the callStartTime to create these filenames and then get the files from S3 using SignedURL but in few cases there is a difference of 1 sec as file stored with incremental of one sec on S3 and I couldn't get the file form S3.

For example I the filename is been created by my application is: 7bb75057-76ae-4e7e-a140-44a50cc5954b_20220418T06:44_UTC.wav. but the recording stored on S3 has filename as: 7bb75057-76ae-4e7e-a140-44a50cc5954b_20220418T06:45_UTC.wav.

The last thing can this data (timestamp) is available in contact object? so I can use it.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

做个ˇ局外人 2025-01-29 00:42:40

看起来文件名的时间戳基于ConnectedToAgentTimestamp,这是有意义的,因为录制直到呼叫者与代理商交谈之前才启动。在联系方式中,ConnectedToAgentTimestamp在AgentInfo下。

{
    "Contact": {
        "Arn": "arn:aws:connect:us-west-2:xxxxxxxxxx:instance/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/contact/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
        "Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
        "InitiationMethod": "INBOUND",
        "Channel": "VOICE",
        "QueueInfo": {
            "Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "EnqueueTimestamp": "2022-04-13T15:05:45.334000+12:00"
        },
        "AgentInfo": {
            "Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "ConnectedToAgentTimestamp": "2022-04-13T15:06:25.706000+12:00"
        },
        "InitiationTimestamp": "2022-04-13T15:05:15.869000+12:00",
        "DisconnectTimestamp": "2022-04-13T15:08:08.298000+12:00",
        "LastUpdateTimestamp": "2022-04-13T15:08:08.299000+12:00"
    }
}

Looks like the timestamp for the file name is based on ConnectedToAgentTimestamp which makes sense as the recording doesn't start until the caller is talking to an agent. ConnectedToAgentTimestamp is under AgentInfo in the contact details...

{
    "Contact": {
        "Arn": "arn:aws:connect:us-west-2:xxxxxxxxxx:instance/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/contact/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
        "Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
        "InitiationMethod": "INBOUND",
        "Channel": "VOICE",
        "QueueInfo": {
            "Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "EnqueueTimestamp": "2022-04-13T15:05:45.334000+12:00"
        },
        "AgentInfo": {
            "Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
            "ConnectedToAgentTimestamp": "2022-04-13T15:06:25.706000+12:00"
        },
        "InitiationTimestamp": "2022-04-13T15:05:15.869000+12:00",
        "DisconnectTimestamp": "2022-04-13T15:08:08.298000+12:00",
        "LastUpdateTimestamp": "2022-04-13T15:08:08.299000+12:00"
    }
}
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文