How To Add A # Pound Key To Outgoing Number

Discussion in 'General' started by ismed, Dec 14, 2009.

  1. ismed

    Joined:
    Oct 1, 2009
    Messages:
    120
    Likes Received:
    0
    Dear Experts,

    I want to add a # key automatically after I dial a PSTN outgoing number.
    Can I do it in elastix?

    Awaiting your respond soon and thank you very much.

    Best regards,
    Ismed
     
  2. danardf

    Joined:
    Dec 3, 2007
    Messages:
    8,069
    Likes Received:
    12
    Re:How To Add A # Pound Key For Outgoing Number

    Hi ismed.

    I don't know if that could be well, but maybe add .# or .+# into the trunk / dial rules ?!

    Regards.
     
  3. ismed

    Joined:
    Oct 1, 2009
    Messages:
    120
    Likes Received:
    0
    Thanks a lot frank,
    I tried your suggestion but it seems that we can only add the "+" before the wildcard, and the system will refuse to work if we put "+" after the wildcard. It will work for instance like 001+. and doesn't work if we put like .+#

    I also already tried to add it manually in the config file like below :
    original -> exten => _01208.,n,Macro(dialout-trunk,4,${EXTEN:3},,)
    modified -> exten => _01208.,n,Macro(dialout-trunk,4,${EXTEN:3}#,,)

    But that "#" key will always gone when I update the trunk or outbound route in the freepbx.

    Any other clue to this problem?

    Awaiting your respond soon and thank you.

    Best regards,
    Ismed
     
  4. danardf

    Joined:
    Dec 3, 2007
    Messages:
    8,069
    Likes Received:
    12
    It's logic. ;)

    Maybe you don't use the good file!
    Maybe you must copy the original context to extensions_custom.conf or extensions_override_freepbx.conf but never write on extensions_additional.conf.

    If you look the bottom line into the file:
    Code:
    ;--------------------------------------------------------------------------------;
    ; Do NOT edit this file as it is auto-generated by FreePBX. All modifications to ;
    ; this file must be done via the web gui. There are alternative files to make    ;
    ; custom modifications, details at: http://freepbx.org/configuration_files       ;
    ;--------------------------------------------------------------------------------;
    ;
    Regards
     
  5. ismed

    Joined:
    Oct 1, 2009
    Messages:
    120
    Likes Received:
    0
    Thanks again frank,
    I do your suggestion and it is working. But I am still confuse with my context "include => outrt-005-AKSES-custom", I cannot find where this "custom" context written? I was worrying to break the relation of context when I move a context to other file, will the relation context break when we move it?

    Ismed
     
  6. danardf

    Joined:
    Dec 3, 2007
    Messages:
    8,069
    Likes Received:
    12
    2 files where you can make some modifications :
    • - extensions_custom.conf
      - extensions_override_freepbx.conf

    The first is your own personal context, and the second you can copy a context from extension_addition.conf and modify it. Like that this same context will be replaced even if it's loaded before into extension_addition.conf
     
  7. danardf

    Joined:
    Dec 3, 2007
    Messages:
    8,069
    Likes Received:
    12
    Code:
    include => outrt-005-AKSES-custom
    The case here, it's at you to make this context like that.
    [outrt-005-AKSES-custom]

    You can insert this context here : extensions_custom.conf

    outrt-005-AKSES-custom event if this context don't exist, it's not important....
     
  8. voipmart

    Joined:
    Dec 15, 2009
    Messages:
    11
    Likes Received:
    0
    Dear ismed !

    Actually, We always use "#" to complete the outgoing call on almost of IP Phone which supported.
    I think we no need to config this one.

    Regards,

    Steven.
     
  9. danardf

    Joined:
    Dec 3, 2007
    Messages:
    8,069
    Likes Received:
    12
    Of course, there's not useful to end the dial.
    For example, like from Alcatel 4400 or OXE, we used the "#" for RNIS config.
    Dial by bloc or overlap.
    Maybe that now the # is obsolete. ;)
     

Share This Page