//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. java基础-泛型举例详解

    泛型 泛型是JDK5.0增加的新特性,泛型的本质是参数化类型,即所操作的数据类型被指定为一个参数.这种类型参数可以在类.接口.和方法的创建中,分别被称为泛型类.泛型接口.泛型方法. 一.认识泛型 在没 ...

  2. swift实现单例的四种方式

    单例模式 单例模式是设计模式中最简单的一种,甚至有些模式大师都不称其为模式,称其为一种实现技巧,因为设计模式讲究对象之间的关系的抽象,而单例模式只有自己一个对象. 当你只需要一个实例的时候需要使用单例 ...

  3. 数据挖掘算法（三）--logistic回归

    数据挖掘算法学习笔记汇总 数据挖掘算法(一)–K近邻算法 (KNN) 数据挖掘算法(二)–决策树 数据挖掘算法(三)–logistic回归 在介绍logistic回归之前先复习几个基础知识点,有助于后 ...

  4. HDU5343 MZL's Circle Zhou(SAM+记忆化搜索)

    Problem Description MZL's Circle Zhou is good at solving some counting problems. One day, he comes u ...

  5. git 设置和取消指定域名代理 - git config proxy

    Firstly - Check Check if U have global .gitconfig file 检查是否有全局 .gitconfig 文件 Usually global .gitconf ...

  6. 【CSS】305- [译] Web 使用 CSS Shapes 的艺术设计

    %; %; %; %; 0, 0 100%, 100% 100%); %; %; % 0, 0 100%, 100% 100%); %; %; ) p:nth-of-type(1)::before { ...

  7. 还不懂MySQL索引？这1次彻底搞懂B+树和B-树

    前言 看了很多关于索引的博客,讲的大同小异.但是始终没有让我明白关于索引的一些概念,如B-Tree索引,Hash索引,唯一索引….或许有很多人和我一样,没搞清楚概念就开始研究B-Tree,B+Tree ...

  8. JSP请求是如何被处理的？jsp的执行原理

    客户端通过浏览器发送jsp请求,服务器端接受到请求后,判断是否是第一次请求该页面,或者该页面是否改变,若是,服务器将jsp页面翻译为servlet,jvm将servlet编译为.class文件,字节码 ...

  9. linux,centos,php,word转图片方法

    刚开始的时候是客户的活儿,真的是没有想到,被这样一个方法给卡住了,真是醉了,经过漫长的一周,终于搞定了这个问题,以下就来给大家介绍以下这个方法把.能方便大家. (直接转换没办法,所以找了个折中的办法, ...

  10. Office安装时报错1907的解决方法

    大家在装office时可能遇到过1907错误,字体无法注册 的问题,百度后者是采用什么四种方法,我四种方法都试过了没有用,也有人说缺什么日本字体,我也试过了没有用,做为有强迫证的我都重做系统,重下载o ...