Skip to main content

Module packages

Module packages 

Source
Expand description

The two event packages that report state sipx already keeps (RFC 4235, RFC 3680).

Dialogs and registrations. Both come first among packages for the same reason: sipx has this state already — a dialog store and a registration lease — so they exercise crate::subscribe without also needing a state model of their own. Presence does need one, which is why it is a separate story.

Together they are what a busy-lamp field on a desk phone subscribes to: dialog says whether a line is ringing or in a call, reg says whether the phone is registered at all. Supported (S-35): sipx_call::Notifier selects these package documents through the live endpoint dispatcher. Breaking changes receive migration guidance while sipx remains pre-1.0.

Structs§

Contact
One registered contact, as a watcher sees it.
Dialog
One dialog, as a watcher sees it.
DialogWatch
The dialog event package (RFC 4235).
RegistrationWatch
The reg event package (RFC 3680).

Enums§

ContactEvent
What happened to a registered contact (RFC 3680 §5.1).
DialogState
Where a dialog has got to (RFC 4235 §3.7.1).
Direction
Which side started the dialog (RFC 4235 §4.1).

Constants§

DIALOG_INFO_TYPE
The MIME type a dialog notification carries (RFC 4235 §4).
REGINFO_TYPE
The MIME type a reg notification carries (RFC 3680 §4).