Search results

@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/

You are running a fairly old version of FS PBX. There have been a lot of updates since 1.7. I don't know if @pbxgeek might have made changes that affect the time zone between where you are and the current 1.8.2 version. The changes have been coming fast and furious.

ChatGPT is the absolute WORST AI to use for programming and troubleshooting. Grok or Gemini are much more reliable. Better yet, follow the instructions at the product's web site.

Thanks. New dashboard buttons a great! I love the new MOH interface and the ability to have the music files play randomized now.

This is a minor suggestion. On the dashboard screen, I instinctively press the icon on each button. Of course, the icon is not in the box that will take you to the selection. My suggestion would be to make the active area of the button include the icon on the button as well.

Dial plan XML changes are part of the setup in the instructions. Here is how my Call Center looks in FusionPBX: The magic is in the new and modified .lua scripts and the modified XML. The GUI is just a basic setup which allows the caller to press-1 to be transferred to a voice mailbox.

This is my original post: https://www.pbxforums.com/threads/announce-position-in-queue-upon-entry-and-continue-to-update.8733/

Yes it works. You have to create callcenter-announce-position. Read the initial post that I link to and then see what modifications I made to it. I have DM'd you a test number so you can see how it works when implemented.