Professional Documents
Culture Documents
Tìm hiểu về SIP
Tìm hiểu về SIP
Giao thức SIP dùng cho các kết nối giữa 2 MSC Server (qua interface Nc), giữa MSC server và IMS, giữa
MSC Server và NGN.
Là giao thức điều khiển nằm trong lớp APPLICATION LAYER.
Được dùng cho : + Khởi tạo (creation)
+ Sửa đổi (Modification)
+ Kết thúc phiên (Terminate of Session)
Giao thức SIP có thể sử dụng UDP hoặc SCTP làm giao thức truyền tải (Mặc định dùng UDP)
IE Description
Via Indicates the path through which the request has passed.
The Via header field prevents loops during the transmission of a request. It also ensures that
the corresponding response takes the same path as the request. Therefore, the transmission of
the request and response passes through firewalls or meets special requirements on route
selection.
Generally, the Via header field is in the following format:
Table 1 IEs in the Request-Line and message header
IE Description
The Via header field in the INVITE message is considered as an example here. In this
example, the request is transmitted through UDP and sent from a termination with the IP
address 129.9.30.50 and port number 5062.
The Call-ID header field in the INVITE message is considered as an example here. In this
example, 10.18.5.64 is a globally defined domain name and
57a5882d4d39645728558b68cc55eb19 is a local ID.
IE Description
The From header field in the INVITE message is considered as an example here. In this
example, 86263201800002 is the calling number of the session.
The To header field in the INVITE message is considered as an example here. In this example,
86263201800001 is the called number of the session.
The CSeq header field in the INVITE message is considered as an example here. In this
example, the sequence number of the INVITE message is 1.
Session- Indicates the session update interval for update negotiation. This header field can be contained
Expires in the INVITE, UPDATE, and 2xx messages.
The Session-Expires header field in the INVITE message is considered as an example here. In
this example, the local end sends a re-INVITE or UPDATE message to the peer end every
1800 seconds after the session is connected, to check whether the peer end has terminated the
session.
Contact Indicates the address for direction communication, that is, the URI of the originator.
This header field can be contained in the INVITE, ACK, REGISTER, 1xx, 2xx, and 3xx
messages.
The Contact header field in the INVITE and ACK messages indicates the location from which
the request is sent. Therefore, the callee can directly send requests, for example, a BYE
message, to the location identified by the Contact header field, rather than through the proxy
servers identified by the Via header field.
The Contact header field in the INVITE message is considered as an example here. In this
example, the IP address of the caller is 129.9.30.50.
Table 1 IEs in the Request-Line and message header
IE Description
The Allow header field in the INVITE message is considered as an example here. In this
example, the proxy server supports the following methods: INVITE, ACK, OPTIONS, BYE,
CANCEL, INFO, PRACK, NOTIFY, MESSAGE, REFER, and UPDATE.
Max- Indicates the maximum number of times the request can be forwarded before it arrives at the
Forward destination.
s When receiving a request containing the Max-Forwards header field, the proxy server or
gateway must check and update the value of the header field. The initial value of the header
field is 70. The value decreases by one at each hop, that is, when the request passes through
each proxy server or gateway. If the value reaches 0 but the request does not arrive at the
destination, the server sends a 483 message and terminates the request.
The header field is used to ensure that resources of the proxy servers are not wasted because
of loops during message transmission.
The Max-Forwards header field in the INVITE message is considered as an example here. In
this example, the request can be forwarded for 70 times before it arrives at the destination. If
the request does not arrive at the destination after being forwarded for 70 times, the request is
terminated.
RSeq Indicates the sequence number of a reliable provisional response message 1XX.
This header field consists of a decimal sequence number and a command name. When a
100rel message is sent and supported, this header field is contained in the reliable provisional
response 1XX message, which ensures the reliability of message transmission.
The RSeq header field in the 183 message is used as an example here. In this example, the
sequence number of the 183 message is 101.
RAck Indicates the sequence number of the PRACK message that maps a reliable provisional
response message 1XX.
This header field consists of three parts: two decimal sequence numbers and the message type.
The first decimal sequence number is the sequence number indicated by the RSeq header field
in the 1XX message. The second decimal sequence number and the message type are those
indicated by the CSeq header field in the 1XX message.
The RAck header field in the PRACK message is considered as an example here. In this
example, the PRACK message is a message in response to the 1XX message, in which the
RSeq header field has the sequence number 1 and the CSeq header field has the sequence
number 1 INVITE.
IE Description
This header field can be contained in the CANCEL and BYE messages.
The Reason header field in the BYE message is considered as an example here. In this
example, the release cause value is 16, which indicates that the session is released normally.
Content- Indicates the length of the message body, expressed in decimal values.
Length This header field is used to indicate the size of the message body to be sent. The empty line
used for separating the message header from the message body is not counted as Content-
Length. The value of Content-Length must not be smaller than 0. If no message body is
contained, the value must be set to 0.
The Content-Length header field in the INVITE message is considered as an example here. In
this example, the length of the message body is 444 bytes.
The Content-Type header field in the INVITE message is considered as an example here. In
this example, the media type of the message body is SDP.