SIP服务器接收不到客户端发出的INVITE协议

2011-03-16 02:40:29 2.8k 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

五 SIP中一个INVITE消息的发起过程 SIP协议的INVITE消息发起流程当通过sip协议发起一个会话时，需要通过invite消息实现该流程。而SIP协议是一个基于事务的协议，每一个sip会话的都是通过sip部件间的一系列消息来完成的。首先需要明确的重要概念就是事务。事务在SIP协议中，一个事务是指完成一次消息交互的整个流程。以INVITE消息为例，一个基于代理服务器交换信令和语音视频数据包的事务模型如下图所示：如阅读详情

如题：在INVITE请求中，添加ICE相关字段后，SIP服务器接收不到客户端发出的INVITE协议，客户端与SIP服务器之间有路由器。感觉可能是路由器过滤掉了，但是没查出个所以然了。请大家帮忙啊
具体的协议如下：

INVITE sip:10317@210.77.82.83 SIP/2.0
Via: SIP/2.0/TCP 192.168.2.69:4915;rport;branch=z9hG4bKPjd905329d9bb04772bf7706f655f6e373
Max-Forwards: 70
From: sip:10303@210.77.82.83;tag=1f01c53103c44a77aa1c8969e15dcb19
To: sip:10317@210.77.82.83
Contact: <sip:10303@192.168.2.69:5060;ob>;+sip.ice
Call-ID: 993c2762c4ef4e34847bde5bf32fb5b4
CSeq: 21482 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v1.8.10/win32
Content-Type: application/sdp
Content-Length: 830

v=0
o=- 3509264699 3509264699 IN IP4 210.77.82.83
s=pjmedia
c=IN IP4 210.77.82.83
t=0 0
a=X-nat:0
m=audio 49152 RTP/AVP 98 97 99 104 3 0 8 9 96
a=rtcp:49153 IN IP4 210.77.82.83
a=rtpmap:98 speex/16000
a=rtpmap:97 speex/8000
a=rtpmap:99 speex/32000
a=rtpmap:104 iLBC/8000
a=fmtp:104 mode=30
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=sendrecv
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=ice-ufrag:65212740
a=ice-pwd:324153d4
a=candidate:Hc0a80245 1 UDP 2130706431 192.168.2.69 4882 typ host
a=candidate:Rd24d5253 1 UDP 16777215 210.77.82.83 49152 typ relay raddr 221.178.201.155 rport 13510
a=candidate:Hc0a80245 2 UDP 2130706430 192.168.2.69 4885 typ host
a=candidate:Rd24d5253 2 UDP 16777214 210.77.82.83 49153 typ relay raddr 221.178.201.155 rport 13959
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.2.69:4915;branch=z9hG4bKPjd905329d9bb04772bf7706f655f6e373;rport=13211
Call-ID: 993c2762c4ef4e34847bde5bf32fb5b4
From: <sip:10303@210.77.82.83:5060>;tag=1f01c53103c44a77aa1c8969e15dcb19
To: <sip:10317@210.77.82.83>
CSeq: 21482 INVITE
User-Agent: FreeSWITCH-mod_sofia/1.0.5-20100223-0400-16729M
Content-Length: 0

SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/TCP 192.168.2.69:4915;branch=z9hG4bKPjd905329d9bb04772bf7706f655f6e373;rport=13211
Call-ID: 993c2762c4ef4e34847bde5bf32fb5b4
From: <sip:10303@210.77.82.83:5060>;tag=1f01c53103c44a77aa1c8969e15dcb19
To: <sip:10317@210.77.82.83>;tag=2emB9178mX08H
CSeq: 21482 INVITE
User-Agent: FreeSWITCH-mod_sofia/1.0.5-20100223-0400-16729M
Accept: application/sdp
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,UPDATE,INFO,REGISTER,REFER,NOTIFY,PUBLISH,SUBSCRIBE
Supported: timer,precondition,path,replaces
Allow-Events: talk,presence,dialog,line-seize,call-info,sla,include-session-description,presence.winfo,message-summary,refer
Proxy-Authenticate: Digest realm="221.178.201.155",nonce="0de2f951-435e-415e-bb48-f324153d3b6b",algorithm=MD5,
qop="auth"
Content-Length: 0

ACK sip:10317@210.77.82.83 SIP/2.0
Via: SIP/2.0/TCP 192.168.2.69:4915;rport;branch=z9hG4bKPjd905329d9bb04772bf7706f655f6e373
Max-Forwards: 70
From: sip:10303@210.77.82.83;tag=1f01c53103c44a77aa1c8969e15dcb19
To: sip:10317@210.77.82.83;tag=2emB9178mX08H
Call-ID: 993c2762c4ef4e34847bde5bf32fb5b4
CSeq: 21482 ACK
Content-Length: 0

INVITE sip:10317@210.77.82.83 SIP/2.0
Via: SIP/2.0/TCP 192.168.2.69:4915;rport;branch=z9hG4bKPj0e6ac76c15c742929d00a4086d5d2946
Max-Forwards: 70
From: sip:10303@210.77.82.83;tag=1f01c53103c44a77aa1c8969e15dcb19
To: sip:10317@210.77.82.83
Contact: <sip:10303@192.168.2.69:5060;ob>;+sip.ice
Call-ID: 993c2762c4ef4e34847bde5bf32fb5b4
CSeq: 21483 INVITE
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Supported: replaces, 100rel, timer, norefersub
Session-Expires: 1800
Min-SE: 90
User-Agent: PJSUA v1.8.10/win32
Proxy-Authorization: Digest username="10303", realm="221.178.201.155", nonce="0de2f951-435e-415e-bb48-f324153d3b6b", uri="sip:10317@210.77.82.83", response="f12021d15679d39770168fd8fd34fce6", algorithm=MD5, cnonce="0ec58004c7b846e9abec61217565297f", qop=auth, nc=00000001
Content-Type: application/sdp
Content-Length: 830

v=0
o=- 3509264699 3509264699 IN IP4 210.77.82.83
s=pjmedia
c=IN IP4 210.77.82.83
t=0 0
a=X-nat:0
m=audio 49152 RTP/AVP 98 97 99 104 3 0 8 9 96
a=rtcp:49153 IN IP4 210.77.82.83
a=rtpmap:98 speex/16000
a=rtpmap:97 speex/8000
a=rtpmap:99 speex/32000
a=rtpmap:104 iLBC/8000
a=fmtp:104 mode=30
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=sendrecv
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15
a=ice-ufrag:65212740
a=ice-pwd:324153d4
a=candidate:Hc0a80245 1 UDP 2130706431 192.168.2.69 4882 typ host
a=candidate:Rd24d5253 1 UDP 16777215 210.77.82.83 49152 typ relay raddr 221.178.201.155 rport 13510
a=candidate:Hc0a80245 2 UDP 2130706430 192.168.2.69 4885 typ host
a=candidate:Rd24d5253 2 UDP 16777214 210.77.82.83 49153 typ relay raddr 221.178.201.155 rport 13959

如上协议显示，开始INVITE请求，SIP服务器是有响应的，但是等到具有添加认证信息的INVITE后，通过抓好包工具查看，SIP服务器并没有收到最后一个，带有认证信息的INVITE请求。

注：以上情况，在局域网内未再现，在局域网是正常的

...全文