Professional Documents
Culture Documents
Gii Thiu
SIP (Session Initiation Protocol) giao thc khi to phin.
c chun ha bi IETF (The Internet Engineering Task
Force) nm 1999.
Gii Thiu
RTSP
Cu Trc
Cu Trc
Cu Trc
SIP
USER
AGENT
UAC
SERVER
UAS
PROXY
REDIRECT
REGISTRAR
Cu Trc
SIP User Agent
- UAC (Client): khi to yu cu SIP.
- UAS (Server): chp nhn, chuyn tip hoc t chi yu cu.
10
Cu Trc
Proxy Server: chuyn tip cc SIP request ti thc th khc trong
mng.
11
Cu Trc
Redirect Server: l mt Server chp nhn mt yu cu
SIP, chuyn i a ch trong yu cu thnh mt a ch
mi v tr li a ch ny tr v Client.
Registrar: c dng ng k cc i tng trong
min SIP v cp nht v tr hin ti ca chng.
12
Cu Trc
SIP Components
Location
Server
Redirect
Server
Registrar
Server
PSTN
User Agent
Gateway
Proxy
Server
Proxy
Server
13
Cu Trc
14
c im Ca SIP
n gin
Hiu qu
Kh nng co dn
Mm do
H tr di ng
Kh nng lp trnh ca ngi dng
Kh nng m rng
15
Phn Loi
m hnh Client-Server.
17
ng k vi Registrar
INVITE
bt u thit lp cuc gi
ACK
BYE
yu cu kt thc
CANCEL
OPTIONS
xc nh nng lc my ch
18
REGISTER
Cho php UA cung cp v tr hin ti v URLs ng k
n Registrar.
C th cp nht v tr hin ti
Cc yu cu sau c chuyn hng ti v tr mi.
UA khng cn IP tnh,m c th dng DHCP.
19
INVITE
yu cu thit lp mt phin.
Thng tin mang trong phn Body cha.
Loi phin
a ch IP
S Port
Chun m ha
20
INVITE
K t bn tin INVITE th 2 gi i gi c gi l
re-INVITE.
re-INVITE c th s dng :
21
INVITE
ACK Dng kt thc qu trnh three way handshake.
22
OPTION
Yu cu v kh nng ca mt UA.
S nhn c cc phn hi v: cc bn tin h tr,codec...
23
UA s dng gi cc gi tin(RTP)
24
Method - MESSAGE
M rng giao thc SIP cho Instant Messaging (IM).
Yu cu:
25
REFER
REFER: ngh ngi nhn truy cp vo a ch ca
bn th 3.
Typical Use: Dng cho tnh nng Call Transfer.
26
27
1xx: Information
2xx: Success
Thnh cng.
3xx: Redirect
Yu cu khng c p ng
Li pha my phc v
S c ton mng
28
Responses: 1xx-3xx
SIP Response Code
100 Trying
180 Ringing
181 Call Is Being Forwarded
182 Queued
183 Session Progress
200 OK
300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
305 Use Proxy
380 Alternative Service
Brief Description
Request received and action is being taken
UA received INVITE and is alerting user
Used by proxy to indicate call is being forwarded
Called party unavailable, call queued
Used in early media and QoS setup
Request successful
Address resolved to several choices
User can no longer be found at Req-URI address
Temporarily cannot find user at Req-URI address
Resource MUST be accessed through proxy.
Call not successful. Alternatives possible.
29
Responses: 4xx
SIP Response Code
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
410 Gone
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Unsupported URI Scheme
420 Bad Extension
421 Extension Required
423 Registration Too Brief
480 Temporarily Unavailable
Brief Description
Request not understood due to malformed syntax
Request requires user authentication
Reserved for future use
UAS understood request and refuses to fulfill it
UAS finds that user doesn't exist in the domain
Method is understood but not allowed
Response content not allowed by Accept header
Client must first authenticate itself with proxy
UAS could not produce response in time
UAS resource unavailable; no forwarding addr.
Request contains body longer than UAS accepts
Req-URI longer than server is willing to interpret
Format of the body not supported by UAS
Scheme of URI unknown to server
UAS not understand protocol extension
UAS needs particular extension process request
Contact header field expiration time too small
UAS contacted successfully but user unavailable
30
Responses: 5xx-6xx
SIP Reponse Code
500 Server Internal Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Server Time-out
505 Version Not Supported
513 Message Too Large
600 Busy Everywhere
603 Decline
604 Does Not Exist Anywhere
606 Not Acceptable
Brief Description
UAS unexpected condition & cannot fulfill request
UAS not support functionality to fulfill the request
UAS Rx invalid response from a downstream server
UAS can't process due to overload or maintenance
UAS not Rx response from external server
UAS not support SIP version in request
Message length exceeded UAS capabilities
End systems contacted, user busy at all of them
End systems contacted, user explicitly decline
UAS has information Req-URI user not exist
Some aspects of Session Desc. not acceptable
31
32
33
34
35
36
Hot ng Ca SIP
TNG QUAN V HOT NG CA SIP
A CH SIP
NH V SERVER SIP
S GIAO DCH SIP
THAY I 1 PHIN ANG TN TI
HOT NG CHNH CA SIP
HOT NG CA PROXY SERVER
HOT NG CA REDIRECT SERVER
M HNH 1 CUC GI SIP IN HNH
CALL HOLD
CALL TRANSFER
M PHNG
Tng Quan
a ch SIP
a ch ca SIP cn c gi l b nh v ti nguyn
chung URL (Universal Resource Locator).
Tn ti di dng
user@host.
sip@hotmail.com
01684722708@192.168.1.1
39
Tng Quan
nh V Server
B1/ Nu phn host trong Request URI(username@host) l a
ch IP, Client tip xc vi Server a ch IP . Nu khng
phi th qua B2.
Tng Quan
S Giao Dch SIP
Khi phn host ca URL SIP c gii quyt, Client gi mt hoc
nhiu yu cu SIP n Server v nhn c mt hoc nhiu p ng t
Server. Cc yu cu cng vi cc p ng lin h vi nhau trong hot
ng ny to thnh s giao dch SIP. Tt c cc p ng cha cng cc
gi tr trong cc trng Call-ID, Cseq, To v From. iu ny cho php
cc p ng so khp vi cc yu cu.
Tng Quan
Thay i M Phin ang Tn Ti
REDIRECT SERVER
CALL
HOLD.
CALL
TRANSFER.
48
SIP SECURITY
Chng Thc
Cc Phng Thc Bo Bt
Cc loi Tn Cng
Gii Php Phng Th
Chng Thc
SIP S dng M ha MD5 ging vi HTTP chn vo
bn tin.
Password khng c th hin r rng m phi bm
thnh m MD5.
c yu cu bi Internet Telephony Service Providers
(ITSP)
50
51
S/MIME
Cung cp mt c ch bo mt Mail trn mng Voip.
52
Attacks : Cp ng k
Hacker gim st cc thng ip REGISTER t mt User v
thay i phn a ch trong thng ip ny
53
54
Attacks : Gi mo Call-ID
55
56
m bo vn QoS lp mng.
C ch bo mt vi gi tin RTP lp transport.
Firewall: p dng nhiu cp lc khc nhau.
Phone: Bo mt firmware.
Chng thc: TLS
58
59
60
61