Call Park stopped working

› VitalPBX Community Support › General Discussion › Call Park stopped working

Up
0
Down
  • Post
    • July 17, 2019 at 2:06 am
    Up
    0
    Down
    Gary
    Participant

    Call parking has stopped working, I have call park buttons on Yealink phones direct to parking slots 701-704 none of them work on all phones, I also can not park to pilot number 700, I get a warning in command line. if I check gui default parking is correct with 700 & 4 slots, it has always worked just suddenly stopped

    WARNING[17347][C-00000030]: pbx.c:2922 pbx_extension_helper: No application ‘ParkedCall’ for extension (sub-parking-lots, s, 7)

    VitalPBX 2.3.4-2 
    Asterisk 16.4.0-1 
    DAHDI 2.11.1-7

     

    0
Viewing 15 replies - 1 through 15 (of 15 total)
  • Replies
    • July 18, 2019 at 4:27 pm
    Up
    0
    Down
    Gary
    Participant

    Is there anything I can do to get Parking back, I have tried making a new group 750 with 2 slots but that also does not work. I get thge same type error message.

     

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

    May you go to the Asterisk CLI and execute the following command:

    module reload res_parking.so

    Post any error if you get some!!

    0
    • July 18, 2019 at 4:34 pm
    Up
    0
    Down
    Gary
    Participant

    [root@vulpbx101 ~]# module reload res_parking.so
    -bash: module: command not found
    [root@vulpbx101 ~]#

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

    First, you must get into the Asterisk CLI

    rasterisk -vvvvvvvvvvvvvv
    module reload res_parking.so
    0
    • July 18, 2019 at 4:38 pm
    Up
    0
    Down
    Gary
    Participant

    vulpbx101*CLI> module reload res_parking.so
    The module ‘res_parking.so’ was not properly initialized. Before reloading the module, you must run “module load res_parking.so” and fix whatever is preventing the module from being initialized.
    vulpbx101*CLI>

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

    May you try this command on Asterisk CLI

    module load res_parking.so
    0
    • July 18, 2019 at 4:42 pm
    Up
    0
    Down
    Gary
    Participant

    Connected to Asterisk 16.4.0 currently running on vulpbx101 (pid = 2815)
    vulpbx101*CLI> module load res_parking.so
    Unable to load module res_parking.so
    Command ‘module load res_parking.so’ failed.
    [2019-07-18 12:41:30] ERROR[17328]: config_options.c:798 aco_process_var: Error parsing parkedplay=parked at line 19 of /etc/asterisk/ombutel/res_parking__50-1-extensions.conf
    [2019-07-18 12:41:30] ERROR[17328]: config_options.c:572 process_category: In res_parking.conf: Processing options for parking-1 failed
    vulpbx101*CLI>

    0
    • July 18, 2019 at 4:43 pm
    Up
    0
    Down
    Gary
    Participant

    [parking-1]
    parkext=>700
    context=>parking-1-parkedcalls
    comebackcontext=parking-1-parkedcallstimeout
    parkpos=>701-704
    parkedmusicclass=moh2
    parkingtime=>90
    comebacktoorigin=yes
    comebackdialtime=20
    parkedplay=parked
    parkedcalltransfers=no
    parkedcallreparking=no
    parkedcallhangup=no
    findslot=>first
    parkext_exclusive=yes

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

    Try changing the “Courtesy Tone” field to “Caller” value as shown in the attached picture

    0
    • July 18, 2019 at 4:49 pm
    Up
    0
    Down
    Gary
    Participant

    changed to Caller but call is still terminated, also when I created a new group that was set to caller and it did not work.

    [parking-1]
    parkext=>700
    context=>parking-1-parkedcalls
    comebackcontext=parking-1-parkedcallstimeout
    parkpos=>701-704
    parkedmusicclass=moh2
    parkingtime=>90
    comebacktoorigin=yes
    comebackdialtime=20
    parkedplay=caller
    parkedcalltransfers=no
    parkedcallreparking=no
    parkedcallhangup=no
    findslot=>first
    parkext_exclusive=yes

    [parking-3]
    parkext=>680
    context=>parking-3-parkedcalls
    comebackcontext=parking-3-parkedcallstimeout
    parkpos=>681-682
    parkedmusicclass=default
    parkingtime=>45
    comebacktoorigin=yes
    comebackdialtime=30
    parkedplay=caller
    parkedcalltransfers=no
    parkedcallreparking=no
    parkedcallhangup=no
    findslot=>next
    parkext_exclusive=yes

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

    Check this link: https://issues.asterisk.org/jira/browse/ASTERISK-24179

    Looks like the “parked” value is not valid, it has been replaced by “callee”, but the documentation still says that the “parked” value is allowed.

    0
    • July 18, 2019 at 4:53 pm
    Up
    0
    Down
    Gary
    Participant

    I did a module load res_parking.so again and it loaded and is working.

    vulpbx101*CLI> module load res_parking.so
    Loaded res_parking.so
    [2019-07-18 12:51:18] NOTICE[19066]: res_parking.c:1090 verify_default_parking_lot: Adding default profile to res_parking
    == Registered application ‘Park’
    == Registered application ‘ParkedCall’
    == Registered application ‘ParkAndAnnounce’
    == Manager registered action Parkinglots
    == Manager registered action ParkedCalls
    == Manager registered action Park
    == Registered custom function ‘PARK_GET_CHANNEL’
    Loaded res_parking.so => (Call Parking Resource)

    Not sure what happened but all seems good.

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

    We will change the “parked” option to “callee” in the next version, for now, you must use only “caller” or “both” options

    0
    • July 18, 2019 at 4:59 pm
    Up
    0
    Down
    Gary
    Participant

    Thanks for your help.

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

    You’re welcome

    0
Viewing 15 replies - 1 through 15 (of 15 total)
  • You must be logged in to reply to this topic.