asterisk

Commit Graph

Author	SHA1	Message	Date
Russell Bryant	3a8756c9b4	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: https://origsvn.digium.com/svn/asterisk/trunk@104120 65c4cc65-6c06-0410-ace0-fbb531ad65f3	18 years ago
Tilghman Lesher	091e1aed8d	Merged revisions 42716 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.2 ........ r42716 \| tilghman \| 2006-09-11 11:39:06 -0500 (Mon, 11 Sep 2006) \| 2 lines Spelling/grammar fixes (Issue 7929) ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@42717 65c4cc65-6c06-0410-ace0-fbb531ad65f3	19 years ago
Matthew Fredrickson	af07dc8883	Add smdi support for asterisk (see doc/smdi.txt for config info) (#5945 ) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@9423 65c4cc65-6c06-0410-ace0-fbb531ad65f3	20 years ago

Author

SHA1

Message

Date

Russell Bryant

3a8756c9b4

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: https://origsvn.digium.com/svn/asterisk/trunk@104120 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Tilghman Lesher

091e1aed8d

Merged revisions 42716 via svnmerge from

https://origsvn.digium.com/svn/asterisk/branches/1.2

........
r42716 | tilghman | 2006-09-11 11:39:06 -0500 (Mon, 11 Sep 2006) | 2 lines

Spelling/grammar fixes (Issue 7929)

........


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@42717 65c4cc65-6c06-0410-ace0-fbb531ad65f3

Matthew Fredrickson

af07dc8883

Add smdi support for asterisk (see doc/smdi.txt for config info) (#5945 )

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@9423 65c4cc65-6c06-0410-ace0-fbb531ad65f3

3 Commits (e72038d2c955d33480573d546db02e14f873a93b)