No feature codes on new build.

› VitalPBX Community Support › General Discussion › No feature codes on new build.

Up
0
Down
  • Post
    • February 18, 2019 at 7:27 am
    Up
    0
    Down
    tonywhelan
    Participant

    I have started a fresh build of VitalPBX and created several extensions to test the basic build. I cannot get ANY of the Feature Codes to work. The extensions are set to the default “all” COS.

    I tried creating a new Feature Code Category with all feature codes included, and created a new COS linked to that, but it made no difference.

    I would have thought the default “all” COS would allow these extensions to access all feature codes?

    0
Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • Replies
    • February 18, 2019 at 2:18 pm
    Up
    0
    Down
    Rodrigo Cuadra
    Keymaster
    NI

    The “COS ALL” service class allows everything in VitalPBX, your problem must be different.

    0
    • February 18, 2019 at 2:25 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    May you share a call log when you call a feature code?

    0
    • February 18, 2019 at 4:45 pm
    Up
    0
    Down
    tonywhelan
    Participant

    Hi, attached is an extract of log when I called x23 from x21, pressed *2 , nothing happened, pressed *70, nothing happened, then I hung up.

    Tony

    0
    • February 18, 2019 at 4:46 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    What kind of phone are you using (Brand and Model)?

    0
    • February 18, 2019 at 4:50 pm
    Up
    0
    Down
    tonywhelan
    Participant

    For this test I am calling a Yealink T23G.

    0
    • February 18, 2019 at 5:01 pm
    Up
    0
    Down
    tonywhelan
    Participant

    I also tried calling a LinPhone softphone, same problem.

     

    0
    • February 18, 2019 at 5:25 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    Do the following from Linux console:

    • go to ombutel folder:  cd /usr/share/ombutel
    • Execute the following command: php scripts/dump_asterisk_conf
    • Reload asterisk: asterisk -rx”core reload”

    Let me know if any error appears after executing the command “dump_asterisk_conf“

    0
    • February 18, 2019 at 5:34 pm
    Up
    0
    Down
    tonywhelan
    Participant

    There was no error message after executing php scripts/dump_asterisk_conf

     

    0
    • February 18, 2019 at 5:41 pm
    Up
    0
    Down
    tonywhelan
    Participant

    I also tried calling an old Aastra phone, same problem

     

    0
    • February 18, 2019 at 5:53 pm
    Up
    0
    Down
    tonywhelan
    Participant

    I notice that after I did that last command, the log file viewer for “full” shows nothing, even though I can see it is a 190KB file. I had noticed this previously. Seems to be a file permissions issue.

    [root@vitalpbx asterisk]# ls -l
    total 2796
    drwxr-xr-x. 2 asterisk asterisk 51 Feb 19 04:35 cdr-csv
    drwxr-xr-x. 2 asterisk asterisk 47 Feb 19 04:35 cdr-custom
    -rw-r—– 1 asterisk asterisk 14297 Feb 19 04:51 fail2ban
    -rw-r–r–. 1 asterisk asterisk 149563 Feb 19 04:33 fail2ban-20190219
    -rw-r—– 1 asterisk asterisk 190890 Feb 19 04:49 full
    -rw-r–r– 1 asterisk asterisk 2486335 Feb 19 04:35 full-20190219
    -rw-r—– 1 asterisk asterisk 120 Feb 19 04:44 queue_log
    -rw-r–r– 1 asterisk asterisk 2032 Feb 19 04:35 queue_log-20190219

    0
    • February 18, 2019 at 6:19 pm
    Up
    0
    Down
    tonywhelan
    Participant

    I should mention that the same handset (Yealink T23G) does work OK for all call features when connected to my “live” VitalPBX machine.

     

    0
    • February 18, 2019 at 10:02 pm
    Up
    0
    Down
    tonywhelan
    Participant

    Update: I just built another fresh install of VitalPBX on a spare SSD. Set the IP address, created 3 extensions, changed nothing else.

    Tested transfer feature codes by dialling an extension, answering that extension, and pressing *2. Nothing happens. None of the three extensions can activate the *2 warm transfer, or #1 cold transfer, to another extension.

     

     

    0
    • February 19, 2019 at 5:33 am
    Up
    0
    Down
    tonywhelan
    Participant

    On my new test build, looking at file /etc/asterisk/ombutel/extensions__50-1-features.conf, there are no entries for *0, *2, *3, *4 and #1. Yet these entries exist in that file on my production machine.

    0
    • February 19, 2019 at 2:22 pm
    Up
    0
    Down
    Jose Miguel Rivera
    Keymaster
    NI

    Check if you have enabled the transfer features on the dial profiles assigned to your phones. check the picture attached

    0
    • February 19, 2019 at 3:11 pm
    Up
    0
    Down
    tonywhelan
    Participant

    I was certain that I had enabled that previously, but apparently I had not.

    Transfers are working ok now. Thank you for your patience.

     

    0
Viewing 15 replies - 1 through 15 (of 16 total)
1 2

Tagged: 

  • You must be logged in to reply to this topic.