Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. DND settings not making it to astmanager

DND settings not making it to astmanager

Scheduled Pinned Locked Moved Support
2 Posts 1 Posters 62 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    A
    andybonyx
    wrote on last edited by
    #1

    DND settings aren't making it to astmanager.
    Watching asterisk manager for the events, logged into fop2 via the web interface, and have the daemon running in debug foreground to see what I get.
    I login as an extension number, and get the usual flash display. I can change the drop-down to DND, and in the fop2 daemon I see the error:

    Use of uninitialized value in pattern match (m//) at script/fop2_server.pl line 9302.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 9360.
    

    Logged, and no events make it to the asterisk manager API.

    Connection to AMI from fop2 works fine, I can see the active session.
    Snippets of the config as follows:

    [general]
    ; AMI definitions
    manager_host=localhost
    manager_port=5038
    manager_user=admin
    manager_secret=blahblah
    
    user=3228:1234:all
    [EXTENSION/3228]
    type=extension
    label=3228-ACCTS-REP
    context=from-internal
    

    Can anyone spot what the perl/patten match error in fop2_server.pl is please? Nic could you advise what those lines are in the raw uncompiled code that would help where we've gone wrong here please?

    Regards,
    Andy

    1 Reply Last reply
    0
    • A
      A
      andybonyx
      wrote on last edited by
      #2

      Sorry, I have found the problem!
      I didn't have a valid extension=3228 line in the [EXTENSION/3228] section. Therefore it didn't have a full list of buttons along the top, and since it was classed as 'not a valid extension' it wasn't writing values to the asterisk database.

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups