Skip to content

Customer Journey

In order to create a Session for either a registration or verification process, Signalling Channels must be employed. This way, Audio Consumer is specified together with audio settings (format, codec, sample rate ...) and Session parameters (including call_id). This information is used by das-Peak Streaming to prepare required resources to receive audio streaming.

Once the Session is successfully created, a notification is sent via das-Peak Streaming Signalling Channel. At that moment, audio streaming must be sent to das-Peak Streaming via Audio Channel using settings agreed when the signalling has been established. das-Peak Streaming will collect that audio using related Audio Consumer and will notify the state of the session via Signalling Channel.

When the Session is completed and no more audio is required, das-Peak Streaming will notify the result via Signalling Channel.

Following sequence diagram shows how a registration/verification process is performed.

Sequence diagram

Check das-Peak Streaming API for details on how to perform an integration as a developer.

Credential Management

When a successful registration process is completed, a biometric credential is created and returned. Also, for a verification process, a biometric credential to compare against is required. Credential management is the process by which generated biometric credentials are stored upon a registration process and obtained before a verification process.

Currently, das-Peak Streaming does not implement any credential management. Credential management is delegated to client specific integration.