Call events (callevents)

Description

Call events. Sent only to connections from the master domain.

Table 1. System characteristics

Class

callevents

Domain type

master

Destination types

broker (callstore), wssubscr (participant domains; master domain — by subscription to the class or class event), svcscript, kafka (master and participant domains)

Source logical role

b2b

Handler logical role

broker, wssubscr, callstore (cdr builder)

Unlike other events, when sent to the KAFKA message broker and the wssubscr service, it is duplicated with binding to the working domains whose subscribers participate in the call. Moreover, if the call is cross-domain, then:

  • only events generated after routing reach the called side domain;

  • if called forks are in different domains, the domain whose subscriber did not answer receives only events related to its fork activity.

Events on the call activity diagram

The diagram shows the call processing flow represented as a stream of callevents events. Call processing starts with an incoming INVITE request to an instance of the B2B microservice.

The following stages are distinguished during call servicing:

  • Initiation

  • Routing

  • Call

  • Dialog

  • Post-processing

Initiation and routing stage events are generated by the B2B microservice in the initiator leg process. Call and dialog stage events are generated by the B2B microservice in the b2b dialog process. Post-processing stage events, as well as final activity monitoring events at the dialog stage, are generated by other microservices - they are highlighted in color and labeled with notifications.

Events in square brackets may or may not appear depending on conditions. Also, in branching blocks events appear only in the shown branches.

callevents