CallFlow plugin not creating custom-fop2-callflow

  1. 8 years ago
    Edited 8 years ago by blistovmhz

    FOP2 2.30.04. Installed Callflow plugin, restarted fop2 and reloaded asterisk. Call Flow pane shows up and populates buttons for all of my time conditions as well as callflows, but none of them work.
    When I click on any of them, they do toggle, but then revert a few seconds later.
    Digging into logs, when I hit a button for a call flow I get:

    set call flow origen 6, destino 0~NIGHT, exten GENERAL, final exten *270, slot 0, value NIGHT
    127.0.0.1 -> Exten: *270
    127.0.0.1 -> Action: Originate
    127.0.0.1 -> Channel: Local/s@custom-fop2-callflow
    127.0.0.1 -> Priority: 1
    127.0.0.1 -> Context: from-internal
    127.0.0.1 -> ActionID: 14461

    pong pong call flow!

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: DAYNIGHT
    127.0.0.1 -> Key: C0
    127.0.0.1 -> ActionID: 14462

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: TC
    127.0.0.1 -> Key: 0
    127.0.0.1 -> ActionID: 14463

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: DAYNIGHT
    127.0.0.1 -> Key: C1
    127.0.0.1 -> ActionID: 14464

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: TC
    127.0.0.1 -> Key: 1
    127.0.0.1 -> ActionID: 14465

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: DAYNIGHT
    127.0.0.1 -> Key: C2
    127.0.0.1 -> ActionID: 14466

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: TC
    127.0.0.1 -> Key: 2
    127.0.0.1 -> ActionID: 14467

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: DAYNIGHT
    127.0.0.1 -> Key: C3
    127.0.0.1 -> ActionID: 14468

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: TC
    127.0.0.1 -> Key: 3
    127.0.0.1 -> ActionID: 14469

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: DAYNIGHT
    127.0.0.1 -> Key: C4
    127.0.0.1 -> ActionID: 14470

    127.0.0.1 -> Action: DBGet
    127.0.0.1 -> Family: TC
    127.0.0.1 -> Key: 4
    127.0.0.1 -> ActionID: 14471

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: DAYNIGHT/C0
    127.0.0.1 -> Value: DAY
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: TC/0
    127.0.0.1 -> Value: ERROR
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: DAYNIGHT/C1
    127.0.0.1 -> Value: ERROR
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: TC/1
    127.0.0.1 -> Value:
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: DAYNIGHT/C2
    127.0.0.1 -> Value: ERROR
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: TC/2
    127.0.0.1 -> Value:
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: DAYNIGHT/C3
    127.0.0.1 -> Value: ERROR
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: TC/3
    127.0.0.1 -> Value:
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: DAYNIGHT/C4
    127.0.0.1 -> Value: ERROR
    127.0.0.1 -> Channel: SIP/220

    127.0.0.1 -> Action: UserEvent
    127.0.0.1 -> UserEvent: GETVAR
    127.0.0.1 -> Family: TC/4
    127.0.0.1 -> Value:
    127.0.0.1 -> Channel: SIP/220

    Discussed this with support, and all we've come up with is that the custom_fop2_callflow is not being generated but have no idea why. Back over to my asterisk/freepbx logs, I do not see any errors pertaining to the generation of the custom dialplans.
    Fop2 is configured to connect to AMI as 'admin', which has all permissions.
    When I check Asterisk dialplans for the custom_fop2_callflow, it does not exist.

    Anyone else run into this? I feel like I'm unlikely to get any further support from Fop guy. Been fighting with this for two weeks and the back and forth with support hasn't been going anywhere. I figure there must be a log, or a way to enable logging of the scripts run to generate the custom dialplans.

  2. admin

    23 Mar 2016 Administrator

    What permissions has the admin user? I suggest you to create a fop2 user in your manager_custom.conf file as suggested in the documentation, using the exact values as set in the documentation:

    http://www.fop2.com/docs/#ConfiguringtheServer

    Perhaps your "admin" user lacks the "config" permission, in any case, try with a special user with "all" permissions set.

    In any case, the context is super simple, is just a dummy context/location so you can use it as an originating local channel that does absolutely nothing:

    [custom-fop2-callflow]
    exten => s,1,Answer()
    exten => s,2,Wait(10)

    Best regards,

  3. [admin]
    secret = ********
    deny=0.0.0.0/0.0.0.0
    permit=127.0.0.1/255.255.255.0
    read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate,message
    write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate,message
    writetimeout = 5000

    That is the user I have fop2 configured to use. I've also setup a user called "fop2" with the permissions stated in the documentation linked. No change.
    When is the dialplan generated and is there any way I can run the config script manually to see what's failing?

  4. Oh, also, I can see in my logs that the fop2 user (or admin) is in fact connecting to AMI successfully.

  5. admin

    23 Mar 2016 Administrator

    The dialplan is created using AMI commands, but instead of smashing your head, you can very well add the context manually in any valid .conf file you might have. I already wrote the context in my previous reply..

    If you want to see the actual commands, then start fop2 server in debug mode:

    http://support.asternic.biz/?/selfhelp/view-article/how-to-debug-fop2/10

or Sign Up to reply!