mkeuter

Member

Last active 5 years ago

  1. 10 years ago
    Wed Oct 1 12:07:55 2014

    Update: I have 2 servers configured (localhost + an external). All related buttons I was testing are configured for server 1. In debug mode I could see, that the failed call event is sent to server 2 instead of 1. After a call on my phone, the next event is sent to localhost (1).

  2. Wed Oct 1 11:52:47 2014
    mkeuter started the conversation 2.2.8 Cannot dial a button after reload.

    Hi Nicolas, I cannot dial a button in FOP2 2.2.8 for my logged in extension after I reloaded FOP2, before either my phone is called by someone or I make an outgoing call on my phone directly. Basically an event related to my phone has to occur, before I call dial a button. Any idea?

    Michael

  3. Mon Sep 8 13:20:35 2014
    mkeuter posted in Queued Calls Counter Plugin.

    Here is the German language file:

  4. Mon Sep 8 08:38:03 2014
    mkeuter posted in Queued Calls Counter Plugin.

    Is there also a way to get this plugin without the FOP2 Manager? In AstLinux we don't have MySQL server.
    Or is there a way to get FOP2 Manager running with SQLite3 ?

  5. Fri Jul 25 19:09:26 2014
    mkeuter posted in Queue MemberName behavior.

    Hi Nicolas,

    I don't know what's happening internally, but on my own system and another customers one, this does not happen. See screenshot (extension 24 has the MemberName 24@local-agents and the button is still named "Yealink Büro"
    http://mksolutions.info/galerie/q-membername.png

    [SIP/24_yeal38g]
    type=extension
    extension=24
    context=internal-phones
    label=Yealink Büro
    group=UG
    server=1
    customastdb=CF/24
    queuechannel=SIP/24_yeal38g|Penalty=0|MemberName=24@local-agents

    Update: it seems when the SIP peername is not SIP/12 but e.g. SIP/12_xxx then it works.

  6. Fri Jul 25 14:18:04 2014
    mkeuter posted in Queue MemberName behavior.

    Hi Nicolas,

    in this case the Member is a SIP channel not a Local channel:

    91 has 0 calls (max 1) in 'ringall' strategy (13s holdtime, 12s talktime), W:0, C:7, A:0, SL:85.7% within 30s
    Members:
    12 (SIP/12 from SIP/12) (ringinuse disabled) (dynamic) (Not in use) has taken no calls yet
    No Callers

    Update: it also happens if I change the context from "default" to it real context "ip-phones".

  7. Fri Jul 25 09:52:41 2014
    mkeuter started the conversation Queue MemberName behavior.

    Hi Nicolas,

    at one of my customer sites with FOP2 2.2.7 I see a very strange behavior when I use the "queuechannel" setting:

    [SIP/12]
    type=extension
    extension=12
    context=default
    label=Secretary
    queuechannel=SIP/12|Penalty=0|MemberName=12

    When I use the above setting and I login 12 into a Queue, the member in the Queue appears with "12", which is fine. But also the label of the extension button for "12" switches from "Secretary" to "12".

    On my own installation and another customers FOP2 2.2.7 installation, this does not happen.
    I compared all related setting, but didn't find anything helpful.
    Any idea what could cause this?

    Michael

  8. Sat Jul 19 17:35:00 2014

    Hi Nicolas,

    I got something working already. But how can I use 2 different handlers for login and logout in one plugin?
    With 2 different it works for me.

  9. Fri Jul 18 09:10:21 2014
    mkeuter started the conversation Queue logged in hints for Queue Agents.

    Hi Nicolas,
    for some customers I have setup BLF keys on the phones for my Queue Agents to dial an extension which toggles login/logout to/from a Queue.
    In the Agent login routine I also set the status for a custom hint (INUSE, NOT_INUSE), so that an Agent could see on the BLF key on the phone, if he's logged into the Queue or not.

    exten => _qm-queue1-XXX,hint,Custom:qm-queue1-${EXTEN:-3}

    Is there a way in FOP2 to adapt this behavior and turn the custom hint on and off, when an Agent is logged in/off through the FOP2 webinterface?

  10. Mon Jul 14 21:09:11 2014
    mkeuter posted in Hide inactive extensions.

    Yes, that would be a nice option for "fop2.cfg".

View more