Search results

I think I was looking at the wrong file, it is in: /etc/freeswitch/autoload_configs/cdr_mongodb.conf.xml There is also a file, in which it is still disabled: /etc/freeswitch/autoload_configs/cdr_sqlite.conf.xml <!-- Log a-leg (a), b-leg (b) or both (ab) --> <param name="legs" value="a"/ >...

Go to Advanced -> Upgrade. You will see "Source Code" at the top, that's how you upgrade version of your FusionPBX. Click on the commit id to see what has changed over your version up now. Don't forget to tick all checkboxes before you hit the execute button. Also you should take a backup before...

I have tested several scenarios and found out that it happens only in Call Center Queues and only if the call is inbound. Scenarios: A: - An extension makes an outbound call OR; - An inbound call or a local call comes directly to an extension OR; - A local call comes to call center THEN; - The...

It is already disabled: <param name="log-b-leg" value="false"/>

Hi. Here the screenshot tells it: The caller calls at 03:18pm and has a 9:46 call duration. But all this time of call, it continues to log the call as "not answered" although they are already on call. I don't know also why destination is not resolved but rather displayed as a variable...

You sure? Here is mine and it works as expected: But of course the line is "caller_id_number" check and not "{$sip_from_user}" if that makes the difference.

Yes, it definitely works in the destination, I am using it right now. But as I said, destination UI doesn't work that way, I have to manually edit inbound route to make it as exactly in the screenshot you posted. Now I am pretty sure that the UI makes it two lines and it works as logical "AND"...

There are some certain callers which I don't want to be transferred to the standard IVR, but instead, it must be transferred to a specific extension. For that, while creating the destination, I add multiple conditions like: This creates two different regex lines for the two caller ids, in the...

That's actually what I am trying to understand, thank you for bearing with me. But as I said, having multiple conditions in destination doesn't actually work, so I have to manually edit the inbound route.

Then there is no problem having zero destinations if we have the inbound routes set correctly, right? And you have any idea about the third article? Seeing the destination number as a variable in the CDR?

Here is the scenario: - The operator starts an attended transfer holding the caller on the line. - The operator talks to a local extension. - The operator returns back to the original caller. The caller's sound is distorted like it is a playback at 2x speed. When I listen to the call record...

I didn't claim that it did. I am just trying to understand. So you say destinations is just a tool to set inbound rules in a simpler way as a UI?

But changing the destination changes the inbound route too? I understand that inbound rules are more advanced to be given the access; but what about my points 2 and 3 while working only on destinations doesn't work as expected?

Hi all, Today I have started using FusionPBX today on production with 4 trunks and 15 extensions, with several IVRs, Call Centers and as such. In general, everything is working fine except some, for which I would like to understand what is the function of destinations. Actually I didn't quite...

I have some T21 and T19 devices on the same network. T21 devices auto provision and take every settings I did through Default Settings -> Provision while T19 phones receive ONLY the account information; but everything else is ignored like: - Timezone - Call waiting - Feature Sync like Call...

The agent timeouts are the default values and it is already low, so it can't let the hold music play forever. And nevertheless, the agents are not even registered, so the system should know that there are no agents available and trigger "No Agent Max Wait"

Anybody? Here is my insight after long testing hours: - "Max Wait Time With No Agent" and "Max Wait Time with No Agent Time Reached" are the same thing according to the docs, but I don't why they co-exist. Besides, both are definitely disregarded. Whatever you set here doesn't change anything...

Hi all. I see a "please_hold" dialplan which plays the prompt "ivr/ivr-hold_connect_call.wav". How can I use this actively? I mean when a user dials an extension or an option in an IVR, appearently we can set it to prompt "please hold while I am transferring your call". But couldn't find it...

Extension 11 is set to record only inbound calls. Extension 12 is set record "disabled". When 11 calls 12, I expect the system not to record the call, but it does. I don't want any of the calls extension 12 to be recorded but it is always recorded regardless of the settings.

I have been searching but couldn't find it anywhere. Right now, if the called extension is busy, if it's a local call, the other party sees normal clearance and if it's an inbound call, the caller sees and hears nothing, just the call terminates immediately. I tried playing with tone settings...