Search results

OpenAI does a much better job at translating various dialects or slurred English. I've tried Watson on a FreePBX system and ended abandoning it.

I had that briefly on one of the 5.4 versions of FusionPBX. You could put the robotic sounding call on hold and pick it back up and it cleared. I'd agree that it is mismatched codecs for some reason.

Yes. That works on a Grandstream GRP2612 and on a Fanvil X4G but not on an Avaya J-series phone. On the Avaya phone I found out (by very frustrating trial and error) that I have to subscribe to presence and MWI for the actual park button on the Avaya phone to work and display status...

Credit where credit is due!

That's odd. Works for me using Chrome browser. I am able to copy using the copy icon and paste to a notepad as a test. See below: And yeah, it takes a lot of mental gymnastics to translate FS PBX/FusionPBX/FreeSWITCH from a brain hard-coded for Asterisk/FreePBX. Six to eight months in, I...

I'm running it on two clouds. FS PBX keeps getting better with the responsive, rapid updates. FreeSWITCH has its quirks but FS PBX helps refine them.

Until you run any of the frequently released updates to FS PBX. Then I suspect you need the 4 GB again.

@pbxgeek I am experimenting with barge-in to an existing call (*33+extension). The lua script requires a password, which I have commented out for testing. The problem I have is that every time I try to barge into a conversation on the line in question, the connection is robotic, has loud...

OK. I had to play with the feature codes contained in the phone itself so I have to modify the config files.. I somehow solved the issue. Thanks for the assistance.

I am running Avaya J-100 series phones with 3pcc. A normal extension BLF works. Its just the park codes. I can make the BLF-PARK feature of the phone work but I'm trying to set up other phones with only the pickup of *5901. The BLF dials the code and retrieves the parked call but the light...

It should be stock, fresh from standard installation. The issue may lie in FreeSwitch lua scripts someplace. <extension name="valet_park" continue="false" uuid="c2f618ec-0ff7-41d6-971e-727f9457f1ec"> <condition field="destination_number" expression="^(park)?\+?\*(59[0-9][0-9])$"...

Yeah. I already do that with "park+*5901@mydomain.com" but it never lights the button either with or without the "park+". My system is in the cloud and neither the domain or the direct IP address make any difference. On a FreePBX/Asterisk system, I can create park hint for just about anything...

Well I might have gotten the park button to work correctly but I'm still interested in the BLF for *5901.

I have some phones that the call park button does not work correctly with them. To get around this, I'm trying to set up BLF buttons for *5901 to park and retrieve that call. I cannot get the phones to show busy indication on those buttons which would indicate a call is parked at *5901. This...

FS PBX Version 1.8.4, by relocating the FreeSwitch scripts to the 'repo' directory broke some of my custom xml coding and lua scripting.. I don't know exactly where to find the FreeSwitch repo directory. There is still a /usr/share/freeswitch/scipts directory but my custom lua scripts are no...

I already did a Debian-12 update on one system and a Debian-13 update on another. Both ran successfully and I have not seen any problems with FS PBX so far. The updates did install a new kernel.

FusionPBX has posted a script to upgrade FreeSwitch to the current level which addresses a security issue. Is there anything we need to do for FS PBX?

Mark, this is very helpful. Thanks!

Yes, having someone who speaks the native tongue in question is very important in the translation process. Getting the words and grammar correct is a very big job when updating the GUI interface. I'm sure @pbxgeek will be happy to have assistance with a foreign language. Google translate often...

Here is an interesting company that appears to have already created sets of voice prompts for FreeSwitch: https://www.westany.com/freeswitch/