Ticket #1523 (closed Patches: wontfix)

Opened 5 years ago

Last modified 4 years ago

Per Extensions trunk password

Reported by: francesco_r Assigned to:
Priority: minor Milestone: 2.5
Component: Core Version:
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

I have created a little application that many of my clients requested to me: block the single extension with a password for the external numbers (trunks). Perhaps someone want to improve it or write a separate application, i have no practice with php. In the modified macro-dialout-trunk i have added a section to not block the emergency numbers that start with 11. I know that in USA there is 911 but here in Italy there are multiple numbers for different services and start all with 11 (112, 113, 118, etc) so is necessary to adapt for the own nation.

I have attached the txt file with the parts to add to extensions_custom.conf and the macro-dialout-trunk modified.

Regards, Francesco Romano

Attachments

password_trunks.txt (4.8 kB) - added by francesco_r on 12/11/06 03:53:50.

Change History

12/11/06 03:53:50 changed by francesco_r

  • attachment password_trunks.txt added.

12/11/06 10:56:08 changed by p_lindheimer

I'll make a suggestion (actually - call it education). Don't bother modifying extensions.conf, just write any such modified context's (macros) directly in extensions_custom.conf. Any time you redefine a module in extension_custom.conf, it will use it INSTEAD of what is in extensions.conf - then you don't get messed up when you upgrade freepbx. (although - rewriting a core macro like this always requires careful scrutiny when you upgrade, since there may be changes to it that you need to adapt to.)

12/11/06 13:33:00 changed by naftali5

This can easily be done using #1447 and allowing only certain routes to specific extensions, and putting password/pinsets on them.

12/11/06 16:04:21 changed by francesco_r

I saw your module #1447, it's very interesting, perhaps the most big thing that miss from Freepbx, the management of custom contexts. But this is different and more simple to implement, users can easily activate or deactivate their own trunk password directly from the phone. And changing in the dialplan Authenticate with VMAuthenticate (http://www.voip-info.org/wiki/view/Asterisk+cmd+VMAuthenticate or http://www.voip-info.org/wiki/view/Asterisk+authenticate+using+voicemail+passwords) you can use the same password of the voicemail.

12/11/06 16:08:18 changed by naftali5

right and convince your secretary to type a password to call home!

01/08/07 13:46:44 changed by

  • milestone deleted.

Milestone 2.2 deleted

01/08/07 14:05:07 changed by vgster

  • milestone set to 2.2.

11/13/07 12:53:50 changed by p_lindheimer

  • version deleted.
  • confirmation set to Confirmed.
  • engine_version changed.
  • svn_rev changed.
  • milestone changed from 2.2 to 3.0.

07/06/08 14:25:35 changed by mbrevda

Ping: any updates here?

07/08/08 01:31:49 changed by p_lindheimer

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

I'm closing this because it is not in a patch format and very old. If you want to add a patch so we can see and evaluate this can easily be reopened.