- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
所以我在我的一些自定义 VOIP 应用程序中使用 JAIN-SIP API 进行调用设置,我遇到了一个困扰我好几天的问题:我无法挂断带有 BYE 消息的调用。更准确地说,我不断收到来自被叫方的 481 Call/Transaction Does Not Exist 响应代码。我不明白为什么。
下面是被调用方堆栈的服务器日志。如果需要,我可以为您提供源代码和调试日志,但请注意源代码很长。
<!-- Use the Trace Viewer in src/tools/tracesviewer to view this trace
Here are the stack configuration properties
javax.sip.IP_ADDRESS= 192.168.1.103
javax.sip.STACK_NAME= vm.nist
javax.sip.ROUTER_PATH= null
javax.sip.OUTBOUND_PROXY= null
-->
<message
from="192.168.1.103:51060"
to="5.9.109.239:5060"
time="1355272841980"
isSender="true"
transactionId="z9hg4bk-cf90a986-d7f9-44a9-bd63-efb74ecc36e9"
callId="f8270729014d0c5b17c759f60ea6510f@192.168.1.103"
firstLine="REGISTER sip:test14.d@talk-place.com SIP/2.0"
>
<![CDATA[REGISTER sip:test14.d@talk-place.com SIP/2.0
Call-ID: f8270729014d0c5b17c759f60ea6510f@192.168.1.103
CSeq: 366 REGISTER
From: "Test14d" <sip:test14.d@talk-place.com>;tag=18faf7d44db09f903ff5895b78787911
To: "Test14d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 212.200.115.198:51060;rport;branch=z9hG4bK-cf90a986-d7f9-44a9-bd63-efb74ecc36e9
Max-Forwards: 70
Contact: <sip:test14.d@212.200.115.198:51060;transport=udp>
Allow: INVITE,ACK,BYE,MESSAGE
User-Agent: Talk-Place
Content-Length: 0
]]>
</message>
<message
from="5.9.109.239:5060"
to="192.168.1.103:51060"
time="1355272842063"
isSender="false"
transactionId="z9hg4bk-cf90a986-d7f9-44a9-bd63-efb74ecc36e9"
callId="f8270729014d0c5b17c759f60ea6510f@192.168.1.103"
firstLine="SIP/2.0 401 Unauthorized"
>
<![CDATA[SIP/2.0 401 Unauthorized
Call-ID: f8270729014d0c5b17c759f60ea6510f@192.168.1.103
CSeq: 366 REGISTER
From: "Test14d" <sip:test14.d@talk-place.com>;tag=18faf7d44db09f903ff5895b78787911
To: "Test14d" <sip:test14.d@talk-place.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.6828
Via: SIP/2.0/UDP 192.168.1.103:51060;rport=51060;branch=z9hG4bK-cf90a986-d7f9-44a9-bd63-efb74ecc36e9
WWW-Authenticate: Digest nonce="UMfTtVDH0okwmWYROC4r29415DGDKaqM",realm="talk-place.com"
Server: kamailio (3.3.2 (x86_64/linux))
Content-Length: 0
]]>
</message>
<message
from="192.168.1.103:51060"
to="5.9.109.239:5060"
time="1355272842069"
isSender="true"
transactionId="z9hg4bk-cf90a986-d7f9-44a9-bd63-efb74ecc36e9"
callId="f8270729014d0c5b17c759f60ea6510f@192.168.1.103"
firstLine="REGISTER sip:test14.d@talk-place.com SIP/2.0"
>
<![CDATA[REGISTER sip:test14.d@talk-place.com SIP/2.0
Call-ID: f8270729014d0c5b17c759f60ea6510f@192.168.1.103
CSeq: 367 REGISTER
From: "Test14d" <sip:test14.d@talk-place.com>;tag=18faf7d44db09f903ff5895b78787911
To: "Test14d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 212.200.115.198:51060;rport;branch=z9hG4bK-cf90a986-d7f9-44a9-bd63-efb74ecc36e9
Max-Forwards: 70
Contact: <sip:test14.d@212.200.115.198:51060;transport=udp>
Allow: INVITE,ACK,BYE,MESSAGE
User-Agent: Talk-Place
Authorization: Digest response="ec655ebc2eb8685de4fb7d739f3f0acf",username="test14.d",nonce="UMfTtVDH0okwmWYROC4r29415DGDKaqM",realm="talk-place.com",uri="sip:test14.d@talk-place.com",algorithm=MD5
Content-Length: 0
]]>
</message>
<message
from="5.9.109.239:5060"
to="192.168.1.103:51060"
time="1355272842118"
isSender="false"
transactionId="z9hg4bk-cf90a986-d7f9-44a9-bd63-efb74ecc36e9"
callId="f8270729014d0c5b17c759f60ea6510f@192.168.1.103"
firstLine="SIP/2.0 200 OK"
>
<![CDATA[SIP/2.0 200 OK
Call-ID: f8270729014d0c5b17c759f60ea6510f@192.168.1.103
CSeq: 367 REGISTER
From: "Test14d" <sip:test14.d@talk-place.com>;tag=18faf7d44db09f903ff5895b78787911
To: "Test14d" <sip:test14.d@talk-place.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.6828
Via: SIP/2.0/UDP 192.168.1.103:51060;rport=51060;branch=z9hG4bK-cf90a986-d7f9-44a9-bd63-efb74ecc36e9
Contact: <sip:test14.d@192.168.1.103:51060;transport=udp>;expires=3600
Server: kamailio (3.3.2 (x86_64/linux))
Content-Length: 0
]]>
</message>
<message
from="5.9.109.239:5060"
to="192.168.1.103:51060"
time="1355272852008"
isSender="false"
transactionId="z9hg4bkbd3c.62eea493.0"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="INVITE sip:test14.d@192.168.1.103:51060;transport=udp SIP/2.0"
>
<![CDATA[INVITE sip:test14.d@192.168.1.103:51060;transport=udp SIP/2.0
Record-Route: <sip:5.9.109.239;lr=on>
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 116 INVITE
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bKbd3c.62eea493.0,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Max-Forwards: 69
Contact: <sip:test14.f@77.243.22.4:36238;transport=udp>
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
User-Agent: Talk-Place
Content-Type: application/sdp
Content-Length: 206
]]>
</message>
<message
from="192.168.1.103:51060"
to="5.9.109.239:5060"
time="1355272852027"
isSender="true"
transactionId="z9hg4bkbd3c.62eea493.0"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="SIP/2.0 100 Trying"
>
<![CDATA[SIP/2.0 100 Trying
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 116 INVITE
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bKbd3c.62eea493.0,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Content-Length: 0
]]>
</message>
<message
from="192.168.1.103:51060"
to="5.9.109.239:5060"
time="1355272854032"
isSender="true"
transactionId="z9hg4bkbd3c.62eea493.0"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="SIP/2.0 180 Ringing"
>
<![CDATA[SIP/2.0 180 Ringing
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 116 INVITE
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>;tag=18faf7d44db09f903ff5895b78787911
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bKbd3c.62eea493.0,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Contact: <sip:test14.d@212.200.115.198;transport=udp>
Content-Length: 0
]]>
</message>
<message
from="192.168.1.103:51060"
to="5.9.109.239:5060"
time="1355272856037"
isSender="true"
transactionId="z9hg4bkbd3c.62eea493.0"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="SIP/2.0 200 OK"
>
<![CDATA[SIP/2.0 200 OK
Record-Route: <sip:5.9.109.239;lr=on>
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 116 INVITE
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>;tag=18faf7d44db09f903ff5895b78787911
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bKbd3c.62eea493.0,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Contact: <sip:test14.d@212.200.115.198;transport=udp>
Content-Type: application/sdp
Content-Length: 218
]]>
</message>
<message
from="5.9.109.239:5060"
to="192.168.1.103:51060"
time="1355272856327"
isSender="false"
transactionId="z9hg4bkcydzigwkx"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="ACK sip:test14.d@192.168.1.103:51060;transport=udp SIP/2.0"
>
<![CDATA[ACK sip:test14.d@192.168.1.103:51060;transport=udp SIP/2.0
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 117 ACK
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bKcydzigwkX,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Max-Forwards: 69
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
User-Agent: Talk-Place
Content-Length: 0
]]>
</message>
<message
from="192.168.1.103:51060"
to="5.9.109.239:5060"
time="1355272856339"
isSender="true"
transactionId="z9hg4bkcydzigwkx"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="SIP/2.0 200 OK"
>
<![CDATA[SIP/2.0 200 OK
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 117 ACK
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bKcydzigwkX,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Content-Length: 0
]]>
</message>
<message
from="5.9.109.239:5060"
to="192.168.1.103:51060"
time="1355272856728"
isSender="false"
transactionId="z9hg4bk9e3c.74261c85.0"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="BYE sip:test14.d@192.168.1.103:51060;transport=udp SIP/2.0"
>
<![CDATA[BYE sip:test14.d@192.168.1.103:51060;transport=udp SIP/2.0
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 119 BYE
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bK9e3c.74261c85.0,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Max-Forwards: 69
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
User-Agent: Talk-Place
Content-Length: 0
]]>
</message>
<message
from="192.168.1.103:51060"
to="5.9.109.239:5060"
time="1355272856738"
isSender="true"
transactionId="z9hg4bk9e3c.74261c85.0"
callId="2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204"
firstLine="SIP/2.0 481 Call leg/Transaction does not exist"
>
<![CDATA[SIP/2.0 481 Call leg/Transaction does not exist
Call-ID: 2b10b9f3880ef078cb20cd9ae7075591@10.86.183.204
CSeq: 119 BYE
From: "test14.f" <sip:test14.f@talk-place.com>;tag=32f8bc24842d02d1357bd2345c542659
To: "test14.d" <sip:test14.d@talk-place.com>
Via: SIP/2.0/UDP 5.9.109.239;branch=z9hG4bK9e3c.74261c85.0,SIP/2.0/UDP 77.243.22.4:36238;rport=36238;branch=z9hG4bK-f7a17df9-2242-4785-80cd-25993986008b
Server: vm.nist
Content-Length: 0
]]>
</message>
最佳答案
UAS 拒绝BYE
请求,因为它在To
header 中不包含tag
。 ACK
请求也应该有 标签
。您如何创建这些请求?
关于java - JAIN SIP 481 对 BYE 消息的响应,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/13831078/
我一直在读到,如果一个集合“被释放”,它也会释放它的所有对象。另一方面,我还读到,一旦集合被释放,集合就会释放它的对象。 但最后一件事可能并不总是发生,正如苹果所说。系统决定是否取消分配。在大多数情况
我有一个客户端-服务器应用程序,它使用 WCF 进行通信,并使用 NetDataContractSerializer 序列化对象图。 由于服务器和客户端之间传输了大量数据,因此我尝试通过微调数据成员的
我需要有关 JMS 队列和消息处理的帮助。 我有一个场景,需要针对特定属性组同步处理消息,但可以在不同属性组之间同时处理消息。 我了解了特定于每个属性的消息组和队列的一些知识。我的想法是,我想针对
我最近开始使用 C++,并且有一种强烈的冲动 #define print(msg) std::cout void print(T const& msg) { std::cout void
我已经为使用 JGroups 编写了简单的测试。有两个像这样的简单应用程序 import org.jgroups.*; import org.jgroups.conf.ConfiguratorFact
这个问题在这里已经有了答案: Firebase messaging is not supported in your browser how to solve this? (3 个回答) 7 个月前关
在我的 C# 控制台应用程序中,我正在尝试更新 CRM 2016 中的帐户。IsFaulted 不断返回 true。当我向下钻取时它返回的错误消息如下: EntityState must be set
我正在尝试通过 tcp 将以下 json 写入 graylog 服务器: {"facility":"GELF","file":"","full_message":"Test Message Tcp",
我正在使用 Django 的消息框架来指示成功的操作和失败的操作。 如何排除帐户登录和注销消息?目前,登录后登陆页面显示 已成功登录为“用户名”。我不希望显示此消息,但应显示所有其他成功消息。我的尝试
我通过编写禁用qDebug()消息 CONFIG(release, debug|release):DEFINES += QT_NO_DEBUG_OUTPUT 在.pro文件中。这很好。我想知道是否可以
我正在使用 ThrottleRequest 来限制登录尝试。 在 Kendler.php 我有 'throttle' => \Illuminate\Routing\Middleware\Throttl
我有一个脚本,它通过die引发异常。捕获异常时,我想输出不附加位置信息的消息。 该脚本: #! /usr/bin/perl -w use strict; eval { die "My erro
允许的消息类型有哪些(字符串、字节、整数等)? 消息的最大大小是多少? 队列和交换器的最大数量是多少? 最佳答案 理论上任何东西都可以作为消息存储/发送。实际上您不想在队列上存储任何内容。如果队列大部
基本上,我正在尝试创建一个简单的 GUI 来与 Robocopy 一起使用。我正在使用进程打开 Robocopy 并将输出重定向到文本框,如下所示: With MyProcess.StartI
我想将进入 MQ 队列的消息记录到数据库/文件或其他日志队列,并且我无法修改现有代码。是否有任何方法可以实现某种类似于 HTTP 嗅探器的消息记录实用程序?或者也许 MQ 有一些内置的功能来记录消息?
我得到了一个带有 single_selection 数据表和一个命令按钮的页面。命令按钮调用一个 bean 方法来验证是否进行了选择。如果不是,它应该显示一条消息警告用户。如果进行了选择,它将导航到另
我知道 MSVC 可以通过 pragma 消息做到这一点 -> http://support.microsoft.com/kb/155196 gcc 是否有办法打印用户创建的警告或消息? (我找不到谷
当存在大量节点或二进制数据时, native Erlang 消息能否提供合理的性能? 情况 1:有一个大约 50-200 台机器的动态池(erlang 节点)。它在不断变化,每 10 分钟大约添加或删
我想知道如何在用户登录后显示“欢迎用户,您已登录”的问候消息,并且该消息应在 5 秒内消失。 该消息将在用户成功登录后显示一次,但在同一 session 期间连续访问主页时不会再次显示。因为我在 ho
如果我仅使用Welcome消息,我的代码可以正常工作,但是当打印p->client_name指针时,消息不居中。 所以我的问题是如何将消息和客户端名称居中,就像它是一条消息一样。为什么它目前仅将消
我是一名优秀的程序员,十分优秀!