Search results

Isn't that the default behavior when a external number is dialed from an IVR, the original caller's caller ID name and number is used on the outbound call to external number. What version of FusionPBX are you running? How are you dialing the external number from the IVR? Can you share the...

BTW, fixing the above typo in destinations.php fixes the duplication issue, but looks like there's another issue with Actions column as well. I see changes were made to actions function as well in the same commit (6176ea2).

@whut I only signed my CLA to be a contributor for the project yesterday after I found this issue. Waiting for the signed CLA pull request to be merged first.

Well, looks like its just a typo in a recent commit (6176ea2) to destinations.php Line 244 foreach ($destinations as &$row) { should be foreach ($destinations as $row) {

Tried this on two fresh installs, FusionPBX master branch, just to rule out any config errors and same results. No new applications or mods installed after fresh install. Added first inbound destination, and saved it. (Using fake numbers for demo, and leaving the ACTION blank - same results)...

I came across this exact same question when I started working on DB replication last week. Overall it depends on your unique setup, but in my case I just skipped replicating the gateways table, and then on the secondary box, manually configured a gateway with same name and details and marked it...

@jessiem can you try to download the device config file directly off of your FusionPBX, and check if you see this line in the DEVICE_KEYS block attendant.resourceList.2.address

Can you please add a little more context as in what and how are you trying do it? maybe a few screenshots of the device setup page?

In FusionPBX, the only two places I can think of are either in the Gateway settings page called 'Channels', or the Extensions setting called 'Limit Max'. The latter only gets used if you have enabled 'call-limit' in your dialplan.

Let us know here if you find a way. Thanks

Thanks @Alocaurd I think because I wrote my own emergency dialplan, I didn't have this line in there, but I can see it if I create a new outbound route in the UI and use '911 Emergency' from the dropdown for option 'Dialplan Expression'.

I played with is_local last year, when I wanted to see how it will look like when extension1 in tenant1 calls a 10 digit number for extension2 in tenant2. The only problem I came across that I couldn't really find a solution within FusionPBX was that the CDR gets messed up. A call like that was...

'Messages' is what you'd want to go with. Recent changes have broken inbound on the 'SMS' app, so don't even bother with it.

So you can control the actual number of cdr records to retain, the setting is at Default settings > Category 'CDR' > limit. Number of retention days for CDR records and call recordings, I don't think you can do this from any setting available in the UI, atleast not that I know of. The only way...

Rebranding FusionPBX is a member feature. members

Well, VVX D230 does not run the same UC firmware stack that all other Poly VVX series phones run. That's because Poly just stamped their logo on it after they acquired OBihai. VVX D230 runs the OBihai stack under the hood. Now that being said, provisioning it against FusionPBX should just be as...

Just curious, what these 'Emergency logs' are and how are they used/populated. Couldn't find any documentation or any previous discussion about it here.

I think I'm a bit confused after your last message. Just to confirm, is your phone getting any provisioning values/settings at all or not? how do know that if the phone is not getting any values?

You can start by looking into the phone templates you're using for your device to see if the default settings you want are even referenced in the template or not

Put the number you want the outbound calls blocked to in the 'Number' field instead of 'Name' field