[asterisk-bugs] [Asterisk 0009260]: [Patch] SMDI features

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Feb 25 18:17:44 CST 2008


The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=9260 
====================================================================== 
Reported By:                ltd
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   9260
Category:                   Core/General
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     resolved
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 58841 
Disclaimer on File?:        Yes 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             03-12-2007 18:37 CDT
Last Modified:              02-25-2008 18:17 CST
====================================================================== 
Summary:                    [Patch] SMDI features
Description: 
I found that using the built in SMDI code in production, there were a few
problems:

1) When two calls come in at roughly the same time, the SMDI messages
generally come in the right order but the calls don't necessarily hit the
zap channels in that same order, resulting in incorrect SMDI messages being
popped off the queue for both calls. In my setup I coordinated with my
telco so that the zap channels I plugged my lines into corresponded to the
message desk terminal number field of incoming SMDI MD messages. As such
I've included code that matches the Zap channel to the terminal number when
you choose to enable it using smdimatchterm=yes in zapata.conf. This solved
the issue for me.

2) My voicemail extensions were four digits but the telco switch requires
that SMDI messages are in FNN format. I added an mwiprefix option to the
smdi config so that when I send MWI operate and RMV messages, the prefix is
prepended to the mailbox extension and everything works nicely.

====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-25-08 18:17  russell        Status                   assigned => resolved
02-25-08 18:17  russell        Resolution               open => fixed       
======================================================================




More information about the asterisk-bugs mailing list