`
linyu19872008
  • 浏览: 282470 次
  • 性别: Icon_minigender_1
  • 来自: 北京
社区版块
存档分类
最新评论

sip学习--邀请流程

 
阅读更多

1000(192.168.1.119)              1001(192.168.1.112)
|                                                     |
|    INVITE                                     |
|    ------------------------------>           |
|    100 Trying                                |
|    <------------------------------           |
|    180 Ringing                              |
|     <------------------------------           |
|    200 OK                                     |
|    <-------------------------------          |
|    ACK                                          |
|    ------------------------------->          |
|                                                     |
|    <---RTP--------------------->         |
|    <---RTP--------------------->         |
|    <---RTP--------------------->         |
|    ...                                              |
|                                                     |
|    BYE                                          |
|    <-------------------------------          |
|    200 OK                                     |
|    -------------------------------->         |
|                                                     |

 


/////////1000-->INVITE-->Server

U 192.168.1.119:34308 -> 192.168.1.88:5060
INVITE sip:1001@192.168.1.88 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport;branch=z9hG4bK1735896405.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>.
Call-ID: 768170422.
CSeq: 20 INVITE.
Contact: <sip:1000@192.168.1.119:34308>.
Content-Type: application/sdp.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO.
Max-Forwards: 70.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Subject: Phone call.
Content-Length:   503.
.
v=0.
o=1000 2317 3462 IN IP4 114.255.88.22.
s=Talk.
c=IN IP4 114.255.88.22.
b=AS:380.
t=0 0.
m=audio 44473 RTP/AVP 120 111 110 0 8 104 100 3 101.
a=rtpmap:120 SILK/16000.
a=rtpmap:111 speex/16000.
a=fmtp:111 vbr=on.
a=rtpmap:110 speex/8000.
a=fmtp:110 vbr=on.
a=rtpmap:104 AMR/8000.
a=fmtp:104 octet-align=1.
a=rtpmap:100 iLBC/8000.
a=fmtp:100 mode=30.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.
a=rtcp:7079 IN IP4 192.168.1.119.
m=video 16420 RTP/AVP 103.
a=rtpmap:103 VP8/90000.
a=rtcp:9079.

/////////Server-->407 Proxy Authentication Required-->1000
#
U 192.168.1.88:5060 -> 192.168.1.119:34308
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1735896405.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2eec.
Call-ID: 768170422.
CSeq: 20 INVITE.
Proxy-Authenticate: Digest realm="192.168.1.88", nonce="Uc1zLFHNcgDco99Y6IeY77vT8cUEd3V3".
Server: kamailio (4.0.2 (x86_64/linux)).
Content-Length: 0.
.

/////////1000-->ACK-->Server
#
U 192.168.1.119:34308 -> 192.168.1.88:5060
ACK sip:1001@192.168.1.88 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport;branch=z9hG4bK1735896405.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=b27e1a1d33761e85846fc98f5f3a7e58.2eec.
Call-ID: 768170422.
CSeq: 20 ACK.
Content-Length: 0.
.

/////////1000-->INVITE-->Server
#
U 192.168.1.119:34308 -> 192.168.1.88:5060
INVITE sip:1001@192.168.1.88 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport;branch=z9hG4bK1699620867.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1000@192.168.1.119:34308>.
Proxy-Authorization: Digest username="1000", realm="192.168.1.88", nonce="Uc1zLFHNcgDco99Y6IeY77vT8cUEd3V3", uri="sip:1001@192.168.1.88", response="5f3854ac9b61ab7ec8c01c1bb4dd4082", algorithm=MD5.
Content-Type: application/sdp.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO.
Max-Forwards: 70.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Subject: Phone call.
Content-Length:   503.
.
v=0.
o=1000 2317 3462 IN IP4 114.255.88.22.
s=Talk.
c=IN IP4 114.255.88.22.
b=AS:380.
t=0 0.
m=audio 44473 RTP/AVP 120 111 110 0 8 104 100 3 101.
a=rtpmap:120 SILK/16000.
a=rtpmap:111 speex/16000.
a=fmtp:111 vbr=on.
a=rtpmap:110 speex/8000.
a=fmtp:110 vbr=on.
a=rtpmap:104 AMR/8000.
a=fmtp:104 octet-align=1.
a=rtpmap:100 iLBC/8000.
a=fmtp:100 mode=30.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.
a=rtcp:7079 IN IP4 192.168.1.119.
m=video 16420 RTP/AVP 103.
a=rtpmap:103 VP8/90000.
a=rtcp:9079.

/////////Server-->100 Trying-->1000
#
U 192.168.1.88:5060 -> 192.168.1.119:34308
SIP/2.0 100 trying -- your call is important to us.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>.
Call-ID: 768170422.
CSeq: 21 INVITE.
Server: kamailio (4.0.2 (x86_64/linux)).
Content-Length: 0.
.

/////////Server-->INVITE-->1001
#
U 192.168.1.88:5060 -> 192.168.1.112:5060
INVITE sip:1001@192.168.1.112;line=a99bbc8e3e5e611 SIP/2.0.
Record-Route: <sip:192.168.1.88;lr=on>.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1000@192.168.1.119:34308>.
Content-Type: application/sdp.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO.
Max-Forwards: 16.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Subject: Phone call.
Content-Length:   503.
.
v=0.
o=1000 2317 3462 IN IP4 114.255.88.22.
s=Talk.
c=IN IP4 114.255.88.22.
b=AS:380.
t=0 0.
m=audio 44473 RTP/AVP 120 111 110 0 8 104 100 3 101.
a=rtpmap:120 SILK/16000.
a=rtpmap:111 speex/16000.
a=fmtp:111 vbr=on.
a=rtpmap:110 speex/8000.
a=fmtp:110 vbr=on.
a=rtpmap:104 AMR/8000.
a=fmtp:104 octet-align=1.
a=rtpmap:100 iLBC/8000.
a=fmtp:100 mode=30.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.
a=rtcp:7079 IN IP4 192.168.1.119.
m=video 16420 RTP/AVP 103.
a=rtpmap:103 VP8/90000.
a=rtcp:9079.

/////////Server-->INVITE-->1001
#
U 192.168.1.88:5060 -> 192.168.1.112:5060
INVITE sip:1001@192.168.1.112;line=6aea0c5f6333c41 SIP/2.0.
Record-Route: <sip:192.168.1.88;lr=on>.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.1.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1000@192.168.1.119:34308>.
Content-Type: application/sdp.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO.
Max-Forwards: 16.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Subject: Phone call.
Content-Length:   503.
.
v=0.
o=1000 2317 3462 IN IP4 114.255.88.22.
s=Talk.
c=IN IP4 114.255.88.22.
b=AS:380.
t=0 0.
m=audio 44473 RTP/AVP 120 111 110 0 8 104 100 3 101.
a=rtpmap:120 SILK/16000.
a=rtpmap:111 speex/16000.
a=fmtp:111 vbr=on.
a=rtpmap:110 speex/8000.
a=fmtp:110 vbr=on.
a=rtpmap:104 AMR/8000.
a=fmtp:104 octet-align=1.
a=rtpmap:100 iLBC/8000.
a=fmtp:100 mode=30.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.
a=rtcp:7079 IN IP4 192.168.1.119.
m=video 16420 RTP/AVP 103.
a=rtpmap:103 VP8/90000.
a=rtcp:9079.

/////////1001-->100 Trying-->Server
#
U 192.168.1.112:5060 -> 192.168.1.88:5060
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>.
Call-ID: 768170422.
CSeq: 21 INVITE.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////1001-->101 Dialog Establishement-->Server
#
U 192.168.1.112:5060 -> 192.168.1.88:5060
SIP/2.0 101 Dialog Establishement.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
Record-Route: <sip:192.168.1.88;lr=on>.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1001@192.168.1.112:5060>.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////1001-->404 Not Found-->Server
#
U 192.168.1.112:5060 -> 192.168.1.88:5060
SIP/2.0 404 Not Found.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.1.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=18467.
Call-ID: 768170422.
CSeq: 21 INVITE.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////Server-->ACK-->1001
#
U 192.168.1.88:5060 -> 192.168.1.112:5060
ACK sip:1001@192.168.1.112;line=6aea0c5f6333c41 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.1.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=18467.
Call-ID: 768170422.
CSeq: 21 ACK.
Max-Forwards: 16.
Content-Length: 0.
.

/////////Server-->101 Dialog Establishement-->1000
#
U 192.168.1.88:5060 -> 192.168.1.119:34308
SIP/2.0 101 Dialog Establishement.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
Record-Route: <sip:192.168.1.88;lr=on>.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1001@192.168.1.112:5060>.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////1001-->OPTIONS-->Server
#
U 192.168.1.112:5060 -> 192.168.1.88:5060
OPTIONS sip:1000@192.168.1.88 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.112:5060;rport;branch=z9hG4bK14574.
From: <sip:1001@192.168.1.88>;tag=6308.
To: <sip:1000@192.168.1.88>.
Call-ID: 9633.
CSeq: 20 OPTIONS.
Accept: application/sdp.
Max-Forwards: 70.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////Server-->407 Proxy Authentication Required-->1001
#
U 192.168.1.88:5060 -> 192.168.1.112:5060
SIP/2.0 407 Proxy Authentication Required.
Via: SIP/2.0/UDP 192.168.1.112:5060;rport=5060;branch=z9hG4bK14574.
From: <sip:1001@192.168.1.88>;tag=6308.
To: <sip:1000@192.168.1.88>;tag=b27e1a1d33761e85846fc98f5f3a7e58.7679.
Call-ID: 9633.
CSeq: 20 OPTIONS.
Proxy-Authenticate: Digest realm="192.168.1.88", nonce="Uc1zLVHNcgHi878xjXYDM8ev5Fm+HVH4".
Server: kamailio (4.0.2 (x86_64/linux)).
Content-Length: 0.
.

/////////1001-->407 180 Ringing-->Server
#
U 192.168.1.112:5060 -> 192.168.1.88:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
Record-Route: <sip:192.168.1.88;lr=on>.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1001@192.168.1.112:5060>.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////Server-->407 180 Ringing-->1000
#
U 192.168.1.88:5060 -> 192.168.1.119:34308
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
Record-Route: <sip:192.168.1.88;lr=on>.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1001@192.168.1.112:5060>.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////1001-->200 OK-->Server
#
U 192.168.1.112:5060 -> 192.168.1.88:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK489f.b6c1ec97.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
Record-Route: <sip:192.168.1.88;lr=on>.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1001@192.168.1.112>.
Content-Type: application/sdp.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length:   207.
.
v=0.
o=1001 1188 861 IN IP4 192.168.1.112.
s=Talk.
c=IN IP4 192.168.1.112.
t=0 0.
m=audio 0 RTP/AVP 101.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.
m=video 9078 RTP/AVP 103.
a=rtpmap:103 VP8/90000.


/////////Server-->200 OK-->1000
#
U 192.168.1.88:5060 -> 192.168.1.119:34308
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1699620867.
Record-Route: <sip:192.168.1.88;lr=on>.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 INVITE.
Contact: <sip:1001@192.168.1.112>.
Content-Type: application/sdp.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length:   207.
.
v=0.
o=1001 1188 861 IN IP4 192.168.1.112.
s=Talk.
c=IN IP4 192.168.1.112.
t=0 0.
m=audio 0 RTP/AVP 101.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.
m=video 9078 RTP/AVP 103.
a=rtpmap:103 VP8/90000.

/////////1000-->ACK-->Server
#
U 192.168.1.119:34308 -> 192.168.1.88:5060
ACK sip:1001@192.168.1.112 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport;branch=z9hG4bK1059414352.
Route: <sip:192.168.1.88;lr=on>.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 ACK.
Contact: <sip:1000@192.168.1.119:34308>.
Proxy-Authorization: Digest username="1000", realm="192.168.1.88", nonce="Uc1zLFHNcgDco99Y6IeY77vT8cUEd3V3", uri="sip:1001@192.168.1.88", response="5f3854ac9b61ab7ec8c01c1bb4dd4082", algorithm=MD5.
Max-Forwards: 70.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////Server-->ACK-->1001
#
U 192.168.1.88:5060 -> 192.168.1.112:5060
ACK sip:1001@192.168.1.112 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bKcydzigwkX.
Via: SIP/2.0/UDP 192.168.1.119:34308;rport=34308;branch=z9hG4bK1059414352.
From: <sip:1000@192.168.1.88>;tag=963256715.
To: <sip:1001@192.168.1.88>;tag=41.
Call-ID: 768170422.
CSeq: 21 ACK.
Contact: <sip:1000@192.168.1.119:34308>.
Proxy-Authorization: Digest username="1000", realm="192.168.1.88", nonce="Uc1zLFHNcgDco99Y6IeY77vT8cUEd3V3", uri="sip:1001@192.168.1.88", response="5f3854ac9b61ab7ec8c01c1bb4dd4082", algorithm=MD5.
Max-Forwards: 16.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Content-Length: 0.
.

 

////////////////////////////////////////////////挂断
/////////1001-->BYE-->Server
#
U 192.168.1.112:5060 -> 192.168.1.88:5060
BYE sip:1000@192.168.1.119:34308 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.112:5060;rport;branch=z9hG4bK24657.
Route: <sip:192.168.1.88;lr=on>.
From: <sip:1001@192.168.1.88>;tag=41.
To: <sip:1000@192.168.1.88>;tag=963256715.
Call-ID: 768170422.
CSeq: 2 BYE.
Contact: <sip:1001@192.168.1.112:5060>.
Max-Forwards: 70.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////Server-->BYE-->1000
#
U 192.168.1.88:5060 -> 192.168.1.119:34308
BYE sip:1000@192.168.1.119:34308 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK935c.67a7a982.0.
Via: SIP/2.0/UDP 192.168.1.112:5060;rport=5060;branch=z9hG4bK24657.
From: <sip:1001@192.168.1.88>;tag=41.
To: <sip:1000@192.168.1.88>;tag=963256715.
Call-ID: 768170422.
CSeq: 2 BYE.
Contact: <sip:1001@192.168.1.112:5060>.
Max-Forwards: 16.
User-Agent: Linphone/3.6.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////1000-->200 OK-->Server
#
U 192.168.1.119:34308 -> 192.168.1.88:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.1.88;branch=z9hG4bK935c.67a7a982.0.
Via: SIP/2.0/UDP 192.168.1.112:5060;rport=5060;branch=z9hG4bK24657.
From: <sip:1001@192.168.1.88>;tag=41.
To: <sip:1000@192.168.1.88>;tag=963256715.
Call-ID: 768170422.
CSeq: 2 BYE.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Content-Length: 0.
.

/////////Server-->BYE-->1001
#
U 192.168.1.88:5060 -> 192.168.1.112:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.1.112:5060;rport=5060;branch=z9hG4bK24657.
From: <sip:1001@192.168.1.88>;tag=41.
To: <sip:1000@192.168.1.88>;tag=963256715.
Call-ID: 768170422.
CSeq: 2 BYE.
User-Agent: LinphoneAndroid/2.2.1 (eXosip2/3.6.0).
Content-Length: 0.
.

分享到:
评论

相关推荐

    sip-3261中文

    这一版本是SIP协议的核心规范,定义了SIP协议的基本语法、消息格式及交互流程。 ### E文不好的人可以先看这个,然后再看E文 这段描述表明此文档是为了帮助那些英文阅读有困难的人士更好地理解SIP协议。文档首先...

    java-sip-api-master.zip_DEMO_SIP java_TEL ltd 86 sip_gettingpqx_

    "gettingpqx"可能是指获取或处理SIP协议中的某个特定流程或组件的代码示例。通过这个项目,我们可以深入学习SIP在Java环境下的应用,了解如何构建和管理通信会话。 SIP是一种基于文本的应用层控制协议,主要用于...

    SIP协议学习总结(SIP-Understanding Session Initation Protocol)

    ### SIP会话流程 1. 用户A(E. Schroedinger)向用户B(Heisenberg)发起呼叫,发送INVITE请求,通过DNS解析B的URI找到代理服务器proxy.munich.de。 2. 代理服务器收到请求,查找B的实际IP地址,并添加自己的Via头,...

    SIp学习实例

    在提供的"送给sip学习者(sip实例).doc"文档中,可能会包含详细的步骤解释、代码示例或实际通话流程图,帮助学习者更好地理解SIP协议的运作方式。这些实例可能涵盖了从初始化呼叫、接收邀请、发送响应到处理各种情况...

    sip协议基本流程和信令流程·学习sip的好帮手sipprotocol

    总结来说,SIP协议是实现VoIP和其他多媒体通信的核心协议,其基本流程包括注册、邀请、响应、确认和会话管理等步骤。理解并掌握SIP协议的工作原理对于开发、维护和优化通信系统至关重要。同时,了解中国国家标准对于...

    Android应用源码之Android-Sip2Peer-1.0 实现p2p.zip

    开发者需要了解SIP的基本工作流程,包括注册、邀请、响应和会话管理,以及如何在Android上实现SIP服务。 二、P2P网络架构 P2P网络中,每个节点既是客户端也是服务器,可以发起或接收通信请求。Android-Sip2Peer-1.0...

    Android高级应用源码-Android-Sip2Peer-1.0 实现p2p.rar

    源码中包含了SIP的注册、邀请、响应等关键流程,有助于我们理解SIP的工作原理及其在Android上的实现。 2. **P2P网络架构** P2P网络中的每个节点既是客户端也是服务器,这种去中心化的结构使得网络更具弹性。在...

    RFC3621sip-china.rar_RFC 3621_RFC3621_sip

    **SIP协议流程** 1. 用户通过UAC发送INVITE请求,邀请另一方加入会话。 2. 请求经过一系列代理服务器,最终到达被叫方的UAS。 3. UAS收到请求后,可能返回200 OK响应,表示接受邀请。 4. 双方通过ACK消息确认会话已...

    Android高级应用源码-Android-Sip2Peer-1.0 实现p2p.zip

    理解SIP的基本概念、语法和流程是掌握该源码的关键,包括注册、邀请、响应、取消等操作。 2. **P2P网络架构** P2P网络中,每个节点既是服务提供者也是消费者,减少了中心服务器的压力。Android-Sip2Peer 实现了这...

    SIP学习帮手SIP中文资料汇编

    **SIP学习帮手SIP中文资料汇编** SIP(Session Initiation Protocol)是一种用于控制多媒体通信会话(如语音和视频通话)的应用层协议。这个“SIP学习帮手SIP中文资料汇编”提供了丰富的中文资源,旨在帮助初学者更...

    sip协议pdf、华为sip和学习sip协议的java代码

    通常,这样的文档会包含SIP协议的基本概念、消息结构、流程图、交互过程以及相关的RFC(Request for Comments)文档引用。通过阅读这份PDF,你可以理解SIP协议的工作原理,包括如何发起呼叫、如何建立和终止会话、...

    sip协议教程,学习SIP协议不错的教程

    - **工作流程**:UAC发送呼叫建立消息给Proxy Server,Proxy Server根据已知信息转发给UAS或查询其他服务器获取位置信息。 - **后续处理**:在会话建立后,Proxy Server可以选择继续监控会话变化或退出会话路径。 ...

    c++实现的sip协议栈invite流程源码

    2. **SipStack** 将邀请消息封装为SIP报文,并通过**SocketClient** 发送给目标地址。 3. **SocketServer** 接收到报文后,将其传递给**SipUas** 进行解析。 4. **SipUas** 解析Invite请求,根据策略生成响应。如果...

    sip协议标准

    SIP协议的工作流程通常包括以下步骤: 1. 注册:用户代理向注册服务器发送注册请求,更新其在线状态和联系信息。 2. 呼叫发起:UAC向UAS发送INVITE请求,邀请对方参与会话。 3. 呼叫处理:UAS收到请求后,根据自身...

    sip.rar_phpsip_sip 实例_sip 解析

    **SIP(Session Initiation Protocol)详解** SIP(会话初始协议)是一种应用层控制协议,用于...对于深入学习和掌握SIP,阅读《sip协议分析.pdf》这样的资料将是十分有益的,它将提供更详细的理论知识和实践案例。

    SIP模拟测试工具sipp-3.3

    在使用`sipp-3.3`进行测试时,首先要理解SIP的基本概念和流程,然后根据实际需求编写或修改XML测试脚本。在执行测试时,需关注服务器的响应,分析测试结果,以优化SIP服务的性能和稳定性。对于新手,可以从官方文档...

    SIP 协议详解 协议 SIP SDP

    SIP(Session Initiation Protocol)协议详解:一种用于多媒体通信的信令协议 SIP,全称为Session Initiation Protocol,是互联网工程任务组...通过学习和掌握SIP,我们可以构建高效、安全且功能丰富的通信系统。

    sip.rar_SIP java_sip_sip java

    - PPT演示文稿,用图形化的方式解释SIP的工作流程和实例。 - 示例代码或项目,演示如何在实际项目中集成和使用SIP API。 对于想要学习SIP的Java程序员来说,这些资源将提供宝贵的理论知识和实践经验,帮助他们快速...

    Distributed SIP Analyzer-开源

    这种图形化表示方法清晰地展现了SIP会话的各个阶段,从初始邀请到通话结束,包括各种信令消息(如INVITE、ACK、BYE等)的交互顺序。这样的视图对于理解呼叫建立、保持和终止的过程非常有帮助,同时也能辅助用户检测...

Global site tag (gtag.js) - Google Analytics