Try
fwconsole ma refreshsignatures
fwconsole chown
fwconsole r
Try
fwconsole ma refreshsignatures
fwconsole chown
fwconsole r
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Interesting… I was trying to get let’s encrypt to work on a box and it complained about this.
Hopefully someone internal will wake up and notice the alarms going off, but as the guy that WROTE the Mirror server, it looks like something is wrong with Apache.
The server is accepting connections, but the error ‘503: Service Unavailable’ means that Apache was unable to distribute it to a worker process. Probably just restarting the container will fix it.
If anyone REALLY REALLY URGENTLY needs access to the mirror server, I did write a mirror proxy earlier this year, due to me being on the other side of the world to the real mirror server. Feel free to send me a PM here or on Twitter (or facebook, or whatever - I’m xrobau everywhere) and I’ll see what I can do about helping you out.
However, I’m sure that as soon as someone at Sangoma sees the alerts, they’ll sort it out.
Could be related to the mirror1.freepbx.org being apparently down.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
This isn’t actually true. The Chan-SCCP-B module is installable and requires minimal “extra” steps: you need to install the asterisk-devel YUM update and you need to compile Chan-SCCP-B against that. Once done, you “not load” the chan-skinny Asterisk module and “load” the chan-sccp module.
There is also a “constantly in development” FreePBX management pageset for the phones in Skinny mode that allows you to manage them from FreePBX. I’ve written in this group extensively about both of these options.
The 79xx phones in SIP mode are terrible. In Skinny mode, they are actually reasonably easy to use. In addition, because of the way they are maintained, you can update the phones button configuration without having to reboot the phone.
Having said that, I would never recommend these phones to a first-time phone installer. If you have experience and understand the vernacular, however, these phones with Chan-SCCP-B and the FreePBX second-party SCCP Manager, the phones are easier to install than (say) Polycoms being flashed to Firmware version 3 to version 4.
There are a ton of ways you can do this. My order or preference:
Common voicemail box for all of the extensions. After 30 seconds, the call is dropped into voice mail and all of the phones are then marked as “email waiting”.
A queue. This way, you can preface the call with an announcement, put a message in the data stream, and basically control the call flow. There are also a lot of other cool features in a queue that aren’t available in a ring group.
Ring Group. Set up all of the phones in a RG and when the call is ‘dropped’, it ends up in VM. Make the “fail” time short (say 15 seconds) and tell people to pick up the phone with the first three rings or leave it alone. Combine this with 1. above and you have a solid, simple solution.
Using the Integrated Frewall, allow SSH and HTTP from only known addresses and get a known address. There are several ways to do this, including static addressing from your IP provider, DynDNS services, and VPN. Pick one and swing away.
There is native support for this with fwconsole
:
[root@lorne14-pro ~]# fwconsole trunks
Choose an ID to enable/disable
+----+--------+-----------------------------+----------+
| ID | TECH | Channel ID | Disabled |
+----+--------+-----------------------------+----------+
| 1 | pjsip | fpbx-1-redacted | off |
| 2 | pjsip | fpbx-2-redacted | off |
| 3 | custom | local/$OUTNUM$@custom-trunk | off |
| 4 | custom | local/s@trunk-notification | off |
+----+--------+-----------------------------+----------+
[root@lorne14-pro ~]# fwconsole trunks --disable 1
Disabling Trunk 1
[root@lorne14-pro ~]# fwconsole trunks
Choose an ID to enable/disable
+----+--------+-----------------------------+----------+
| ID | TECH | Channel ID | Disabled |
+----+--------+-----------------------------+----------+
| 1 | pjsip | fpbx-1-redacted | on |
| 2 | pjsip | fpbx-2-redacted | off |
| 3 | custom | local/$OUTNUM$@custom-trunk | off |
| 4 | custom | local/s@trunk-notification | off |
+----+--------+-----------------------------+----------+
[root@lorne14-pro ~]# fwconsole trunks --enable 1
Enabling Trunk 1
https://wiki.freepbx.org/pages/viewpage.action?pageId=37912685#fwconsolecommands(13+)-Trunks
If I understand your problem, I’d suggest setting the Caller ID on the outbound “city” trunk to use a standard “office” caller ID. That would solve the problem with internal extensions leaking out onto the POTS network.
Now, in the scenario where you have a call “from outside” that gets to a Cisco phone, which is CFW to an external number, it’s incumbent on UCM to pass along the original number. If that’s not happening in UCM, the number will get passes as the extension (which sounds familiar).
In this case, you might need to set up the system so that CFW is handled within Asterisk and don’t have the people using Cisco to use the “in the phone” CFW button.
Who are these?
Yes, that part. You still need to set up the Integrated Firewall to only allow your trusted IP address partners to access ports 5060/5160.
The “simple” way of doing this is to bite the bullet and buy the commercial module “System Administration”. You can manage it from there.
As mentioned in other threads, there are two GitHub sources for a solution to this specific problem:
Steps 1 and 2 to install the Chan-SCCP-B module from GitHub. Interesting new success with Chan-SCCP-B and SCCP-Manager (both from GitHub)
Once you do that, the phones will work in Skinny mode and be managed from the FreePBX GUI. It’s not EPM, and it only works with Skinny/SCCP phones, but it’s an option. There are a couple of gotcha’s in the install right now, but I think they’ve been addressed in recent weeks.
Short of that - you can try to manage it all by hand through your SIP settings.
While that’s totally true, if you can find and fix it yourself and then submit the fix, that is more likely to get your issue to get traction. The fix to the GUI is going to be the hard part - losing the link should be a snap.
If this is still a thing, I have two observations:
Obvious question: Why?
Are you installing something on the server that requires that version or are you looking at a security scan and need to get compliant?
I activated the firewall, now it works very well! thank you all for the information, you have helped me in a practical way to resolve to perfection
To say out loud what everyone else probably thought: WTH?
The regular expression is pretty straightforward (he says, lying through his teeth) but it sounds like you want concatenate a couple of WAV files, which is pretty simple is any free wave file editor.