2006-02-10 21:50:56 +00:00
|
|
|
; Asterisk SMDI configuration
|
|
|
|
|
|
|
|
|
|
[interfaces]
|
|
|
|
|
; Specify serial ports to listen for SMDI messages on below. These will be
|
2009-05-27 16:07:57 +00:00
|
|
|
; referenced later in chan_dahdi.conf. If you do not specify any interfaces
|
|
|
|
|
; then SMDI will be disabled. Interfaces can have several different attributes
|
2006-02-10 21:50:56 +00:00
|
|
|
; associated with them.
|
|
|
|
|
|
|
|
|
|
; Set the number of stop bits to use per character here. The default is no,
|
|
|
|
|
; in which case one stop bit will be used.
|
|
|
|
|
|
|
|
|
|
;twostopbits = no
|
|
|
|
|
|
2006-09-11 16:41:49 +00:00
|
|
|
; Character size or bit length is the size of each character sent across the
|
2006-02-10 21:50:56 +00:00
|
|
|
; link. Character size can be 7 or 8. The default is 7.
|
|
|
|
|
|
|
|
|
|
;charsize = 7
|
|
|
|
|
|
|
|
|
|
; If you need parity checking enabled you can turn it on here. Acceptable
|
|
|
|
|
; values are even, odd, and none. The default is even.
|
|
|
|
|
|
|
|
|
|
;paritybit = even
|
|
|
|
|
|
|
|
|
|
; The baudrate to use for this port. Acceptable values are 1200, 2400, 4800,
|
|
|
|
|
; and 9600. The default is 9600.
|
|
|
|
|
|
|
|
|
|
;baudrate = 1200
|
|
|
|
|
|
|
|
|
|
; Often the numbering scheme for a set of mailboxes or extensions will not be 7
|
|
|
|
|
; or 10 digits (as SMDI requires). Use the msdstrip option to strip unused
|
|
|
|
|
; digits from the start of numbers.
|
|
|
|
|
|
|
|
|
|
;msdstrip = 0
|
|
|
|
|
|
|
|
|
|
; Occasionally Asterisk and the SMDI switch may become out of sync. If this
|
|
|
|
|
; happens, Asterisk will appear one or several calls behind as it processes
|
2006-09-11 16:41:49 +00:00
|
|
|
; voicemail requests. To prevent this from happening, adjust the msgexpirytime.
|
2006-02-10 21:50:56 +00:00
|
|
|
; This will make Asterisk discard old SMDI messages that have not yet been
|
|
|
|
|
; processed. The default expiry time is 30000 milliseconds.
|
|
|
|
|
|
|
|
|
|
;msgexpirytime = 30000
|
|
|
|
|
|
|
|
|
|
;smdiport => /dev/ttyS0
|
Merged revisions 104119 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4
........
r104119 | russell | 2008-02-25 18:25:29 -0600 (Mon, 25 Feb 2008) | 33 lines
Merge changes from team/russell/smdi-1.4
This commit brings in a significant set of changes to the SMDI support in Asterisk.
There were a number of bugs in the current implementation, most notably being that
it was very likely on busy systems to pop off the wrong message from the SMDI message
queue. So, this set of changes fixes the issues discovered as well as introducing
some new ways to use the SMDI support which are required to avoid the bugs with
grabbing the wrong message off of the queue.
This code introduces a new interface to SMDI, with two dialplan functions. First,
you get an SMDI message in the dialplan using SMDI_MSG_RETRIEVE() and then you access
details in the message using the SMDI_MSG() function. A side benefit of this is that
it now supports more than just chan_zap.
For example, with this implementation, you can have some FXO lines being terminated
on a SIP gateway, but the SMDI link in Asterisk.
Another issue with the current implementation is that it is quite common that the
station ID that comes in on the SMDI link is not necessarily the same as the Asterisk
voicemail box. There are now additional directives in the smdi.conf configuration
file which let you map SMDI station IDs to Asterisk voicemail boxes.
Yet another issue with the current SMDI support was related to MWI reporting over
the SMDI link. The current code could only report a MWI change when the change
was made by someone calling into voicemail. If the change was made by some other
entity (such as with IMAP storage, or with a web interface of some kind), then the
MWI change would never be sent. The SMDI module can now poll for MWI changes if
configured to do so.
This work was inspired by and primarily done for the University of Pennsylvania.
(also related to issue #9260)
........
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@104120 f38db490-d61c-443f-a65b-d21fe96a405b
2008-02-26 00:31:40 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
[mailboxes]
|
|
|
|
|
; This section configures parameters related to MWI handling for the SMDI link.
|
|
|
|
|
|
|
|
|
|
; This option configures the polling interval used to check to see if the
|
|
|
|
|
; mailboxes have any new messages. This option is specified in seconds.
|
|
|
|
|
; The default value is 10 seconds.
|
|
|
|
|
;
|
|
|
|
|
;pollinginterval=10
|
|
|
|
|
|
|
|
|
|
; Every other entry in this section of the configuration file is interpreted as
|
|
|
|
|
; a mapping between the mailbox ID on the SMDI link, and the local Asterisk
|
|
|
|
|
; mailbox name. In many cases, they are the same thing, but they still must be
|
|
|
|
|
; listed here so that this module knows which mailboxes it needs to pay
|
|
|
|
|
; attention to.
|
|
|
|
|
;
|
|
|
|
|
; Syntax:
|
|
|
|
|
; <SMDI mailbox ID>=<Asterisk Mailbox Name>[@Asterisk Voicemail Context]
|
|
|
|
|
;
|
|
|
|
|
; If no Asterisk voicemail context is specified, "default" will be assumed.
|
|
|
|
|
;
|
|
|
|
|
; Before specifying mailboxes, you must specify an SMDI interface. All mailbox
|
|
|
|
|
; definitions that follow will correspond to that SMDI interface. If you specify
|
|
|
|
|
; another interface, then all definitions following that will correspond to the
|
|
|
|
|
; new interface.
|
|
|
|
|
;
|
|
|
|
|
;smdiport=/dev/ttyS0
|
|
|
|
|
;2565551234=1234@vmcontext1
|
|
|
|
|
;2565555678=5678@vmcontext2
|
|
|
|
|
;smdiport=/dev/ttyS1
|
|
|
|
|
;2565559999=9999
|