...
Following are the terms which are used in this document
Sip SIP Message | It is the type of message through which CUCM communicates with VRS. It It can either be a Request or a Response. It can either have content or notan empty message. | ||||||||
Call | Call determines a complete object containing all sessions in it. The sessions can be multiple in case of A call aggregates all sessions of a call. An actual call may have several sessions due to hold/resume or Transfer transfer/conference scenarios. A call object contains all sessions of a call. | ||||||||
Session | Session A session determines a single recording containing both parties streams/legsjoining all voice streams of all participants. | ||||||||
Session _LegsLeg | A Session legs determine Leg is the voice stream of a single person in any callone participant in the session. A Normal call has minimum of 2 session has at least two session_legs for both parties stream. | ||||||||
Calling Number | This is the Endend-user/ Party party who dialed initiated the SIP call to anyone. | ||||||||
Called Number | This is the Endend-user/ Party party who received the incoming call. | ||||||||
Force Termination | It is a flag which represents that a recording for this call is corrupted or incomplete. This recording might be empty or incomplete. | ||||||||
Zombie Timer | If the call is terminated for equal or more then this interval we mark it Terminated. | ||||||||
Thread Timer | This is the time interval after which our internal process check all the terminated calls and send them to the Mixer. | ||||||||
Call_Timeout | If no RTP packets received from the socket for this amount of time we mark it “Force Terminated” | Topic | Kafka Topic is basically a queue by which we send call information from recorder to mixer |
Components
Expertflow Voice Recording Solution consists of 3 components. These components communicate with each other through Apache Kafka.
...