//12-02 16:39:00.869323 24174 27394 I CarrierServices: [1172] cpb.x: Send INVITE
//12-02 16:39:00.920251 24174 27394 I CarrierServices: [1172] byy.a: (RCS): : Adding transaction context and starting timer with: 30000 for transaction OUTGOING_f6bbc1f8-c523-4ece-9aa3-18071d554ce6_INVITE_1, method: INVITE
//12-02 16:39:00.993351 24906 24906 I Bugle   : onGetOrCreateConversationSucceeded
//12-02 16:39:01.339010 24174 26674 I CarrierServices: [1012] dxd.a: First response received
//12-02 16:39:01.346428 24174 27394 I CarrierServices: [1172] cpb.c: 200 OK response received
//12-02 16:39:01.361142 24174 27394 I CarrierServices: [1172] cpb.c: Send ACK
//12-02 16:39:01.374160 24906 24906 I Bugle   : DraftMessageTypeConverter: draft switching to RCS.
//12-02 16:39:01.396320 24906 24906 I BugleDataModel: ConversationData{id:9}: refreshRcsCapabilities, unlatchReason: CONVERSATION_PARTICIPANT_LOADER_FINISHED, RcsAvailability: RCS appears to be active, for call sim: 1
//12-02 16:39:01.547456 17386 17397 D BlockedNumbers: isBlocked: in=+17866700559, e164=+17866700559
//12-02 16:39:01.577488 17386 24742 D BlockedNumbers: isBlocked: in=+17862660646, e164=+17862660646
//12-02 16:39:01.592958 24174 27394 I CarrierServices: [1172] dub.a: Secure socket connected to /216.239.36.133:443   ---->>>安全套接字连接http服务器
//12-02 16:39:01.850157 24174 27394 I CarrierServices:  To: msrps://216.239.36.133:443/ADCMgDbvgoZJobdhZ7fcCVzYR-Vm9OiaADimqz0C4OwA1J96064H9uezCGbqzVesABr07FbUYD5EAly3CLImGcvuJm2V6h2DTazow5zlNi0WSgssQQ;tcp
//12-02 16:39:01.850157 24174 27394 I CarrierServices:  From: msrps://[2607:fb90:1c3b:298e:0:1:d1e0:e001]:9/f4339254182a4f34bb00e0607075fb94;tcp
//12-02 16:39:01.865712 24174 27394 I CarrierServices: [1172] duu.a: sendMessage (MSRP session ID:f4339254182a4f34bb00e0607075fb94):
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Message ID: 60a8dbeb71c2e489
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Content array type: null
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Content array length: 0
//12-02 16:39:01.865712 24174 27394 I CarrierServices: To: (redacted)
//12-02 16:39:01.865712 24174 27394 I CarrierServices: From: (redacted)
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Silent: true
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Canceled: false
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Success report required: no
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Failure report required: yes
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Content array value:
//12-02 16:39:01.865712 24174 27394 I CarrierServices: Null
//12-02 16:39:02.260062 24906 24906 I BugleDataModel: ConversationData{id:9}: refreshRcsCapabilities, unlatchReason: CONVERSATION_PARTICIPANT_LOADER_FINISHED, RcsAvailability: RCS appears to be active, for call sim: 1
//12-02 16:39:05.104428 24906 24906 I BugleDataModel: ConversationData{id:9}: send message {Redacted-10 } to 2 recipients
//12-02 16:39:05.116282 24906 24958 I BugleDataModel: InsertNewMessageAction: inserting new message.
//12-02 16:39:05.117352 24906 24906 I Bugle   : DraftMessageTypeConverter: draft switching to RCS.
//12-02 16:39:05.233866 17386 24742 D BlockedNumbers: isBlocked: in=+17866142836, e164=+17866142836
//12-02 16:39:05.280820 24906 24958 I BugleDataModel: InsertNewMessageAction: inserted RCS message{id:23} conversation{id:9}, timeStamp: 1575322745142
//12-02 16:39:05.369435 24906 24958 I BugleDataModel: PendingMessagesProcessor: process from InsertNewMessageAction due to message inserted with queues: rcsMessagesToSend{size:1}
//12-02 16:39:05.445705 24906 27398 I BugleDataModel: Processing changed messages for 23
//12-02 16:39:05.471500 24906 24906 I BugleDataModel: Message 23 processed.
//12-02 16:39:05.471740 24906 24958 I BugleDataModel: PendingMessagesProcessor: started message{id:23} rcsMessage{id:MsWcRdJuTHSqKN83kESI2srg}
//12-02 16:39:05.482670 17386 24742 D BlockedNumbers: isBlocked: in=+17866700559, e164=+17866700559
//12-02 16:39:05.485128 24906 24906 I Bugle   : DraftMessageTypeConverter: draft switching to RCS.
//12-02 16:39:05.545606 17386 18652 D BlockedNumbers: isBlocked: in=+17862660646, e164=+17862660646
//12-02 16:39:05.566730 24906 24906 I BugleDataModel: Message 23 processed.
//12-02 16:39:05.670422 24906 24958 I BugleDataModel: SendMessageAction: Sending RCS message{id:23} in conversation{id:9} rcsMessage{id:MsWcRdJuTHSqKN83kESI2srg}
//12-02 16:39:05.680446 24174 27394 I CarrierServices: [1172] duu.a: sendMessage (MSRP session ID:f4339254182a4f34bb00e0607075fb94):
//12-02 16:39:05.680446 24174 27394 I CarrierServices: Type: text/plain
//12-02 16:39:05.680446 24174 27394 I CarrierServices: RCS message ID: MsWcRdJuTHSqKN83kESI2srg
//12-02 16:39:05.718362 24906 24958 I Bugle   : RcsUtils.getOrCreateP2pThreadId returned thread id 10
//12-02 16:39:05.741436 24906 24958 W Bugle   : PduPersister.persist persisting PDU to given thread: 10
//12-02 16:39:05.884582 17386 18652 D BlockedNumbers: isBlocked: in=+17866142836, e164=+17866142836
//12-02 16:39:05.936636 17386 18652 D BlockedNumbers: isBlocked: in=+17866700559, e164=+17866700559
//12-02 16:39:05.974260 17386 18652 D BlockedNumbers: isBlocked: in=+17862660646, e164=+17862660646
//12-02 16:39:06.306452 24906 24958 I BugleDataModel: SentMessageProcessor: Done sending RCS message{id:23} conversation{id:9}, status: SUCCEEDED

发送RCS成功的消息log_1的更多相关文章

  1. 发送RCS 消息摘录相关成功log

    //11-25 16:48:09.612102  2175  2726 I BugleDataModel: PendingMessagesProcessor: process from InsertN ...

  2. 金蝶k/3 K3云之家消息查询发送是否成功SQL语句

    金蝶k/3 K3云之家消息查询发送是否成功SQL语句 1是成功,0是还在轮询中未发送,4是发送失败 select * into #tempUserID from ( union select t_Gr ...

  3. JavaMail邮件发送不成功的那些坑人情况及分析说明

    [我的Segmentfault原文]https://segmentfault.com/a/1190000008030346 前言   JavaMail的使用本身并不难,网上有不少案例,简单易懂,而且有 ...

  4. 2.技巧: 用 JAXM 发送和接收 SOAP 消息—Java API 使许多手工生成和发送消息方面必需的步骤自动化

    转自:https://www.cnblogs.com/chenying99/archive/2013/05/23/3094128.html 技巧: 用 JAXM 发送和接收 SOAP 消息—Java ...

  5. (七)发送、接收SOAP消息(以HttpClient方式)(2)

    一.为什么要用soap 原本我们使用web服务都是根据wsdl生成客户端(生成一堆java文件)然后再调用,本章节讲解如何用soap消息来替代这种方式. 二.SOAP消息格式 SOAP(简单对象访问协 ...

  6. Java Socket发送与接收HTTP消息简单实现

    在上次Java Socket现实简单的HTTP服务我 们实现了简单的HTTP服务,它可以用来模拟HTTP服务,用它可以截获HTTP请求的原始码流,让我们很清楚的了解到我们向服务发的HTTP消息的结 构 ...

  7. 解决Springboot整合ActiveMQ发送和接收topic消息的问题

    环境搭建 1.创建maven项目(jar) 2.pom.xml添加依赖 <parent> <groupId>org.springframework.boot</group ...

  8. python实现微信发送服务器监控报警消息代码实现

    这篇文章主要介绍了python3.8 微信发送服务器监控报警消息代码实现,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友可以参考下 ! python版本 > ...

  9. 在使用TCP协议进行消息发送时,对消息分帧

    成帧与解析 阅读 <java TCP/IP Socket 编程>第三章笔记 成帧技术(frame)是解决如何在接收端定位消息的首尾位置的问题.在进行数据收发时,必须指定消息接收者如何确定何 ...

随机推荐

  1. Android 自定义 View 详解

    View 的绘制系列文章: Android View 绘制流程之 DecorView 与 ViewRootImpl Android View 的绘制流程之 Measure 过程详解 (一) Andro ...

  2. Java 中的 Servlet&Http&Request

    # 今日内容 : 1. Servlet 2. HTTP 协议 3. Request (就是 Servlet 中 service 方法的 形参. (有这个))     ## Servlet : 1. 概 ...

  3. 记一次Elasticsearch OOM的优化过程——基于segments force merge 和 store type 转为 niofs

    首选,说明笔者的机器环境(不结合环境谈解决方案都是耍流氓): cpu 32核,内存128G,非固态硬盘: RAID0 (4T * 6),单节点,数据量在700G到1800G,索引15亿~21亿.敖丙大 ...

  4. Redux和Context对比

    Redux和Context对比 如果项目体量较小,只是需要一个公共的store存储state,而不讲究使用action来管理state,那context完全可以胜任.反之,则是redux的优点. co ...

  5. Zookeeper Watcher接口

    在ZooKeeper中,接口类Watcher用于表示一个标准的事件处理器,其定义了事件通知相关的逻辑,包含KeeperState和EventType两个枚举类,分别代表了通知状态和事件类型,同时定义了 ...

  6. USB摄像头之130w像素 OV9655配置,ov9650,ov7725,ov7670

    USB摄像头之130w像素 OV9655配置 为了usb2.0采集达到足够的速率,不得不将采用raw格式输出. // 20150411 XVGA 1280*1024 实际上位机需要2560*1024 ...

  7. [状态模式]实现stopwatch

    1.模拟传统面向对象语言的状态模式实现 // Stopwatch类 状态机class Stopwatch {    constructor() {        this.button1 = null ...

  8. 【Gitlab】371- GitLab从安装到全自动化备份一条龙

    原文地址[1]欢迎star 需求 1.在新服务器上安装并搭建好gitlab2.手动+自动将旧服务器上的gitlab备份3.手动+自动将gitlab备份包scp到新服务器上4.手动+自动恢复新服务器上的 ...

  9. Cloudflare Workers 部署跨域代理服务

    项目源码:https://github.com/netnr/workers 发布链接:https://cors.zme.ink 使用文档:https://developers.cloudflare.c ...

  10. kubernetes-单机实验(入门)

    一.安装kubernetes   实验环境: centos7.0(建议使用7.5版本) 实验机器IP:192.168.1.4 安装方式:yum安装 需求环境:Tomcat+Mysql   1:关闭防火 ...