1. Call Traffic Monitoring Guide
  2. Selective Call Recording SIPREC
  3. SIPREC Call Flows
  4. Selective Recording
  5. SRS Indicates Busy in Call (recording not required)

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.

The SRS indicates busy without recording required call flow is described below.
  • UA-A sends INVITE to Oracle® Enterprise Session Border Controller.
  • Oracle® Enterprise Session Border Controller forwards INVITE to UA-B.
  • UA-B responds with OK to Oracle® Enterprise Session Border Controller.
  • Oracle® Enterprise Session Border Controller forwards OK response to UA-A.
  • Oracle® Enterprise Session Border Controller sends INVITE to SRS1 with SDP and metadata.
  • SRS1 responds to Oracle® Enterprise Session Border Controller with 436 BUSY HERE.
  • RTP stream initiated between UA-A andOracle® Enterprise Session Border Controller.
  • RTP stream initiated between Oracle® Enterprise Session Border Controller and UA-B.
  • Oracle® Enterprise Session Border Controller sends INVITE to SRS2 with SDP and metadata.
  • SRS2 responds with OK to Oracle® Enterprise Session Border Controller.
  • RTP stream initiated between Oracle® Enterprise Session Border Controller and SRS2.
  • UA-A sends BYE to Oracle® Enterprise Session Border Controller.
  • Oracle® Enterprise Session Border Controller responds with OK to UA-A.
  • Oracle® Enterprise Session Border Controller sends BYE to UA-B.
  • UA-B responds with OK to Oracle® Enterprise Session Border Controller.
  • Oracle® Enterprise Session Border Controller sends BYE to SRS2.
  • SRS2 responds with OK to Oracle® Enterprise Session Border Controller.