在SIP INVITE方法中，连续获得200个响应_Sip

在SIP INVITE方法中，连续获得200个响应

sip

在SIP INVITE方法中，连续获得200个响应,sip,Sip,在INVITE请求中，被叫方正在向我发送200（OK）响应，我正在发送ACK，但现在我不知道被叫方是否没有收到确认，因为我仍在不断收到200响应，下面是请求和响应以下是整个SIP对话框： INVITE sip:3000@192.168.1.101 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bKe446822249352251a5bd13b6e66ef303;rport Max-Forwards: 70 From: Sahitya

在INVITE请求中，被叫方正在向我发送200（OK）响应，我正在发送ACK，但现在我不知道被叫方是否没有收到确认，因为我仍在不断收到200响应，下面是请求和响应

以下是整个SIP对话框：

INVITE sip:3000@192.168.1.101 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bKe446822249352251a5bd13b6e66ef303;rport
Max-Forwards: 70
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 1 INVITE
Contact: <sip:3001@192.168.1.9:5070>
Allow: INVITE,ACK,BYE,CANCEL
User-Agent: MySIP V2.0
Content-Type: application/sdp
Content-Length: 179
<------------->


<--- Reliably Transmitting (no NAT) to 192.168.1.9:5070 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP  192.168.1.9:5070;branch=z9hG4bKe446822249352251a5bd13b6e66ef303;received=192.168.1.9;rport=5070
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 1 INVITE
Server: Asterisk PBX 11.7.0~dfsg-1ubuntu1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="50310a1a"
Content-Length: 0



 <--- SIP read from UDP:192.168.1.9:5070 --->
ACK sip:3000@192.168.1.101 SIP/2.0
Via: SIP/2.0/UDP   192.168.1.9:5070;branch=z9hG4bKe446822249352251a5bd13b6e66ef303;rport
Max-Forwards: 70
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 1 ACK
User-Agent: MySIP V2.0
Content-Length: 0

<------------->


<--- SIP read from UDP:192.168.1.9:5070 --->
INVITE sip:3000@192.168.1.101 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bK4fc5c00de7440b65f8b5355cfacb82d2;rport
Max-Forwards: 70
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 2 INVITE
Contact: <sip:3001@192.168.1.9:5070>
Allow: INVITE,ACK,BYE,CANCEL
User-Agent: MySIP V2.0
Content-Type: application/sdp
Content-Length: 179
Authorization: Digest username="3001", realm="asterisk", nonce="50310a1a",  opaque="", uri="sip:3001@192.168.1.101:5060", response="b1e38ea10061a0224e2189e9177fff1c", algorithm=MD5
<------------->


<--- Transmitting (no NAT) to 192.168.1.9:5070 --->
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bK4fc5c00de7440b65f8b5355cfacb82d2;received=192.168.1.9;rport=5070
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 2 INVITE
Server: Asterisk PBX 11.7.0~dfsg-1ubuntu1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:3000@192.168.1.101:5060>
Content-Length: 0
<------------>


<--- Transmitting (no NAT) to 192.168.1.9:5070 --->
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bK4fc5c00de7440b65f8b5355cfacb82d2;received=192.168.1.9;rport=5070
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 2 INVITE
Server: Asterisk PBX 11.7.0~dfsg-1ubuntu1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:3000@192.168.1.101:5060>
Content-Length: 0
<------------>

<--- Reliably Transmitting (no NAT) to 192.168.1.9:5070 --->
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bK4fc5c00de7440b65f8b5355cfacb82d2;received=192.168.1.9;rport=5070
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 2 INVITE
Server: Asterisk PBX 11.7.0~dfsg-1ubuntu1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:3000@192.168.1.101:5060>
Content-Type: application/sdp
Content-Length: 195
<------------>


<--- SIP read from UDP:192.168.1.9:5070 --->
ACK sip:3000@192.168.1.101:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bKd8c26ff688480593ce616e913ac8e609;rport
Max-Forwards: 70
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 2 ACK
Authorization: Digest username="3001", realm="asterisk", nonce="50310a1a", opaque="", uri="sip:3001@192.168.1.101:5060", response="b1e38ea10061a0224e2189e9177fff1c", algorithm=MD5
User-Agent: MySIP V2.0
Content-Length: 0
<------------->


Retransmitting #1 (no NAT) to 192.168.1.9:5070:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.9:5070;branch=z9hG4bK4fc5c00de7440b65f8b5355cfacb82d2;received=192.168.1.9;rport=5070
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 2 INVITE
Server: Asterisk PBX 11.7.0~dfsg-1ubuntu1
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Contact: <sip:3000@192.168.1.101:5060>
Content-Type: application/sdp
Content-Length: 195
---

<--- SIP read from UDP:192.168.1.9:5070 --->
ACK sip:3000@192.168.1.101:5060 SIP/2.0
Via: SIP/2.0/UDP   192.168.1.9:5070;branch=z9hG4bK542e162569381a2bd29c111fa3ea6e03;rport
Max-Forwards: 70
From: Sahitya<sip:3001@internalmail.com>;tag=m1RbnnhW7m
To: Prithvi<sip:3000@192.168.1.101>;tag=as69cbf848
Call-ID: b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq: 2 ACK
Authorization: Digest username="3001", realm="asterisk", nonce="50310a1a", opaque="", uri="sip:3001@192.168.1.101:5060", response="b1e38ea10061a0224e2189e9177fff1c", algorithm=MD5
User-Agent: MySIP V2.0
Content-Length: 0

INVITE sip:3000@192.168.1.101SIP/2.0
Via:SIP/2.0/UDP 192.168.1.9:5070；分支机构=Z9HG4BKE44682249352251A5BD13B6E66EF303；港口
最大前锋：70
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:1邀请
联系人：
允许：邀请、确认、再见、取消
用户代理：MySIP V2.0
内容类型：应用程序/sdp
内容长度：179
SIP/2.0 401未经授权
Via:SIP/2.0/UDP 192.168.1.9:5070；分支机构=Z9HG4BKE44682249352251A5BD13B6E66EF303；接收=192.168.1.9；rport=5070
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:1邀请
服务器：星号PBX 11.7.0~dfsg-1ubuntu1
允许：邀请、确认、取消、选项、再见、参考、订阅、通知、信息、发布
支持：替换、定时器
WWW-Authenticate:Digest algorithm=MD5，realm=“asterisk”，nonce=“50310a1a”
内容长度：0
确认sip：3000@192.168.1.101SIP/2.0
Via:SIP/2.0/UDP 192.168.1.9:5070；分支机构=Z9HG4BKE44682249352251A5BD13B6E66EF303；港口
最大前锋：70
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:1确认
用户代理：MySIP V2.0
内容长度：0
邀请sip：3000@192.168.1.101SIP/2.0
Via:SIP/2.0/UDP 192.168.1.9:5070；分支=Z9HG4BK4FC5C000DE7440B65F8B535CFACB82D2；港口
最大前锋：70
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:2邀请
联系人：
允许：邀请、确认、再见、取消
用户代理：MySIP V2.0
内容类型：应用程序/sdp
内容长度：179
授权：Digest username=“3001”，realm=“asterisk”，nonce=“50310a1a”，不透明=“uri=”sip:3001@192.168.1.101：5060“，response=“b1e38ea10061a0224e2189e9177fff1c”，算法=MD5
SIP/2.0 100
Via:SIP/2.0/UDP 192.168.1.9:5070；分支=Z9HG4BK4FC5C000DE7440B65F8B535CFACB82D2；接收=192.168.1.9；rport=5070
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:2邀请
服务器：星号PBX 11.7.0~dfsg-1ubuntu1
允许：邀请、确认、取消、选项、再见、参考、订阅、通知、信息、发布
支持：替换、定时器
联系人：
内容长度：0
SIP/2.0 180振铃
Via:SIP/2.0/UDP 192.168.1.9:5070；分支=Z9HG4BK4FC5C000DE7440B65F8B535CFACB82D2；接收=192.168.1.9；rport=5070
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:2邀请
服务器：星号PBX 11.7.0~dfsg-1ubuntu1
允许：邀请、确认、取消、选项、再见、参考、订阅、通知、信息、发布
支持：替换、定时器
联系人：
内容长度：0
SIP/2.0 200正常
Via:SIP/2.0/UDP 192.168.1.9:5070；分支=Z9HG4BK4FC5C000DE7440B65F8B535CFACB82D2；接收=192.168.1.9；rport=5070
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:2邀请
服务器：星号PBX 11.7.0~dfsg-1ubuntu1
允许：邀请、确认、取消、选项、再见、参考、订阅、通知、信息、发布
支持：替换、定时器
联系人：
内容类型：应用程序/sdp
内容长度：195
确认sip：3000@192.168.1.101：5060 SIP/2.0
Via:SIP/2.0/UDP 192.168.1.9:5070；分支=z9hG4bKd8c26ff688480593ce616e913ac8e609；港口
最大前锋：70
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:2确认
授权：Digest username=“3001”，realm=“asterisk”，nonce=“50310a1a”，不透明=“uri=”sip:3001@192.168.1.101：5060“，response=“b1e38ea10061a0224e2189e9177fff1c”，算法=MD5
用户代理：MySIP V2.0
内容长度：0
将#1（无NAT）重新传输到192.168.1.9:5070：
SIP/2.0 200正常
Via:SIP/2.0/UDP 192.168.1.9:5070；分支=Z9HG4BK4FC5C000DE7440B65F8B535CFACB82D2；接收=192.168.1.9；rport=5070
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:2邀请
服务器：星号PBX 11.7.0~dfsg-1ubuntu1
允许：邀请、确认、取消、选项、再见、参考、订阅、通知、信息、发布
支持：替换、定时器
联系人：
内容类型：应用程序/sdp
内容长度：195
---
确认sip：3000@192.168.1.101：5060 SIP/2.0
Via:SIP/2.0/UDP 192.168.1.9:5070；分支=z9hG4bK542e162569381a2bd29c111fa3ea6e03；港口
最大前锋：70
发件人：Sahitya；标签=m1RbnnhW7m
致：Prithvi；标签=as69cbf848
呼叫ID:b6c72c48-402d-40d3-aabf-0538eb1bb630@internalmail.com
CSeq:2确认
授权：Digest username=“3001”，realm=“asterisk”，nonce=“50310a1a”，不透明=“uri=”sip:3001@192.168.1.101：5060“，response=“b1e38ea10061a0224e2189e9177fff1c”，算法=MD5
用户代理：MySIP V2.0
内容长度：0

我怀疑问题是因为在您的第二次邀请请求中，您正在使用与原始邀请相同的呼叫ID，从标记和到标记。对于第二个INVITE请求，它们都应该是不同的值，因为这是一个新事务。

在第二个INVITE中：

From标记应该不同
Via分支应该是不同的
应该缺少To标记

也在200 OK的确认中：

From、To、Via和Call ID应与200 OK中的相同

否则，在被调用方端也存在明显的bug（例如接受带有to标记的邀请）。

在哪里捕获它，为什么我可以通过标题查看？