Appendix B SIP Call Flows
Call Flow Scenarios for Successful Calls
Step | Action | Description |
|
|
|
15 | Cisco SIP IP phone B sends a | |
| to Cisco SIP IP phone A | SIP IP phone A with the same call ID as the previous |
|
| INVITE (sent to Cisco SIP IP phone A) and new SDP |
|
| session parameters (IP address), which are used to |
|
| reestablish the call. |
|
| Call_ID=1 |
|
| SDP: c=IN IP4 181.23.250.2 |
|
|
|
16 | 200 | Cisco SIP IP phone A sends a SIP 200 OK response to |
| to Cisco SIP IP phone B | Cisco SIP IP phone B. |
|
|
|
17 | Cisco SIP IP phone B sends a SIP ACK to Cisco SIP IP | |
| Cisco SIP IP phone A | phone A. The ACK confirms that Cisco SIP IP phone B has |
|
| received the 200 OK response from Cisco SIP IP phone A. |
|
|
|
A
18 | The call continues and then User B hangs up. Cisco SIP IP | ||||
| Cisco SIP IP phone A | phone B sends a SIP BYE request to Cisco SIP IP phone A. | |||
|
|
|
| The BYE request indicates that User B wants to release the | |
|
|
|
| call. | |
|
|
| |||
19 | 200 | Cisco SIP IP phone A sends a SIP 200 OK message to | |||
| to Cisco SIP IP phone B | Cisco SIP IP phone B. The 200 OK response notifies Cisco | |||
|
|
|
| SIP IP phone B that the BYE request has been received. | |
|
|
|
| The call session between User A and User B is now | |
|
|
|
| terminated. | |
|
|
|
| ||
The RTP channel between Cisco SIP IP phone A and Cisco SIP IP phone B is torn down. | |||||
|
|
|
| ||
14 | Cisco SIP IP phone B sends a | ||||
| to Cisco SIP IP phone C | SIP IP phone C with the same call ID as the previous | |||
|
|
|
| INVITE (sent to Cisco SIP IP phone C) and new SDP | |
|
|
|
| session parameters (IP address), which are used to | |
|
|
|
| reestablish the call. | |
|
|
|
| Call_ID=2 | |
|
|
|
| SDP: c=IN IP4 181.23.250.2 | |
|
|
| |||
15 | 200 | Cisco SIP IP phone C sends a SIP 200 OK response to | |||
| to Cisco SIP IP phone B | Cisco SIP IP phone B. | |||
|
|
|
|
|
|
|
|
| Cisco SIP IP Phone 7960 Administrator Guide | ||
|
|
| |||
|
|
|
|
| |
|
|
|
| ||
