Quantcast
Channel: FreePBX Community Forums - Latest posts
Viewing all 227965 articles
Browse latest View live

Problem with system update

$
0
0

It's unlocked...ran the command again. It's doing something right now. will report when that something is finished. Thanks,


Audiocodes 310HD provisioned with EndPoint Manager

$
0
0

Thanks Tony. I have just opened it!

TFTP server not starting FreePBX 14 - HELP!

$
0
0

I noticed this as well

[root@pbx log]# service xinetd status
Redirecting to /bin/systemctl status  xinetd.service
● xinetd.service - Xinetd A Powerful Replacement For Inetd
   Loaded: loaded (/usr/lib/systemd/system/xinetd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2017-08-14 18:12:57 UTC; 29min ago
 Main PID: 718 (xinetd)
   CGroup: /system.slice/xinetd.service
           └─718 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid

Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: removing discard
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: removing echo
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: removing echo
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: removing tcpmux
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: removing tftp
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: removing time
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: removing time
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.
Aug 14 18:12:57 pbx.axcoadhesive.local xinetd[718]: Started working: 0 available services
Aug 14 18:12:57 pbx.axcoadhesive.local systemd[1]: Started Xinetd A Powerful Replacement For Inetd.

TFTP server not starting FreePBX 14 - HELP!

$
0
0

While I cannot answer your actual question I would suggest that you try out HTTP provisioning sometime as it works much smoother than TFTP and I've had less problems with it.

Problem with system update

Can I have different external port configured in firewall for freep pbx nat?

$
0
0

So, you agree that it depends on the router...

You will need to open UDP ports 10000-20000 on the firewall and redirect them to the server, but the 5060 port on the phone can be directed through any open port on most systems. Apparently not PFSense (although it works fine when I do it).

Now, it's important to understand how this is going to work. Outgoing calls should work without changes (as long as the rest of your NAT is set up correctly). Incoming calls (from an ITSP) should get redirected correctly through the external firewall. You should still lock down the 5060-avatar port to known hosts just to keep the curious out.

You can also set up your incoming port in Asterisk/FreePBX to match the "odd" port you picked in the firewall and tell your ITSP your incoming call port is "whatever". Your ITSP may or may not want to set up something other than 5060 for THEIR incoming calls, but that's a separate connection (your incoming and their incoming are completely independent)..

Every Monday all of our phones are down saying "invalid account"

$
0
0

The log shows the successful update. What happens when the phones try to reconnect?

TFTP server not starting FreePBX 14 - HELP!

$
0
0

TFTP doesn't run all the time, but you should be able to enable it by updating the tftpd file in /etc/xinetd.d. Remember that the option is backwards )"disable = false" turns it on). Once you have that, xinetd will manage your TFTP sessions.


Send Volumes

$
0
0

Same problem here across two installs. It's hard to tell them "you're using it wrong"

Can you tell me the issue ID you opened?

Send Volumes

$
0
0

And I'll add you can do a basefile edit and adjust it.

0 # HandSetSendVolume
0 # HeadSetSendVolume

Send Volumes

$
0
0

Edit again. It does work:

6 = -6dB
5 = -4dB
4 = -2dB

Anything but 6 (or -6dB) is really loud unless you are 2" away from the handset. Frankly I think it's still too loud even at this setting

TFTP server not starting FreePBX 14 - HELP!

$
0
0

Why wouldn't TFTP run all the time in a PBX environment? You need it to provision phones.

Every other FreePBX install (v13) the TFTP server was always running?!

Why register multiple lines on same phone to same extension?

$
0
0

all,
I am doing this on my installs now. If I am doing something wrong or not using best practice, i would like to know.
The reason i have the phones configured for 2 accounts to the same extension is because when I do that, the user can be on the phone, get a second incoming call and either conference it in or switch to it if it is more important.
When I just have one account to one extension, the second call goes to voicemail.

so, is this wrong? or is there a better way?

TFTP server not starting FreePBX 14 - HELP!

$
0
0

Not in my experience. It's always run out of xinetd (and inetd before that). In fact, that's the primary reason for having xinetd installed. I've never seen a Unix-like system where TFTP ran all of the time. Of course, I could be wrong, I've only been doing this kind of work since the 1980s.

Upgrade from 13 to 14 Error on phase 2

$
0
0

Did you find out the fix on this? Our machine is stuck at exactly the same looping error.


TFTP server not starting FreePBX 14 - HELP!

$
0
0

Well I don't know as much as you, but how are phones supposed to provision via TFTP if they can't receive the configs as the service isn't running? Or am I missing something?

Why register multiple lines on same phone to same extension?

$
0
0

With Chan-SIP, this setup (Shared Line Appearance, IIRC) wasn't possible since the registration was unique - you couldn't have two sessions on the same extension. To accomplish this kind of "multi-line" exposure, you needed to set up multiple extensions and mark then as "the original" extension. Not challenging and it supported your "two calls at a time" thing.

With the advent of PJ-SIP, it's now possible to register more than one line to an extension. You need to set up the extension so that it supports multiple appearances.

I don't think there's a "best practice" involved - it depends on what you're trying to accomplish. I prefer people calling get VM if I'm busy. Telephones are already an incredibly rude system of communication, so dropping someone onto hold while I talk to this new caller that's more important than your last caller is just worse.

Why register multiple lines on same phone to same extension?

$
0
0

I am using pjsip and this is not multiple appearances as it is only one phone (this works if max endpoints is 1) however, i hear what you are saying, but in the end, we set it up the way the customer wants.

Number of external numbers in ring group gets matched against Outbound Concurrency Limit

$
0
0

Just found out that if you have several external numbers in a ring group, the total number of those get matched against the Outbound Concurrency Limit of the extension you call the ring group from.

In other words, if the Outbound Concurrency Limit of your extension is 3, and you have 4 external numbers in the ring group you are calling, you will get a "your simultaneous call limit has been reached" message and the call will fail.

Now that doesn't look right to me.
Is that a bug?

TFTP server not starting FreePBX 14 - HELP!

$
0
0

Xinetd starts an instance of TFTP for every request, thereby preventing a single instance from locking everyone else out. This is a more appropriate use of resources than trying to have one, and only one, TFTP running trying to respond to phone config (or other file transfer) requests.

IIRC, Commercial EPM resets the xinetd TFTP server to start on demand. If it isn't, I think it's a bug. We (the list) talked about this a couple of months ago and I recall that being the way forward.

Having TFTP enabled "be default" is not an industry best practice. We normally want the server disabled and turn it on "on purpose", which is why I suggested updating the /etc/xinetd.d/TFTP file to "enable" the TFTP service so that you can get the software downloads working.

Viewing all 227965 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>