Recent content by voipBull

Hello all, Looking for some suggestions around this issue that I'm experiencing with calls to external PSTN numbers via Ring groups. So I have a user extension, Ext 1001, that is call forwarded to an external number 416xxxXX31. And this Ext 1001 is part of Ring Group 8001. Ring group has...

Thank you @markjcrane

@michelerizzo88 Usually carriers follow the below order of preference for caller ID (Atleast North_American carriers) 1/ P-Asserted ID header 2/ Remote-Party-ID header 3/ From header In your case. you are atleast sending the R-P-ID header correctly (0832139XXXX for name and number - I'm...

@mudasar321 Its always a good thing to share back what you found to be the solution to your issue, so that others who may experience the same issue can use your solution.

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'.