Search results

That's supposed to be a curly braces instead of normal brackets.

You're missing the dollar signs in the variables. As for the SIP outbound proxy issue, that's part of the line information along with port, etc. Shouldn't be anything necessary you need to change in the template. (There is a brand new Yealink firmware that doesn't like sip_server_host anymore...

There's a script provided with the installer called dsn.sh that does it all for you, you'll need to provide it with the postgres password found in /etc/fusionpbx/config.conf Unless you have a lot of domains, SQLITE is perfectly fine as long as it's on a RAM disk. It's perfectly fine on an SSD...

Check Event Guard. https://docs.fusionpbx.com/en/latest/status/event_guard.html

https://docs.fusionpbx.com/en/latest/advanced/access_controls.html SIP Providers rarely use challenge based authentication, this permits unauthenticated INVITEs from specific IP address ranges.

Next time, make a new thread. It's confusing to mix issues. Have you ensured that 178.128.235.81 is in the providers ACL? Your external SIP profile uses this to decide whether to send authentication challenges.

I think editing the default call_block should be enough to include local into the regex. Not tested myself. Make sure things like voicemails/transfers still work.

Enable the is_local dialplan rule. It's a LUA script that detects local routes and transfers them to the destination context accordingly. As for the WHY?????, it's probably for people like me who have to make every call to different entities go via the voice core network instead of floating...

I can attest to the Acrobits Cloud Softphone too.

You 100% NEED to use Google Firebase or Apple Push Notification Service for iOS, and you also need to have a proxy hosted online that wakes the phones using Firebase/APNS to tell the phone to re-register for the SIP INVITE that is about to be sent to the phone. This reason is why the only...

Yeh, I thought that, but then it happens next year and the year after that too. I think someone at Yealink/Fanvil just made an erroneous commit.

https://www.pbxforums.com/threads/dst-a-week-early.7692/post-31224 Fix in here. Not tested with every single model though.

KeyDB seems promising, only downside is the BSD license means the same might happen again.

Yeh, most of our Yealinks and on FusionPBX AND 3CX. Yealink must have dropped a bollock when defining the automatic DST time, as they've put it as the 4th week instead of the last week of March. Must be a recent thing as some ancient phones like the T27P have got the correct definition. I just...

You'll probably want to take the extras folder from the legacy 5.2 branch of PHPMailer: https://github.com/PHPMailer/PHPMailer/tree/5.2-stable as the supplied one with FusionPBX doesn't seem to include the entire thing: https://github.com/fusionpbx/fusionpbx/tree/master/resources/phpmailer...

On a rudimentary level, it is possible to attach another PBX as an extension to FusionPBX. You simply set the outbound caller ID on the extension, and route the inbound to the extension. For more complex setups, you may need to research the Bridges tool...

You sending the INVITES to port 5080? 5060 is for extensions. 5080 for trunks.

You'll find a lot of the configs don't have the provisioning variables after account 1, 2, 3, etc. You'll have to manually match them up to the account.1.codec rules in /var/www/fusionpbx/resources/templates/provision/yealink/w70b/{$mac}.cfg...

Nevermind. It was simpler than I thought. All I had to do was export a new variable diversion_outbound_number=${dialed_extension} and use that in the outbound routes as my effective_caller_id_number. There's me trying to complicate things by doing it in the one leg,

Debian 8 repositories! :eek: