HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols

Contents

Contents
14 SIP .............................................................................................................................................14-1
14.1 Description of SIP .....................................................................................................................................14-2 14.1.1 Related Terms ..................................................................................................................................14-2 14.1.2 SIP Addressing.................................................................................................................................14-4 14.2 SIP Message Types....................................................................................................................................14-4 14.2.1 Request Messages ............................................................................................................................14-5 14.2.2 Response Messages..........................................................................................................................14-5 14.3 SIP Message Structure...............................................................................................................................14-6 14.3.1 Request Message Structure ..............................................................................................................14-6 14.3.2 Response Message Structure..........................................................................................................14-12 14.4 Introduction to SIP-T ..............................................................................................................................14-13 14.5 SIP Signaling Procedures ........................................................................................................................14-14 14.5.1 Flows of Mobile Originated Calls Through SIP Trunks.................................................................14-14 14.5.2 SIP-T Signaling Procedure.............................................................................................................14-16

Issue 03 (2007-06-30)

Huawei Technologies Proprietary

i

Figures

HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols

Figures
Figure 14-1 Structure of a SIP request message ...............................................................................................14-7 Figure 14-2 Structure of a SIP response message...........................................................................................14-13 Figure 14-3 SIP flowchart of an MOC through SIP trunks ............................................................................14-15 Figure 14-4 A successful SIP-T procedure (PSTN-IP-PSTN)........................................................................14-16

ii

Huawei Technologies Proprietary

Issue 03 (2007-06-30)

................................................14-5 Table 14-2 Response messages..................................................................................................................................................................HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols Tables Tables Table 14-1 Request messages ......14-6 Issue 03 (2007-06-30) Huawei Technologies Proprietary iii .............................

5 SIP Signaling Procedures Describes Application and related terms of SIP protocol. SIP message structure. SIP Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-1 .2 SIP Message Types 14. Application of SIP-T. Examples about the SIP signaling procedures. Section 14. SIP message types.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP 14 About This Chapter The following table lists the contents of this chapter.3 SIP Message Structure 14.4 Introduction to SIP-T 14.1 Description of SIP 14.

if several people invite a user to the same multicast session. end users can originate and receive calls and access subscribed telecommunication services in any location at any time. Internet telephony. Therefore. Internet telephony gateways that connect public switched telephone network (PSTN) parties can also use SIP to set up calls between them. modify. with reliable or unreliable service. SIP supports five facets of establishing and terminating multimedia communications: User location: determining the end system to be used for communication User capabilities: determining the media and media parameters to be used User availability: determining the willingness of the called party to engage in communications Call setup: sending ring back tones to the called party and establishing call parameters at both called and calling parties Call handling and control: including redirection. UDP is preferred. SIP is one of the key protocols that implement the voice over IP (VoIP). A SIP call is identified by a globally unique Call-ID. and similar applications.14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14. That is. These sessions include multimedia conferences. SIP makes minimal assumptions about the underlying transport and network-layer protocols. SIP supports such services as: Name mapping Redirection Integrated services digital network (ISDN) services Intelligent network services These facilities also enable personal mobility. A point-to-point Internet telephony conversation maps into a single SIP call. each of these invitations will be a call. transfer.1 Related Terms This section depicts some terms related to SIP.1. The lower layer can provide either a packet or a byte stream service. SIP can use user datagram protocol (UDP) and transmission control protocol (TCP) as transport protocols. 14-2 Huawei Technologies Proprietary Issue 03 (2007-06-30) . Call A call consists of all participants in a conference invited by a common source. and termination of calls SIP can also initiate multi-party calls using a multipoint control unit (MCU) or fully meshed interconnection instead of multicast.1 Description of SIP SIP is an application-layer control protocol that can establish. and terminate sessions or calls. 14.

the requests sent from A to B and from B to A use the same Call-ID. rewrites a request before forwarding the message. A SIP redirect or proxy server uses a location service to obtain the possible location of a callee beyond the scope of this document. To. the client can directly initiate requests to these new addresses again. but comprises a transaction of its own. It can offer location services.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP Call Leg The combination of Call-ID. A redirect server implements the routing function instead of receiving or rejecting calls. A registrar needs to store the address mapping relationship in REGISTER requests in a database for subsequent call processes. Thus. Location Service Location services are offered by location servers. an ACK request has the same CSeq number as the corresponding INVITE request. It comprises all messages from the first request sent from the client to the server up to a final (non-1xx) response message sent from the server to the client. User Agent A user agent is a logical entity that initiates or receives SIP requests. For example. requiring no response. However. A proxy server may process requests internally or pass them on to other proxy servers. belonging to the same call leg. It is co-located with a proxy or redirect server. It acts as both a server and a client to route SIP requests to destinations. Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-3 . A normal call includes three transactions. Proxy Server A proxy server is an intermediary program. Call termination contains one request BYE. The latter is an acknowledgement that the final response is received. for a call between A and B. Redirect Server A redirect server performs the following: Accepts a SIP request. It interprets. and. and From identifies a call leg. Registrar A registrar is a server that accepts REGISTER requests. Maps the address into zero or more new addresses. Call initiation consists of two requests: INVITE and ACK. A call leg is actually a path of messages for a call. the manner in which a SIP server requests location services is beyond the scope of this manual. Transaction A SIP transaction occurs between a client and a server. if necessary. However. The former requires a response. The CSeq sequence number within a call leg identifies a transaction. Returns these addresses to the client.

1. a SIP URL has a syntax as follows: SIP:user:password@host:port. method-param: specifies methods or operations to be used. The default is 5060. When the field is set to "phone". transport-param: indicates which transport protocol to be used. This parameter is valid only when the Transport parameter is "UDP" and the maddr parameter is "multicast address". current destination (Request-URI). CSOFTX3000 supports SIP URLs in the format of E.0.164 number@IP address:port. the username is a telephone number and the corresponding end system is an IP telephony gateway. the use is not recommended. and to specify redirection addresses (Contact). ttl-param: designates the time-to-live (TTL) of a UDP multicast data packet. overriding the address supplied in the host field. The following parameters are optional: transport-param user-param method-param ttl-param maddr-param other-param Currently. because the passing of authentication information in texts is a security risk.14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14. user: consists of any characters in a form of e-mail address or telephone number. password: can be included in a SIP URL. A special function of SIP URL is to allow the host to be an IP telephony gateway with a telephone number as the username. TCP or UDP. The default is UDP.2 SIP Addressing Uniform resource locators (URLs) are used within SIP messages to indicate the originator (From). Commonly. This address is typically a multicast address. user-param: can be a telephone number. Two values are available for this field: IP and phone. port: indicates the port number to which a request is sent.transport-param|user-param|method-param| ttl-param|maddr-param|other-param The components of a SIP URI have the following meanings: SIP: indicates that SIP is used for the communication with a specified end system.1:5060.0. a public SIP port number. For example: Sip:8613301080001@127. However. maddr-param: provides the server address to be contacted for a user. host: can be a host domain name or an IP address. and final recipient (To) of a SIP request. 14-4 Huawei Technologies Proprietary Issue 03 (2007-06-30) .

ACK. Confirm that the client receives a final response to an INVITE request. and accepted. Table 14-1 describes the functions of these messages. They are INVITE. Final response The 1xx responses are provisional. 2xx: success — the action was successfully received. REGISTER. 14. ACK messages are used only with INVITE message. Indicate that the client wishes to release a call already set up. There are two types of response messages: Provisional response Provisional responses indicate progress. CANCEL.2.2.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP 14. − − − − − − 1xx: informational — a request received. REGISTER OPTIONS Register an address with a SIP server. understood.1 Request Messages Request messages are sent from a client to a server to activate a specific operation.2 SIP Message Types SIP messages are encoded in a text form. whereas other responses are considered final. a server returns a response message to a client. 4xx: client error — the request contains bad syntax or cannot be fulfilled at this server. CANCEL messages do not affect a completed request. There are two types of SIP messages: request and response. continuing to process the request.2 Response Messages After receiving and interpreting a request message. A request is considered completed if the client receives a final response from the server. and OPTIONS. Cancel a pending request. 3xx: redirection — further action needs to be taken in order to complete the request. Table 14-1 Request messages Message INVITE ACK BYE CANCEL Function Initiate a session request to invite a user to participate in a session. 5xx: server error — a SIP server fails to fulfill an apparently valid request. 6xx: global failure — the request cannot be fulfilled at any SIP server. 14. but do not terminate SIP transactions. BYE. Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-5 . Query a server about its capabilities.

OK. In addition. 14.3 SIP Message Structure Both request and response messages consist of the following: A start line The start line of a request message is a Request-Line. One or more header fields Header fields include general-header. request-header. Calls are being forwarded. Queue. response-header. A reliable provisional response. 14-6 Huawei Technologies Proprietary Issue 03 (2007-06-30) . a message body can encapsulate ISDN user part (ISUP) messages.14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols Table 14-2 describes common 1xx and 2xx response messages. whereas that of a response message is a Status-Line. The header fields contain different parameters. − General header fields Accept | Accept-Encoding | Accept-Langrage | Call-ID | Contact | Cseq | Date | Encryption | From | Record-Route | Require | Supported | Timestamp | To | User-Agent | ViaRequest header fields Authorization | Contact | Hide | Max-Forwards| Organization | Priority | Proxy-Authorization | Proxy-Require | Route | Require | Response-Key | Subject − Response header fields Proxy-Authenticate | Retry-After | Server | Unsupported | Warning | WWW-Authenticate − Entity header fields Allow | Content-Encoding | Content-Length | Content-Type | Expires An empty line indicating the end of the header fields An optional message body A message body can use session description protocol (SDP) as the description format of a session. Table 14-2 Response messages Status code 100 180 181 182 183 200 Message function Try. and entity-header. Ring.

an empty line. CRLF SDP Message body The Request-Line begins with a method token. The value and colon are separated by a space. Single space (SP) characters separate the elements. a message header.. Methods contain the following request message names: INVITE ACK OPTIONS BYE CANCEL REGISTER The message header of a request message can be a general header.1 Request Message Structure Figure 14-1 shows the structure of a SIP request message. A message header ends with a CRLF.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP 14. Figure 14-1 Structure of a SIP request message Status line Method Request-URI Call-ID: value From: value To: value Cseq: value Via: value Contact: value SIP-Version Message header Max-Forwards: value Content-Length: value Content-Type: value . A carriage-return line-feed (CRLF) distinguishes each parameter line in the message header. or an entity header. consisting of a request line. message header. and a message body. Each parameter consists of its name followed by a colon and a value. The order of message header parameters is not fixed. followed by the Request-URI identifying the peer URI and the SIP-Version identifying the protocol version.. followed by a message body. a request header.. Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-7 ...3. and ending with a CRLF..

A server copies the CSeq value from a request message to its response message. A Call-ID is generally in such a format as Call-ID:local-id@host The "host" is a host domain name or an IP address. Retransmissions of the same request message carry the same sequence number. and then discards. Command sequence (Cseq) Clients must add the CSeq general-header field to every request message. The "tag" may appear in the From field of a request message. Request and response messages must contain a To general-header field. This field is generally in such a format as From: display-name <SIP-URL>. The system must use the display name "Anonymous" if the identity of the client is to remain hidden. Call-IDs are case-sensitive. The "tag" value must be globally unique. indicating the initiator of a request message. any INVITE request message with a lower sequence number. Consecutive request messages that differ in request methods.14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols Figure 14-1 only shows some parameters possibly contained in the message header of a request message. headers. The server responds to. ACK and CANCEL request messages must contain the same CSeq value as that in the corresponding INVITE request message. and To fields identify a call leg. the combination of Call-ID.via-params comment Where. It must be present when two instances of a user sharing a SIP address make call invitations with the same Call-ID. A server copies the field from a request message to its response message. The initial value of a sequence number is arbitrary. 14-8 Huawei Technologies Proprietary Issue 03 (2007-06-30) . Parameter Descriptions The following describes some common parameters in the message header of a request message.tag=xxxx The "display-name" is characters rendered by a human-user interface. whereas a BYE request message must have a higher sequence number. In SIP. The "local-id" is a unique identifier within "host". To This field specifies the recipient of a request message. A server remembers the highest sequence number for any INVITE request message with the same Call-ID value. A CSeq field in a request contains the request method and a decimal sequence number unique within a Call-ID. or bodies but have the same Call-ID must contain monotonically increasing and contiguous sequence numbers. Call-ID This field uniquely identifies a SIP call. with the same syntax as the From field. Via This field is generally in such a format as Via:sent-protocol sent-by. From Request and response messages must contain a From general-header field. The user maintains the same tag throughout the call identified by the Call-ID. From.

For example: Via:SIP/2.0/UDP softx3000.0. Normally. set it to "1". Otherwise. a proxy server must check the top-most Via field. In the process of sending a request onwards. using the port indicated in "sent-by". If it does not.3 to reach the proxy server softx3000.ttl=16. discard the message. The Via field indicates the path taken by a request message so far.0.0. send the response message to the multicast address listed there.116:5061.bell-telephone. every host that sends or forwards a SIP message adds a Via field indicating the path traversed.169. Otherwise. the Via field cannot be relied on to route response messages.0. To prevent this. this response message reaches its destination. 3.169. If there is no second Via field. send the message to the address indicated in the "received" parameter. The client originating a request message must insert into the request message a Via field containing its host name or network address. A proxy sending a request to a multicast address must add the "maddr" parameter to its Via field. Notices the mismatch.maddr=191.bell-telephone. which assists in firewall traversal and other unusual routing situations. However. Appends its own address at the top as a new Via field. the message originates from 10. The TTL of the response message should be the value indicated in the "ttl" parameter.0/UDP 191. 2.12. Adds a "received" parameter to the Via field of previous hop.10. The proxy sever does the following: 1. This prevents request looping and ensures response messages take the same path as its request messages.1 and traverses a NAT with the IP address 199. send the message to the address indicated by the "sent-by" value in the second Via field. If neither of the previous cases applies. An example of the Via field is: Via: SIP/2. If the value of Via field mismatches the previous hop address seen from the proxy server.1. delete this Via field.com:5060 Via:SIP/2. the proxy adds a "received" parameter to the Via field inserted by the previous hop.via-params=via-hidden | via-ttl | via-maddr | via-received | via-branch. A proxy server or a client processes the Via field in a response message according to the following rules: The first Via field should indicate the proxy or client processing this response message. network address translators (NATs) may change the source address and port number of a request message.136.branch=a7c6a8dlze Contact Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-9 .HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP sent-protocol=protocol-name / protocol-version / transport.20. If a server receives a request message containing an "maddr" parameter in the topmost Via field.30 In this example. If that parameter is not present.com.169. containing the address that the packet actually came from.0/UDP 10. or port 5060 if none is present. and the port number at which it wishes to receive response messages if it does not use the default port number. each proxy server must add its own address as a new Via field before any existing Via fields.172. If the second Via field contains a "received" but not a "maddr" parameter. the server will transfer the request message to the multicast address listed in the "maddr" parameter.received=191.1:5060. In this case. the processing depends on whether the Via field contains a "maddr" or a "receiver" parameter: If the second Via field contains a "maddr" parameter.

Any Content-Length greater than or equal to zero is a valid value. ACK. and in 1xx.q=0. OPTIONS. 2xx. If the received value is zero (0) and the request message does not reach its destination address. This field is generally in such a format as Max-Forwards: decimal integrals Allow This field lists the set of methods supported by proxy servers. in decimal number of octets. The "action" parameter is only applicable to REGISTER request messages. It is subtracted by 1 every time a request message traverses a proxy server or gateway. The "expires" parameter indicates how long a uniform resource identifier (URI) is valid. The "extension-attribute" is an extension name. It provides a URL where a user can be reached for further communications. Each proxy server or gateway recipient of a request message containing a Max-Forwards field must check and update the value of the field before forwarding the request. If this parameter is not specified. the action taken depends on server configuration. An example of the Contact field is: Contact: <Sip:66500002@191. the message header must contain this field. The purpose of setting this field is to prevent consuming proxy server resources in the case of loop during message transfer. and 3xx response messages. ACK. Applications use this field to indicate the size of a message-body to be transferred. The initial value is 70. It indicates whether a server expects future requests to the client for the server proxy or redirection service.action= “proxy” | “redirect”. The "q" value ranges from 0 to 1.7. directly to the caller rather than through a series of proxy servers. This field is generally in such a format as Content-Length: decimal number of octets Content-Type 14-10 Huawei Technologies Proprietary Issue 03 (2007-06-30) .110:5061>. BYE Content-Length This field indicates the size of a message-body. CANCEL. Higher values indicate higher preference. An empty line separating a message header and a message body is beyond the scope of the Content-Length. and REGISTER request messages. This field is generally in such a format as Contact:name-addr. the Content-Length header field must be set to zero. An example of the Allow field is: Allow: INVITE. If no body is present in a message.q=value.14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols This field can appear in INVITE. such as BYE.1. If TCP serves as the transport protocol.expires=3600 Max-Forwards This field limits the number of times for which a request message is allowed to be forwarded. the server returns 483 (too many hops) and terminates this request.extension-attribute The "name-addr" form is the same as that in the To and From fields.169. INVITE and ACK request messages contain Contact fields indicating from which location a request message originates. This parameter can be a number indicating seconds or a quoted string containing a SIP-date.expires=value. This allows the called subscriber to send future request messages.

95 t: 0 0 m: audio 30000 RTP/AVP 8 0 4 18 a: rtpmap:8 PCMA/8000 a: rtpmap 0 PCMU/8000 a: rtpmap 4 G723/8000 a: rtpmap 18 G729/8000 The following details the example: Line 1: Request-Line The Method is INVITE.110" and SIP-Version "2. identifying a specific invitation.116:5061.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP This field indicates the media type of the message-body sent to the recipient.1.169. Line 6: Via field It indicates the path taken by the request.0 From: <sip:44510000@191. in which "SIP" is the protocol name. "SIP/2. Line 2: From field It indicates the address of the request initiator is "sip:44510000@191.116".116:5061> Max-Forwards:70 Content-Length:230 Content-Type: application/sdp v: 0 o: HuaweiSoftX3000 1073741831 1073741831 IN IP4 191. "191.169.169.0".1. "tag" is "1ccb6df3".1. "2.1.169.116>.169.1.116 s: Sip Call c: IN IP4 191.1.1.169.116:5061" indicates that the CSOFTX3000 IP address of the Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-11 .1.110> CSeq: 1 INVITE Call-ID: 20973e49f7c52937fc6be224f9e52543@sx3000 Via: SIP/2. Line 3: To field It specifies the address of the request recipient is "sip:66500002@191. it must contain the Content-Type field.1. Request Message Examples An example of SIP request message is: INVITE sip:66500002@191. If the message-body is not null.tag=1ccb6df3 To: <sip:66500002@191. followed by the Request-URI "sip:66500002@191.0/UDP 191.169.169.0/UDP" specifies the sent protocol. Line 4: Cseq field Line 5: Call-ID field It is globally unique. differentiating the users who share a SIP address and make call invitations with the same Call-ID.1.0" is the protocol version.1.169.110".169.110 SIP/2.169.branch=z9hG4bkbc427dad6 Contact: <sip:44510000@191. and "UDP" is the transport layer. An example of the Content-Type field is: Content-Type: application/sdp Expires This field gives the time after which the message content expires.

1. "branch=z9hG4bkbc427dad6" is the "branch" parameter. Line 8: Max-Forwards field It specifies that the maximum number of intermediate proxy servers or gateways that the request message is allowed to traverse is 70.2 Response Message Structure Figure 14-2 shows the structure of a SIP response message. see SDP-related documents.169.116" and port number is "5061".14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols sender is "191. Line 11: an empty line It indicates that the message header ends and below is the message body described by the SDP. 14-12 Huawei Technologies Proprietary Issue 03 (2007-06-30) . consisting of: A status line A message header An empty line A message body A line feed character distinguishes each parameter line in the message header. v=<protocol version> o=<user name><session ID><version><network type><address type><address> s=<subject> c=<network type><address type><connection address> t=<start time><end time> m=<media><port><transport layer><format list> a=rtpmap:<payload type><encoding><code> 14.116:5061" rather than through the Via field.1.169. Parameters vary with response messages. Line 9: Content-Length field It indicates the length of the message body. identifying branches when the CSOFTX3000 distributes request messages concurrently.3. Line 7: Contact field It indicates subsequent request messages such as BYE can be directly sent to "sip:44510000@191. The following briefs the message body. Line 10: Content-Type field It indicates the message contains a single message body SDP. For details.

The type of the message body with ISUP encapsulated in it is Application /ISUP. 2xx. The Reason-Phrase gives a short textual description of the Status-Code. and 6xx. The Status-Code is a 3-digit integer code that indicates the type of a request message. The purpose of SIP-T is to provide better PSTN-SIP interconnection. and PSTN-IP-PSTN. 14. It is a set of mechanisms for encapsulating ISUP signaling within SIP.3.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP Figure 14-2 Structure of a SIP response message SIPVersion ReasonPhrase Status line Status-Code Call-ID: value From: value To: value Cseq: value Via: value Contact: value Message header Max-Forwards: value Content-Length: value Content-Type: value .. which type is Application/ ISUP. a Status-Code. namely. including two cases: A SIP message does not carry SDP.. respectively defining six types of SIP response messages. CRLF SDP Message body A Status-Line consists of a SIP protocol version. 5xx. Encapsulation means that SIP message bodies contain ISUP messages. For full definitions. The parameters in the header of a response message are the same as those in a request message header.4 Introduction to SIP-T The session initiation protocol for telephones (SIP-T) is an extension of SIP.2. SIP-T adopts SIP message structures and flows. Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-13 .2 "Response Messages".. encapsulation and mapping apply to SIP-T.. see section 14. and its associated textual phrase (Reason-Phrase).1 "Request Message Structure". 3xx. ISUP messages are encapsulated within the SIP message body... There are three call models: PSTN-IP. Two techniques. 4xx. IP-PSTN. A SIP message that carries SDP contains multiple message bodies. For details. The Status-Code includes 1xx. see section 14.

SIP-T defines the procedure for mapping of information from ISUP to SIP. for example. an IAM must be sent on receipt of an INVITE. a REL for BYE. For example. 14.5 SIP Signaling Procedures This session does not describe the procedure that the CSOFTX3000 controls media gateways (MGWs) to set up bearers. SIP-T specifies the rules that govern the mapping between ISUP and SIP messages. and so on. Figure 14-3 shows the flowchart. 14-14 Huawei Technologies Proprietary Issue 03 (2007-06-30) . the called number in an ISUP IAM must be mapped onto the SIP "To" header field.5.1 Flows of Mobile Originated Calls Through SIP Trunks The following describes the procedure of a mobile originated call (MOC) through the SIP trunks between CSOFTX3000 devices. A mapping between ISUP and SIP messages can be as follows: IAM = INVITE ACM = 180 RINGING ANM = 200 OK REL = BYE RLC = 200 OK for BYE ISUP parameter-SIP header mapping A SIP request message that is used to set up a call contains information that enables the message to be correctly routed to its destination. a called number. 14. Conversely.14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols Mapping includes: ISUP-SIP message mapping Gateways must generate a specific ISUP message for each SIP message received. For example. gateways can also generate a specific SIP message for each ISUP message received.

After number analysis. At the time. indicating that it receives the request message and message processing is in progress. 8. containing the called bearer information in the message body. Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-15 . the CSOFTX3000 finds that the outgoing office interacts with the ingoing office through SIP. indicating setup of the signaling path. 2. The CSOFTX3000 sends an ASS_REQ to the BSS. 6. 3. If the called subscriber hooks off. 7. 5. The BSS returns an ASS_CMP. the CSOFTX3000 sends the called office an INVITE containing the calling bearer information in the message body. the called office sends the local CSOFTX3000 a 200 OK. After the MGW fulfils bearer setup under the control of the local CSOFTX3000. The called office returns the CSOFTX3000 a 100 Trying. The CSOFTX3000 receives a 180 Ringing.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP Figure 14-3 SIP flowchart of an MOC through SIP trunks BSS CSOFTX3000 CM_SERVICE_REQ CSOFTX3000 ASS_REQ ASS_CMP INVITE 100 Trying 180 Ringing 200 OK ACK CLEAR_REQ BYE CLEAR_CMD 200 for BYE CLEAR_CMP 1. 4. An ordinary mobile subscriber initiates a CM_SERVICE_REQ. the local CSOFTX3000 sends the peer office an ACK.

the local CSOFTX3000 returns a 200 for BYE. 3. it sends a CLEAR_CMD to the BSS at the calling side. A PSTN subscriber dials. the called office sends a BYE to the local CSOFTX3000. On receipt of the BYE. On receipt of the BYE. The BSS returns a CLEAR_CMP. the called office sends a 200 for BYE to CSOFTX3000. the CSOFTX3000 receives a CLEAR_REQ. CSOFTX3000 B returns CSOFTX3000 A a 100 Trying. CSOFTX3000 A preserves the received IAM in an INVITE message body that it sends to CSOFTX3000 B. 5. indicating that it receives the request message and message processing is in progress. 4. LS A sends an IAM to CSOFTX3000 A. If the called subscriber hooks on.2 SIP-T Signaling Procedure The following illustrates the call flow of transparency across points of PSTN-SIP interconnection in terms of the PSTN-IP-PSTN call model. If the calling subscriber hooks on. The BSS sends a CLEAR_CMP to confirm the completion of calling party disconnect. it sends a BYE to the called office and a CLEAR_CMD to the BSS at the calling side. 14-16 Huawei Technologies Proprietary Issue 03 (2007-06-30) . CSOFTX3000 B extracts the IAM from the INVITE and sends the IAM to LS B. Figure 14-4 A successful SIP-T procedure (PSTN-IP-PSTN) LS A CSOFTX3000 A CSOFTX3000 B LS B IAM INVITE IAM 100 Trying ACM 180 Ringing ACM 200 OK ANM ACK ANM REL BYE REL RLC RLC 200 OK 1.14 SIP HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 9. 10. Meanwhile. The called PSTN phone rings. At the time. Figure 14-4 shows the flowchart.5. CSOFTX3000 B preserves the received ACM in a 180 Ringing that sends to CSOFTX3000 A. 14. 2. Meanwhile. LS B sends an ACM to CSOFTX3000 B.

9. CSOFTX3000 A extracts the RLC from the received 200 OK and forwards the RLC to LS A. LS A receives the ACM. If the calling PSTN subscriber hooks on. CSOFTX3000 A extracts the ACM from the received 180 Ringing and forwards the ACM to LS A. 8. At this time. The calling PSTN subscriber hears ring back tones.HUAWEI CSOFTX3000 Technical Manual – Signaling Protocols 14 SIP 6. CSOFTX3000 A sends an ACK to CSOFTX3000 B. 12. both parties can communicate through an established bidirectional signaling path. If the called PSTN subscriber hooks off. If the calling PSTN subscriber hooks on. CSOFTX3000 B extracts the REL from the received BYE and forwards the REL to LS B. acknowledging receipt of the final message from CSOFTX3000 B in response to the INVITE. LS A sends a REL to CSOFTX3000 A. Issue 03 (2007-06-30) Huawei Technologies Proprietary 14-17 . 7. 10. LS B sends a RLC to CSOFTX3000 B. CSOFTX3000 A extracts the ANM from the received 200 OK and forwards the ANM to LS A. 15. CSOFTX3000 B preserves the received ANM in a 200 OK that it sends to CSOFTX3000 A. 13. CSOFTX3000 B preserves the received RLC in a 200 OK message body that it sends to CSOFTX3000 A. 11. On receipt of the REL. CSOFTX3000 A preserves the received REL in a BYE message body that it sends to CSOFTX3000 B. LS B sends an ANM to CSOFTX3000 B. LS B sends busy tones to the called PSTN subscriber. 14.

Sign up to vote on this title
UsefulNot useful