IshMalik

Member

Last active 8 years ago

  1. 8 years ago
    Fri Mar 11 15:33:57 2016

    Thank you for your rapid help, my issue is resolved now.

  2. Thu Mar 10 16:52:37 2016

    Actually it's blind transfer that defaults to # but I'm guessing the same principle applies...

    ;blindxfer => #1 ; Blind transfer (default is #) -- Make sure to set the T and/or t option in the Dial() or Queue() app call!

  3. Thu Mar 10 16:48:16 2016

    That makes sense, I'll test it now.

  4. Wed Mar 9 12:19:35 2016

    Hi

    As I understand it, FOP2 uses the key sequence as defined in the features.conf to initiate an attended transfer, and it uses the default which is a single #

    If I want to change this in the features.conf, is there a way to make the same change in the fop2 config?

    Thanks in Advance

    Ish

  5. 10 years ago
    Tue Jan 7 14:50:16 2014
    IshMalik started the conversation Pickup security hole in multi tenanted environment.

    Hi

    We are using version 2.26 in a multi tenanted environment. If user A clicks the call pickup button when there is no call coming in for that customer, it picks up a random call from another customer on the server. As you can appreciate that this is a serious security issue.

    Can anyone try to replicate this to and see if it is a genuine bug?

  6. 11 years ago
    Fri Dec 28 14:21:26 2012

    Hi

    I tried adding the server option again and it worked this time.

    I must have done some human error last time and misspelt server or something...

    Thanks for your help

  7. Thu Dec 13 13:46:57 2012

    Hi

    We are using FOP2 in a multi tenanted way and with multiple asterisk servers. We are having issues with the queue button as follows:

    Customer x is on server 1. When customer X logs in, all the queue members (stored in queue_members table using realtime architecture) are populated in the queue button, incoming calls to the queue show on the queue button and the presence indication works for the members of the queue button.

    Customer y is on server 2. When customer y logs in the queue button shows no members even though they are assigned to the queue via a realtime table. If queue members are added through the fop2 interface they will show on the queue button but the member icon never shows when the member is in use even though the extension button for the same extenion/member does show all activity.
    Incoming calls never show on the queue button either even though they are being routed through the queue.

    Extension buttons work completely normally for customer y.

    The asterisk configuration for the 2 servers is identical as the servers are deployed and controlled by puppet. The queue configuration for the 2 queues is the same apart from the queuename, timeout and context.

    The queue buttons are set up as follows
    [QUEUE/<queue-name>]
    type=queue
    label=<Distinct Label>
    extension=<queue-name>
    context=<customer-outgoing-context>

    I tried adding server=x.x.x.x to the queue button from customer y but this broke the fop2 service.

    Has anyone else encountered this problem and know what is going wrong and how to fix it?

    Thanks in Advance

    Ish

  8. 12 years ago
    Thu Nov 8 09:00:48 2012

    Hi

    Thanks for the tip, it really helped.

    So, the working condition I've got to is:

    RewriteRule ^/([a-z]{4})$ ?context=$1 [L,R]

    The key bit here is the R flag which issues a redirect to the browser and we end up at the messy URL again, which has got me wondering; where exactly is the get variable being picked up? Is it being pulled by php or extracted from the URL string by the javascript?

  9. Thu Nov 1 09:59:49 2012

    Hi

    I have successfully set up fop2 and have got it working in a multi tenanted environment but would like it to work with clean URLs

    each on e of our contexts will be 4 alpha characters so I have this in my virtual host config

    RewriteEngine On
    RewriteRule ^([a-z]{4})$ /?context=$1

    And have tried a lot of permutations of the above.

    I know that mod rewrite is enables because if I put /abc at the end of the user I get an apache error whereas if I put /abcd I get a fop2 login but it's like it ignores the context aspect.

    Does anyone have any ideas about this?