System information

Figure 8-1. Simplified SIP enterprise environment
Instead you can statically define an entry for each mailbox in the voicemail server’s
sip.conf file, indicating where the message notifications are to be sent. Rather than
defining the address of each endpoint, however, you can have the voicemail server send
all messages to the proxy, which will handle the relay of the message notifications to
the appropriate endpoints.
The voicemail server still needs to know about the SIP endpoints, even though the
devices are not registered directly to it. This can be done either through a sip.conf file
that identifies each SIP endpoint, or through a static real-time database that does the
same thing. Whether you use sip.conf or the Asterisk Realtime Architecture (ARA),
each endpoint will require an entry similar to this:
[messagewaiting](!) ; a template to handle the settings common
; to all mailboxes
type=peer
subscribecontext=voicemailbox ; the dialplan context on the voicemail server
context=voicemailbox ; the dialplan context on the voicemail server
host=192.168.1.1 ; ip address of presence server
[0000FFFF0001](messagewaiting) ; this will need to match the subscriber
; name on the proxy
mailbox=0000FFFF0001@DIR1 ; this has to be in the form mailbox@mailboxcontext
defaultuser=0000FFFF0001 ; this will need to match the subscriber
; name on the proxy
Using Asterisk As a Standalone Voicemail Server | 175