Call events (callevents)
Description
Call events. Only sent to connections from the master domain.
Class |
|
Domain type |
|
Destination types |
|
The Logical Role , source |
|
Logical role handler |
Unlike other events, when sending KAFKA messages to the broker and the wssubscr service is duplicated with binding to the working domains whose subscribers are involved in the call. That said, if the call is cross-domain, then:
-
only events generated after marshrutization will enter the domain of the called party;
-
If the called forks are in different domains, the domain whose subscriber has not picked up the phone will receive only events related to the activity of its fork.
Events on the call activity diagram
The diagram shows the call handling process represented as an event stream callevents. Call processing begins with an incoming INVITE request to the microservice instance B2B.
There are distinct stages in the call maintenance process:
-
Initiation
-
Routing
-
Challenge
-
Dialogue
-
Post-processing
The events of the initiation and routing stages are generated by the B2B microservice during the initiator’s shoulder process. The events of the call and dialog stages are generated by the B2B microservice during the b2b dialog process. The post-processing stage events, as well as the final monitoring events of activity monitoring in the dialog stage are generated by other microservices - they are highlighted in color and signed with notifications.
Events in square brackets may or may not appear depending on the conditions. Also, in branching blocks, events appear only in the branches given.
