zwillis

Member

Last active 9 years ago

  1. 9 years ago
    Fri Oct 9 20:03:49 2015
    zwillis posted in Click to Call Not Working.

    Hello,

    I've set up a fresh machine (new image, only Chrome and Bria softphone application), built outside our domain, to avoid GPO's that would be causing the restriction of configuring the protocol handlers.

    Although the handlers are more configurable, it still acts the same, with or without protocols enabled for either application.

    I remember you mentioning this yesterday, I noticed in the Console tab of the background page, anytime the number is clicked it provides this

    (22-number of attempted clicks)
    sending command <msg data="27|dial|8004057119|2f4776f18ce7500b9b981466f3cbxxxx" />
    background.js:6 ping -2
    background.js:6 sending command <msg data="1|ping||" />

    I also notice that when you middle-click a link, it's suppose to auto-open said link in another tab, but this doesn't work, only with FOP2 clickable numbers. It's definitely the protocol handlers, right?

    Thanks

  2. Wed Oct 7 14:56:18 2015
    zwillis posted in Click to Call Not Working.

    Hi,

    For some reason our click to call feature seems only half functional and was wondering if someone could provide some support to this.

    We are using FreePBX along with FOP2 Chrome Extension and Bria Stretto. I don't know the technical specs but I'll give you some information.

    When you go to any clickable number, and click it, the softphone will not ring with the number selected. However, if you hover over any phone number and right-click > open link in new tab, the click to call function works as intended. We have 1 user that we're aware of (all Windows 7) that has working click-to-call, and found that his SIP protocol under 'Default Programs > Bria Stretto' are all unchecked. When we try to uncheck these boxes for ourselves, the boxes are checked and grayed out, and cannot interact with them at all. We feel this might have something to do with it, but am not 100%. Editing these protocols through registry also had zero effect, although my registry and the functioning one is identical.

    These screenshots are the only differences I came across between the computers on this issue.

    Was just curious if you had any information regarding this or maybe have ran into this issue in the past? Any help would be greatly appreciated.

    Thanks,
    Zac

  3. Mon Oct 5 17:31:19 2015
    zwillis joined the forum.