Date and time when the message was sent/received
Optional didA decentralized identifier
For example, this identifier may resolve to credential about personal data
Optional eventRaw SIP event
Optional extraAdditional SIP headers to be sent with the message
If message is outgoing (LOCAL): An incremental, unique id (parseable as number)
If message is incoming (REMOTE): A unique id
This is because according to the standard both unique numbers or strings are allowed
However, this library ALWAYS uses numbers for outgoing messages
Where the message was sent from (LOCAL or REMOTE)
Promise that's resolved if the message was received by the other communicating party
The message's state
Optional tagA free to use property for internal identification and matching of messages This is helpful, if you want to use ng112-js as a PSAP and want to tag incoming messages
The ETSI TS 103 698 message type
An internally generated id that is unique among all messages within ng112-js, even across multiple conversations
Chat message html
Chat message text
A list of URIs
Allows for resending local messages that have run into an error.
A new message is created (with new message id and unique id) and then sent via the original conversation.
IMPORTANT: Only local messages that are in state ERROR can be re-sent.
All other cases will result in an error.
To avoid running into message id collisions the original message is NOT reused!
a new message
Generated using TypeDoc
The corresponding conversation