Search results

https://docs.fusionpbx.com/en/latest/dialplan/dialplan_details.html#call-limit

I tried too. I can't register to my trunking server but my Yealink phone can register to trunking server when a : is used in the password. Might be an issue on Freeswitch rather than Fusion.

How long is a piece of string? Depends on the acceptable quality required by the parties on the call. If calls are fine at 5K, great. At 10K? great. There is no formula as the bottleneck could be in any place in your interconnected systems.

Instead of us guessing, why not include a picture and some log info to help you out?

Looks like you are very familiar with the state of SMS in FusionPBX, and you're just fishing. Would be redundant for me to link you the rest of the SMS related threads on this site, so what have you tried? Might help people give you a useful answer.

Calls have nothing to do with web content, so no interruption to calls while messing around with Nginx. Provisioning will be interrupted (for 15 seconds?) as that does require web based content. As always, if you are unsure on a production box, the smartest thing to do is create a test system...

Well there's one of your problems .... Your customers can do [vmxfr][blf_extension] - two presses This exists and is called "paging" - they may be a prefix you can use, similar to what I mentioned above Provisioning can apply any button to the Yealink - issue here is you need to first work it...

This isn't a paid-member forum. Care to share a means @ad5ou?

I would look at the phone logs to see the specific reason on why they can't keep registration.

An Nginx 504 error would be logged in /var/log/nginx/error.log. Can't help without some kind of error to go off. Look at the access.log and error.log when making your requests.

They do not call from the web interface. They can go to their User Settings and toggle to and from Available.

Create extension on domain A and B Register extension as a gateway Register extension A as Gateway on B Register extension B as Gateway on A Create outbound rule to transfer calls through gateway on A and B

Hi Gay, 1) has to be an actual inbound number from your provider. e.g. 56435634564. 2) Has to have an action. You can see in your image that your inbound route just hangs up. Also if you are trying to trunk extensions on one PBX to another PBX you are doing it all wrong.

Pay me and I'll work the rest out for you. Otherwise you'll need to get your hands dirty commenting lines out!

That's why I shared all I had with you and why I don't use Polycom. Tell me about it. Change. Test. Change. Test. All you can do with Polycom. Use code blocks when posting logs. Not going to read through that.

I have successfully provisioned a VVX400 with LDAP via TFTP (many many years ago) and not via Fusion. Only way I can help is by saying I had the line: <APPLICATION APP_FILE_PATH= "Firmware/sip.ld" CONFIG_FILES= "...,Config/LDAP.cfg,..." And my LDAP.cfg file looked like this: <dir>...

Hi Gay, Two things... 1) You are not sending the caller number. You f**ked something up and are sending the literal string ^(\d{4})$ not the dialed extension 5514 or 5590. Regex (FAIL) [BREWE_165.0d11] destination_number(^(\d{4})$) =~ /^0\+?(\d{11})$/ break=on-false Regex (FAIL) [BREWE_165.d4]...

Welcome. Not sure I would call it a "distro" even if it is technically "distributed" :p

After reading your reply, it looks like you don't want the new devices to have lowercase letters. In the case, you would apply the same logic, but to the app/devices/device_edit.php page. Also, no need to restart Nginx for PHP changes.

This is very difficult to read and interpret. I assume the TLDR; is that the URI from the Cisco devices becomes lowercase in the Fusion processing. No. This is done in source within the app/provision/index.php.