Search results

Hi @markjcrane , any update on this issue? I updated to the latest 5.4 version and it's still happening.

Ok, here's part of the puzzle. The devices I was updating are yealink t46u's. looking in the provisioning editor, that model has 6 files. I set device #2 to a cisco 79x1, which has 3 files, then I was getting 6 updates for device #1(yealink) and 3 updates for device #2(cisco). Then I changed...

I'm not sure what other information is needed to troubleshoot this. When I click save on one of my two test extensions, the regular queries (ie. updating the extension, device, voicemail) happen. That's not a problem. But then it seems to trigger a provisioning update (6 times?) on every single...

Hi all, Whenever I click save on a device or an extension (even if the extension doesn't have a device associated) FusionPBX generates 6 update queries per device in the system. For small systems this isn't really an issue, but I have close to 2000 devices, so every time I click save, it's...

I had uppercase chars in the mac address in my sql queries, converting all macs to lowercase seems to have fixed the issue.

Nevermind, it had nothing to do with 5.4. I am importing stuff via direct psql and I believe my device import is messed up somehow.

Hi all! I just upgraded FusionPBX to version 5.4 (from 5.2 via 5.3) and am getting 404 errors when I add/change extensions and devices. The changes are made, but instead of the banner at the top showing the status, it goes to a 404 page instead. Gateways, users, everything under dialplan...

Aside from adding the tag, the final version is pretty much the same: <extension name="operator-new" continue="false" uuid="53fa7641-b806-4a8d-bede-a5d8e0c7f05f"> <condition field="destination_number" expression="^0$"/> <condition field="caller_id_number" expression="^50..$"...

I think I've figured it out. I added "break="on-true"" to all of the caller_id_number conditions so if one is false it doesn't stop processing the rule.

Hi all, Hopefully an easy question. :) I am trying to make an operator dialplan that sends to different operators based on the extension that is dialing 0. I've made a simple test dialplan to send two extensions to each other when they dial 0. the first one (3333 > 3334) works, but the second...

ok, I took off my blinders and noticed the mention of 3pcc. I see there's a SIP profile option called "enable-3pcc". I don't know enough about SIP to know what that does, but turning it on allowed the call through.

Hi all, I am trying to integrate Singlewire Informacast with FusionPBX. When I send a call through to a phone, I get "sofia.c:8032 No SDP in INVITE and 3pcc not enabled, hanging up." in the FreeSwitch log, because InformaCast does not send an early offer. I contacted their support and that's...

I believe that is for a 7940/60. 7942/62 use an xml configuration. Thank you for posting it though!

Believe me, I would love to. Unfortunately, I need to make these work or we're not moving to FusionPBX. I did manage to get my tester to send a register with the fqdn with an old firmware version (8.5.4) I found on github, but I seem to be having other issues now. Link to the github in case it...

ah, I think SPA phones are quite different from 79x2's.

I get a 404 from that URL, unfortunately. Do your notes mention a specific firmware version?

If switching to admin mode is different than pressing **# in the settings menu, I don't know how to do it. I can't really find any solid info on google, either. Some people have mentioned an "Unlock Settings" menu option, but I do not have it.

I can't seem to manually enter a line configuration. I've unlocked it with **#, but pressing select on a line does nothing.

I can register this phone successfully via SIP on our current FreePBX server. I copied the firmware and provisioning file from FreePBX to FusionPBX, and modified the address, extension, and password. I put the phone on the FusionPBX vlan (where Yealink phones are working great). I can see it...

Yep, I've made sure it's picking up the config. I've done a pcap, it's sending the IP in the request, not being overwritten at any point.