SRS Indicates Busy in Call (recording not required)
The following illustration shows the Session Recording Server (SRS) is BUSY for a call session. Recording is not required in this call flow.
| Call Flow Description | |
|---|---|
| ① UA-A sends INVITE to Oracle® Enterprise Session Border Controller. | ⑨ Oracle® Enterprise Session Border Controller sends INVITE to SRS2 with SDP and metadata. |
| ② Oracle® Enterprise Session Border Controller forwards INVITE to UA-B. | ⑩ SRS2 responds with OK to Oracle® Enterprise Session Border Controller. |
| ③ UA-B responds with OK to Oracle® Enterprise Session Border Controller. | ⑪ RTP stream initiated between Oracle® Enterprise Session Border Controller and SRS2. |
| ④ Oracle® Enterprise Session Border Controller forwards OK response to UA-A. | ⑫ UA-A sends BYE to Oracle® Enterprise Session Border Controller. |
| ⑤ Oracle® Enterprise Session Border Controller sends INVITE to SRS1 with SDP and metadata. | ⑬ Oracle® Enterprise Session Border Controller responds with OK to UA-A. |
| ⑥ SRS1 responds to Oracle® Enterprise Session Border Controller with 436 BUSY HERE. | ⑭ Oracle® Enterprise Session Border Controller sends BYE to UA-B. |
| ⑦ RTP stream initiated between UA-A andOracle® Enterprise Session Border Controller. | ⑮ UA-B responds with OK to Oracle® Enterprise Session Border Controller. |
| ⑧ RTP stream initiated between Oracle® Enterprise Session Border Controller and UA-B. | ⑯ Oracle® Enterprise Session Border Controller sends BYE to SRS2. |
| ⑰ SRS2 responds with OK to Oracle® Enterprise Session Border Controller. | |
