Microtronix Access User Guide
9.7 SMDI Messaging Examples
1) SIP Notify message-summary received from the UMS contains the following fields:
● SIP-URI: sip:551234567@domain1
● message content: Messages-waiting: yes
If enabled, the telephone number 55512134567 is looked up in the database for the destination switch
interface. If not in the database, the switch interfaces are scanned for a domain name match to
”domain1” starting at the lowest configured switch interface.
When a switch interface is determined and it is SMDI, the telephone number is used to construct the
SMDI MWI message to be sent to the matching switch.
OP:MWI 5551234567!<ctrl-D>
2) SIP Notify message summary received from the UMS contains the following fields:
● SIP-URI: sip:551234567@domain1
● message content: Messages-waiting: no
An SMDI MWI message will be sent to the matching switch.
RMV:MWI 5551234567!<ctrl-D>
3) If a transmitted SMDI MWI message contains a telephone number not assigned to the destination
switch, it will respond with an SMDI invalid message.
MWI5551234567 INV<cr><lf><ctrl-Y>
This will cause the MWI Gateway to remove the current SMDI interface assignment in the database
and re-assign to the next available switch interface number. It will transmit an MWI message to the
next switch (could be SIP Notify or SMDI).
9.8 Standards
● SMDI: Simplified Message Desk Interface (Bellcore TR-NWT-000283)
● RFC 3261: Session Initiation Protocol (SIP)
● RFC 3265: Session Initiation Protocol - Specific Event Notification: (EXT. of 3261)
● RFC 3842: A Message Summary and MWI Event Package for SIP
● RFC 3966: The tel: URI for telephone numbers
● ITU-T E.123 Notation for national and international telephone numbers
87