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

D

dogatemycomputer

@dogatemycomputer
Unfollow Follow
About
Posts
5
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Labels are correct initially then change to old values
    D dogatemycomputer
    Support

    I need some time to test when I get back to the office but I suspect you are absolutely correct and that would explain why queue members update properly but queue members do not. It would also explain why the correct name shows up then is overwritten by the queue member.

    Thanks for your help Nicolas! Have a great day!


  • Labels are correct initially then change to old values
    D dogatemycomputer
    Support

    We are running:

    [root@proxy200 fop2]# ./fop2_server --version
    fop2_server version 2.26

    We are running FreePBX.

    What happens:

    • We login.
    • All the CORRECT button labels appear for all extensions.
    • The button labels refresh with incorrect values for some extensions (not all).

    What we expect:

    • The correct values will remain for all extensions.

    The test case below is for X3507 which should be labeled "Leslie CA".

    • The extension "Name" in FreePBX is correct (reads "Leslie CA")
    • Click TOOLS -> FOP2 BUTTONS -> Checked X3507 and the LABEL field is correct ("Leslie CA")
    • We have clicked TOOLS -> FOP2 BUTTONS -> REFRESH LABELS -> APPLY CHANGES
    • We have tried 3 separate browsers including Firefox, Chrome and IE
    • We have tried multiple logins to the FOP2 and all exhibit the same problem.
    • Checked voicemail.conf which shows "3507 => XXXX,Leslie CA,,,attach=no|saycid=no|envelope=no|delete=no" and the name is correct in the voicemail profile.
    • Executed /usr/local/fop2/autoconfig-buttons-freepbx.sh which reports the following which appears to be correct:
    [SIP/3507]
    type=extension
    extension=3507
    label=Leslie CA
    mailbox=3507@default
    context=from-internal
    queuecontext=from-queue
    extenvoicemail=*3507@default
    privacy=none
    rtmp=0
    queuechannel=Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3300600&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3300602&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3300603&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3300604&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3300605&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3300607&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500600&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500602&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500603&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500604&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500607&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500608&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500609&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500610&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500612&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500613&Local/3507@from-queue/n|Penalty=0|MemberName=Leslie CA|StateInterface=SIP/3507|Queue=3500614
    customastdb=CF/3507
    
    • also confirmed autoconfig-buttons-freepbx.sh contains: FOP2PLUGIN=1 and executed it again. (Note: The Conferences parse first which seems to be the correct behavior.)
    • Restarted Asterisk
    • Restarted the FOP2
    • Checked mysql:
    mysql> select exten, label from asterisk.fop2buttons where label like '%Leslie%' or exten=3507;
    +-------+-----------+
    | exten | label     |
    +-------+-----------+
    | 3507  | Leslie CA | 
    +-------+-----------+
    1 row in set (0.00 sec)
    
    mysql> 
    

    The answers I am looking for are:

    • What happens during the loading process where one label is shown then it is overwritten by another label?
    • Where is this secondary (incorrect) information coming from?
    • Why does one button update properly and another button update incorrectly?

    Any information you could provide would be appreciated.

    Thank you!


  • FOP2 stops updating on queue call..
    D dogatemycomputer
    Support

    We are running Asterisk 1.8.3.3 with whitelabel FOP2 2.2 on CentOS 5. I am trying to understand what is happening here.

    WHAT WORKS:
    If we dial the queue internally (for example.. dial 1000600.. it rings all the phones and the FOP2 continues to update perfectly).

    WHAT BREAKS:
    If we dial a queue from an IVR the FOP2 stops updating the agent information until we restart it. We can still..

    • add and remove agents from the queue
    • can see queue updates such as how many callers are waiting and their information
    • receive call audio alerts for callers entering/leaving the queue

    .. but from that point forward the agents will be listed as "inactive" or "restricted" and the FOP2 stops responding. In some cases all the queue extensions will continue to show a "ringing" symbol long after the call is answered. This happens from Firefox on linux, IE and Firefox on Windows.

    Here is a partial log below. I am not sure how much logging I should post but everything looks normal until the error below. I would guess this could be an Asterisk issue but even so why doesn't the FOP reconnect and update all the extensions automatically without restarting the service? If anyone has a suggestion I would appreciate it.

    *127.0.0.1 <- Event: Newexten
    127.0.0.1 <- Privilege: dialplan,all
    127.0.0.1 <- Channel: Local/3302@from-queue-0f7e;2
    127.0.0.1 <- Context: macro-dial-one
    127.0.0.1 <- Extension: s
    127.0.0.1 <- Priority: 5
    127.0.0.1 <- Application: GotoIf
    127.0.0.1 <- AppData: 1?skip1
    127.0.0.1 <- Uniqueid: 1306254362.59707
    127.0.0.1 <- Server: 0

    ** CLEAN SOCKET connection lost removing socket IO::Socket::INET=GLOB(0xf67c1f4)
    ** CLEAN SOCKET Connection lost to server 0

    CLEAN activity for buttons for server 0 as the connection was lost

    Cannot send command to (unauthenticated or connection failed)

    Cannot send command to (unauthenticated or connection failed)

    Cannot send command to (unauthenticated or connection failed)

    Cannot send command to (unauthenticated or connection failed)

    ** MANAGER CONNECTION Connecting to localhost:5038 (Server 0)
    ** MANAGER CONNECTION Connected to localhost:5038 (Server 0)

    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)
    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)

    ** QUERY CUSTOM ASTDB 2400 CF

    Cannot send command to IO::Socket::INET=GLOB(0xf67c200) (unauthenticated or connection failed)

    127.0.0.1 -> Action: Challenge
    127.0.0.1 -> AuthType: MD5

    127.0.0.1 <- Asterisk Call Manager/1.1
    127.0.0.1 <- Response: Success
    127.0.0.1 <- Challenge: 438789614
    127.0.0.1 <- Server: 0

    127.0.0.1 -> Action: Login
    127.0.0.1 -> Username: admin
    127.0.0.1 -> AuthType: MD5
    127.0.0.1 -> Key: de0cdd243cd6f13411025a1ea9153d6d

    127.0.0.1 <- Response: Success
    127.0.0.1 <- Message: Authentication accepted
    127.0.0.1 <- Server: 0

    ** QUERY CUSTOM ASTDB 2100 CF

    127.0.0.1 <- Event: FullyBooted
    127.0.0.1 <- Privilege: system,all
    127.0.0.1 <- Status: Fully Booted
    127.0.0.1 <- Server: 0*


  • Phantom Queue Members
    D dogatemycomputer
    Support

    We run the FOP on a few servers for our telemarketing and call center customers. The only solution we could find to eliminate the problem is adding this to cron:

    0,30 * * * * /sbin/service fop2 restart

    If the Flash Operator Panel is loaded on a client then it will automatically reconnect after about 15 seconds.


  • 'Connecting to server, attempt number... ' with SSH
    D dogatemycomputer
    Support

    I wanted to post this message because I just spent approximately 5 hours trying to get FOP2 installed with FreePBX over SSH. There are plenty of documents indicating FOP2 listens on port 4445 by default. The problem is there is very little discussion as to WHY it is listening on port 4445.

    TCP/4445 is used by the Flash client to communicate with the Flash Operator Panel on the server. If you are installing FOP2 via port forwarding TCP/80 over SSH then your client cannot access the server unless you also forward port 4445.

    ssh root@<serverip> -L 4445/localhost/4445

    If you fail to forward those ports then you will be presented with the login screen, you can enter your credentials but after that you will only see..

    "Connecting to server, attempt number 1" .... "Connecting to server, attempt number 9"... FAILED.

    Of course I have over 25 years of IT experience so I should have known better but I completely spaced it. Hopefully this will remind the next guy.

  • 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