blistovmhz

Member

Last active 2 years ago

  1. 2 years ago
    Mon Nov 21 21:21:47 2016

    Okay, I think there's actually more to it.
    Time conditions by default in FPBX, for some reason are issued a feature code of *_ _ _ (three digits), but it doesn't seem to care that this feature code will conflict with the direct dial to a given extensions voice mail. So I'd modified the feature codes for each Time Condition, to *1270 through *1274. Dialing these, overrides the current override state. Also, FOP2 Call Flow plugin does correctly detect the current state, but cannot set it.
    I enabled more debugging and found that FOP2 is trying to send the original feature code (*277) instead of the manually overridden feature code (*1270). When you click it to flip the override, it says it's enabled, but then a few second later of course detects that it is not in fact, overridden.
    Log:
    set call flow origen 5, destino 7~DAY, exten GENERAL, final exten *277, slot 7, value DAY
    127.0.0.1 -> Exten: *277
    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: 356

    127.0.0.1 <- Response: Error
    127.0.0.1 <- ActionID: 356
    127.0.0.1 <- Message: Extension does not exist.

    So all we really need for this to work correctly (I think) is for FOP to check the actual feature codes associated with each Time Condition.
    Any chance this could be done. It was the only reason I bought the plugin :P

  2. 3 years ago
    Thu Mar 24 17:48:07 2016
    blistovmhz started the conversation CallFlow/TimeConditions status/toggle.

    Is there any way to display time condition status in fop2? The CallFlow plugin can toggle TC's, but does not show their current status. I feel like the plugin should show the current status of a TC, and toggling it should simply override the current mode.
    Currently, you can toggle the override state, but that is only meaningful to someone who knows what the current state SHOULD be.

    Showing the current status would be useful in that our receptionist could override the "businesshours" TC to allow calls to come in earlier or later than regular business hours. As it stands now, if she toggles the override in FOP, that override stays toggled even after the TC changes, so if she overrides the TC to allow calls before business hours, when the TC switches at 8 am, the toggle is now inverted and incoming calls would still be directed to the afterhours ivr.

  3. Wed Mar 23 19:35:47 2016

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

  4. Wed Mar 23 19:30:11 2016

    [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?

  5. Wed Mar 23 16:17:47 2016
    blistovmhz started the conversation CallFlow plugin not creating custom-fop2-callflow.

    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.

  6. Mon Mar 14 19:35:14 2016
    blistovmhz joined the forum.