FreePBX
  1. FreePBX
  2. FREEPBX-1516

Allow substitution of 11 for * at start of a feature code

    Details

    • Type: Feature Requests Feature Requests
    • Status: Open (View Workflow)
    • Resolution: Unresolved
    • Affects Version/s: HEAD
    • Fix Version/s: None
    • Component/s: Feature Code Admin
    • Labels:
      None
    • Backend Engine:
      All

      Description

      Traditional telephone companies have long allowed customers to dial 11xx rather than *xx on most feature codes
      - originally this was put in place for rotary dial phones that didn't have * on the dial. But with VoIP, there is another use
      - to bypass built-in feature codes in some adapters. For example, in the Sipura/Linksys adapters, *70 means cancel call waiting for the next call only, whereas in FreePBX it is used to enable call waiting. If there were a checkbox on the page that would simply allow the use of 11xx in addition to *xx, then Sipura adapter users could be instructed to dial 11xx to turn on call waiting (after which *70 on their adapter should work as expected).

      So my suggestion is, put a checkbox near the bottom of the Feature codes pages that says:

      [] Allow user to replace * with 11 at start of feature codes.

      And if that box is checked, make it so that either code will manipulate the feature.

      I do realize that as a stopgap you can set up a custom extension (example, make a custom extension 1170 and put Local/*70@from-internal in the Dial field) but it would be rather cumbersome to do that for all the feature codes.

        Activity

        Hide
        Philippe Lindheimer added a comment -

        moving to 2.3

        of course you could always disable the feature codes in the various ata devices since they are notorious for creating problems and confusion... Or redefine all the feature codes to *1XX so that ata users don't conflict with their typical *XX (and the set the digitimap in the ata to handle *1XX.)

        Lastly
        - if you want a slightly more general workaround, you can add the follwoing in the extension_custom.conf (or some variant to be more restrictive then XX):

        exten => _11XX,1,Goto(from-internal,*${EXTEN:2),1)
        
        Show
        Philippe Lindheimer added a comment - moving to 2.3 of course you could always disable the feature codes in the various ata devices since they are notorious for creating problems and confusion... Or redefine all the feature codes to *1XX so that ata users don't conflict with their typical *XX (and the set the digitimap in the ata to handle *1XX.) Lastly - if you want a slightly more general workaround, you can add the follwoing in the extension_custom.conf (or some variant to be more restrictive then XX): exten => _11XX,1,Goto(from-internal,*${EXTEN:2),1)
        Hide
        wild goose added a comment -

        Um,

        exten => _11XX,1,Goto(from-internal,*${EXTEN:2},1)
        

        Works better.

        (I know it's hard to tell the difference between a ) and a } on a CRT
        - that has bitten me a few times too!)

        Thanks much for the suggestion, works great (once I fixed the closing brace).

        Show
        wild goose added a comment - Um, exten => _11XX,1,Goto(from-internal,*${EXTEN:2},1) Works better. (I know it's hard to tell the difference between a ) and a } on a CRT - that has bitten me a few times too!) Thanks much for the suggestion, works great (once I fixed the closing brace).
        Hide
        anonymous added a comment -

        Milestone 2.3 deleted

        Show
        anonymous added a comment - Milestone 2.3 deleted

          People

          • Assignee:
            Unassigned
            Reporter:
            wild goose
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development