Ticket #2134 (reopened Feature Requests)

Opened 6 years ago

Last modified 4 years ago

Add vm mailbox option to DISA

Reported by: mbrevda Assigned to:
Priority: minor Milestone: Undetermined
Component: DISA Version:
Keywords: Cc:
Confirmation: Confirmed Distro:
Backend Engine: Asterisk 1.4.x Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description (Last modified by mbrevda)

There is an option avalible to attach a vm mailbox to disa so that if there is new vm, the caller to disa will get a stutter tone.

"DISA(<numeric passcode>[|<context>[|<cid>[|mailbox[|options]]]]) or\n"
"DISA(<filename>[||||options])\n"
<mailbox[@context]> will cause a stutter-dialtone (indication \"dialrecall\")\n"
"to be used, if the specified mailbox contains any new messages.\n" 

Taken from: http://svn.digium.com/svn/asterisk/trunk/apps/app_disa.c

Change History

07/22/07 13:14:20 changed by mbrevda

  • description changed.

07/22/07 13:15:47 changed by mbrevda

  • engine changed from Asterisk 1.2.x to Asterisk 1.4.x.

07/22/07 13:39:57 changed by p_lindheimer

is this in the mainstream 1.4 versions or trunk only?

07/22/07 23:35:19 changed by mbrevda

From the source of 1.4.7.1:

static char *descrip =

DISA(<numeric passcode>[|<context>]) or DISA(<filename>)The DISA, Direct Inward System Access, application allows someone from outside the telephone switch (PBX) to obtain an internal system dialtone and to place calls from it as if they were placing a call from within the switch.

DISA plays a dialtone. The user enters their numeric passcode, followed by the pound sign (#). If the passcode is correct, the user is then given system dialtone on which a call may be placed. Obviously, this type of access has SERIOUS security implications, and GREAT care must betaken NOT to compromise your security. There is a possibility of accessing DISA without password. Simply exchange your password with no-password. Example: exten => s,1,DISA(no-password|local)Be aware that using this compromises the security of your PBX.The arguments to this application (in extensions.conf) allow eitherspecification of a single global passcode (that everyone uses), or individual passcodes contained in a file. It also allows specification of the context on which the user will be dialing. If no context is specified, the DISA application defaults the context to disa.Presumably a normal system will have a special context set up for DISA use with some or a lot of restrictions.

The file that contains the passcodes (if used) allows specificationof either just a passcode (defaulting to the disa context, orpasscode|context on each line of the file. The file may contain blank lines, or comments starting with # or ;. In addition, the above arguments may have |new-callerid-string appended to them, tospecify a new (different) callerid to be used for this call, forexample: numeric-passcode|context|My Phone <(234) 123-4567> or full-pathname-of-passcode-file|My Phone <(234) 123-4567>. Lastbut not least, |mailbox[@context] may be appended, which will causea stutter-dialtone (indication dialrecall) to be used, if thespecified mailbox contains any new messages, for example:numeric-passcode|context1234 (w/a changing callerid). Note that in the case of specifying the numeric-passcode, the context must be specified if the callerid is specified also.

If login is successful, the application looks up the dialed number in the specified (or default) context, and executes it if found.If the user enters an invalid extension and extension i (invalid) exists in the context, it will be used. Also, if you set the 5th argument to 'NOANSWER', the DISA application will not answer initially.

07/13/08 11:32:00 changed by mbrevda

  • confirmation set to Unreviewed.

hmm, so if we set the callerid to one extension and set the mailbox to another, things will probably break. Instead there should be a dropdown box that with a list of extensions and you can pick either an extension or enter a custom callerid

07/13/08 20:23:05 changed by p_lindheimer

unless it's not documented, this does not look like a 1.4 function but trunk (or 1.6) only. I think it is a bit premature to implement this in the mainstream code base if that is the case.

07/14/08 02:30:37 changed by mbrevda

This feature is actually quite old, it was commited in October of 2004 in response to a bug filed in August of that year

07/14/08 11:15:21 changed by p_lindheimer

  • confirmation changed from Unreviewed to Confirmed.
  • milestone changed from 4.0 to 2.5.

fair enough (although those links don't work). Feel free to add the new paramter. While you are at it (this is really another feature request), it would be nice to play with the DISA diaplan and see if something could be added to it. It would be nice if the dialplan could be modified so that upon a successful call going through and being hungup at the remote end, it would return and allow another call to be made.

07/14/08 11:22:54 changed by mbrevda

07/24/08 23:49:22 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to wontfix.

closing as won't fix, this requires the use of the disa file which was just removed because it produces a sub-standard disa functionality and to improve the repeat call option, both of which I think are much more important than this.

07/25/08 03:07:35 changed by mbrevda

  • status changed from closed to reopened.
  • resolution deleted.
  • milestone changed from 2.5 to 3.0.

hmm, it seems to be possible to do the without a disa file

DISA(<numeric passcode>[,<context>[,<cid>[,mailbox[,options]]]])

08/22/09 20:13:36 changed by p_lindheimer

  • version deleted.
  • milestone changed from 2.6 to 2.7.