Home Unified Communications UC Chalk Talks H.323 to SIP Call Flow
H.323 to SIP Call Flow PDF Print E-mail
Written by Paul Stryer   
Wednesday, 04 November 2009 20:07

 

H.323 to SIP Call Setup and Disconnect

Figure 1 illustrates a successful phone-call setup and disconnect. In this scenario, the two end users are User A and User B. User A is located at PBX A. PBX A is connected to Gateway 1 (SIP gateway) via a T1/E1. User B is located at a Cisco SIP IP phone. Gateway 1 is connected to the Cisco SIP IP phone over an IP network.

The call flow is as follows:

1. http://www.cisco.com/univercd/illus/images/blank.gifUser A calls User B.

2. http://www.cisco.com/univercd/illus/images/blank.gifUser B answers the call.

3. http://www.cisco.com/univercd/illus/images/blank.gifUser B hangs up.



Figure 1 H.323 to SIP Call Flow


Step

Action

Description

1. http://www.cisco.com/univercd/illus/images/blank.gif

Setup—PBX A to Gateway 1

Call setup is initiated between PBX A and Gateway 1. Setup includes the standard transactions that take place as User A attempts to call User B.

2. http://www.cisco.com/univercd/illus/images/blank.gif

INVITE—Gateway 1 to Cisco SIP IP phone

Gateway 1 maps the SIP URL phone number to a dial peer. The dial peer includes the IP address and the port number of the SIP-enabled entity to contact. Gateway 1 sends a SIP INVITE request to the address it receives as the dial peer, which, in this scenario, is the IP phone. In the INVITE request:

http://www.cisco.com/univercd/illus/images/blank.gifThe IP address of the phone is inserted in the Request-URI field.

http://www.cisco.com/univercd/illus/images/blank.gifPBX A is identified as the call session initiator in the From field.

http://www.cisco.com/univercd/illus/images/blank.gifA unique numeric identifier is assigned to the call and is inserted in the Call-ID field.

http://www.cisco.com/univercd/illus/images/blank.gifThe transaction number within a single call leg is identified in the CSeq field.

http://www.cisco.com/univercd/illus/images/blank.gifThe media capability that User A is ready to receive is specified.

http://www.cisco.com/univercd/illus/images/blank.gifThe port on which the gateway is prepared to receive the RTP data is specified.

3. http://www.cisco.com/univercd/illus/images/blank.gif

Call Proceeding—Gateway 1 to PBX A

Gateway 1 sends a Call Proceeding message to PBX A to acknowledge the Call Setup request.

4. http://www.cisco.com/univercd/illus/images/blank.gif

100 Trying—Cisco SIP IP phone to Gateway 1

The phone sends a SIP 100 Trying response to Gateway 1. The response indicates that the INVITE request has been received.

5. http://www.cisco.com/univercd/illus/images/blank.gif

180 Ringing—Cisco SIP IP phone to Gateway 1

The phone sends a SIP 180 Ringing response to Gateway 1. The response indicates that the user is being alerted.

6. http://www.cisco.com/univercd/illus/images/blank.gif

Alerting—Gateway 1 to PBX A

Gateway 1 sends an Alert message to User A. The message indicates that Gateway 1 has received a 180 Ringing response from the phone. User A hears the ringback tone that indicates that User B is being alerted.

7. http://www.cisco.com/univercd/illus/images/blank.gif

200 OK—Cisco SIP IP phone to Gateway 1

The phone sends a SIP 200 OK response to Gateway 1. The response notifies Gateway 1 that the connection has been made.

8. http://www.cisco.com/univercd/illus/images/blank.gif

Connect—Gateway 1 to PBX A

Gateway 1 sends a Connect message to the PBX A. The message notifies PBX A that the connection has been made.

9. http://www.cisco.com/univercd/illus/images/blank.gif

Connect ACK—PBX A to Gateway 1

PBX A acknowledges Gateway 1's Connect message.

10. http://www.cisco.com/univercd/illus/images/blank.gif

ACK—Gateway 1 to Cisco SIP IP phone

Gateway 1 sends a SIP ACK to the phone. The ACK confirms that Gateway 1 has received the 200 OK response. The call session is now active.

11. http://www.cisco.com/univercd/illus/images/blank.gif

BYE—Cisco SIP IP phone to Gateway 1

User B terminates the call session. The phone sends a SIP BYE request to Gateway 1. The request indicates that User B wants to release the call.

12. http://www.cisco.com/univercd/illus/images/blank.gif

Disconnect—Gateway 1 to PBX A

Gateway 1 sends a Disconnect message to PBX A.

13. http://www.cisco.com/univercd/illus/images/blank.gif

Release—PBX A to Gateway 1

PBX A sends a Release message to Gateway 1.

14. http://www.cisco.com/univercd/illus/images/blank.gif

200 OK—Gateway 1 to Cisco SIP IP phone

Gateway 1 sends a SIP 200 OK response to the phone. The response notifies the phone that Gateway 1 has received the BYE request.

15. http://www.cisco.com/univercd/illus/images/blank.gif

Release Complete—Gateway 1 to PBX A

Gateway 1 sends a Release Complete message to PBX A, and the call session terminates.



Add this page to your favorite Social Bookmarking websites
Reddit! Del.icio.us! Mixx! Free and Open Source Software News Google! Live! Facebook! StumbleUpon! TwitThis Joomla Free PHP
Last Updated on Wednesday, 04 November 2009 20:22
 
4 Votes

0 Comments

Add Comment


    • >:o
    • :-[
    • :'(
    • :-(
    • :-D
    • :-*
    • :-)
    • :P
    • :\
    • 8-)
    • ;-)



    Click to get a new image.