@faisalkhan wrote:
I have setup a follow me to an external number. now what happens is when call is transferred to that external number after few rings but instead of getting voicemail of extension on no answer it goes to ivr or response from operator.
how to fix this issue?
I want my system extension’s voicemail to be presented in both cases whether it’s call on external number or my extension no answer.
Posts: 4
Participants: 3
@twojtczak wrote:
This machine is VoIP to E1 bridge. Working properly 2 years. Yesterday I found ~1200 active channels. FWconsole restart stop it. After ~24 hours same situation.
Posts: 3
Participants: 3
@MoTheMighty wrote:
Hello,
We have some boxes running HA and they have been acting a little squirrely lately and I think it is time to attempt a DB repair. So, I’m curious, what is the best way to do this on an HA system? I wouldn’t hesitate on a non-HA system, but I don’t want this beast to turn into Ultron. I already have backups of backups.
FreePBX: 10.13.66-22
Asterisk: 11.25.3
HA Services: 13.0.11Thanks!
Posts: 1
Participants: 1
@brian4 wrote:
I want to direct an unanswered incoming call (office number) to a recorded voicemail message (sorry we are unavailable right now) with the incoming message shared/sent to all extensions.
- I dont want to use an existing extension as that would be a personal message. Virtual/Custom Ext???
- How do I send 1 voice message to multiple extensions? or is it even possible?
Any help would be appreciated
Thanks
Posts: 6
Participants: 5
@yois wrote:
Brand new SNG7 1910 setup with all current updates as of today, including to Asterisk (13.29.2)
PBX has public IP and is NOT behind NAT. Extension is behind NAT. Registration goes to PBX but Asterisk is using the private IP of the device and not the public IP.
[2020-01-15 04:05:59] VERBOSE[27198] res_pjsip_registrar.c: Added contact 'sip:201@172.19.219.146' to AOR '201' with expiration of 3600 seconds [2020-01-15 04:06:02] VERBOSE[16326] res_pjsip/pjsip_options.c: Contact 201/sip:201@172.19.219.146 is now Unreachable. RTT: 0.000 msecOf the many FreePBX setups I’ve done, this is the first time I’m seeing this behavior, and I checked other systems and I see no settings set differently. The External IP is correct, and the local networks setting is blank (as there are no local endpoints).
What am I missing here?
Posts: 2
Participants: 1
@MrXirtam wrote:
FreePBX 14.0.13.23
Current Asterisk Version: 13.29.2I have noticed this issue for some time now and through at least a couple of FreePBX upgrades. Anytime I do a change, the Apply Config button shows. As soon as I press it to apply the changes, all phones drop registration and they will not register back again unless I either reboot the entire server, or I log into the CLI and issue the fwconsole restart command. Once I do that, phones register back up and everything is back to normal. I thought Apply Config was supposed to do the same thing, but doing it alone seems to break registrations. The trunks stay connected and registered, it’s just phones. I’ve noticed that this issue happens on multiple different FreePBX servers, both running different phones (Polycom and Yealink). Any ideas on this? Anything I can pay attention to while going through this process to help narrow down the cause?
Thanks!
Posts: 4
Participants: 2
@oliv2831 wrote:
Hello,
I’m completely new to LDAP.
I’ve just read [1] but I would appreciate to better understand how to use both FreePBX and LDAP.General questions:
Do LDAP directories commonly implement helpers functions that keep people from attributing an already allocated or incorrect resource ?FreePBX/OpenLDAP connector refers to “User Extension Link Attribute”. Does this attribute exists in every Directory based on OpenLDAP is it needed to create it ?
FreePBX/Active Directory connector refers to “ipphone” attribute. Does this attribute exists in every Active Directory ?
Is it possible to interface FreePBX with 389-ds ?
Scenario 1: Adding a new user and its telephony resources
Can you really set everything within LDAP Directory and let it create extension (I saw “Create Missing Extensions” in FreePBX/LDAP connector settings) ?
If positive, what is the event that triggers extension creation ?
Is there a Sync button within FreePBX GUI that create this extension or is the extension created whenever the LDAP Directory is searched by FreePBX and the need for extension creation is detected ?Scenario 2: Removing user and its telephony resources
Is it possible from FreePBX GUI to reset some LDAP attributes for some LDAP entries ?[1] https://wiki.freepbx.org/display/FPG/User+Management+with+OpenLDAP
Best regards
Posts: 2
Participants: 1
@boubadebf wrote:
the memory of my freepbx fills up quickly I would like a solution to solve this.
Posts: 1
Participants: 1
@waseemly wrote:
Hi
I have developed an IVR using Node JS and the ARI client.
The system originates a call to a field officer depending which options the caller chooses via the IVR.
To test the IVR i am using two soft phones (one for the caller) and one for the field officer.
What i noticed is that if I use an external number (ie my mobile) for the field officer , when I hang up (from mobile) i get the hangup request cause as “undefined” , ie there is no cause in the event passed back to the Node js code. However if i use another soft phone instead i get a cause code
Is this something to do with my Trunk settings or the provider ? Or something else
Thanks for any help
Posts: 1
Participants: 1
@Flurd wrote:
What do I need to do to get Sangoma to setup my PBXact system for me and show me how?
Posts: 3
Participants: 3
@MrXirtam wrote:
FreePBX Version: 14.0.13.23
Asterisk Version: 13.29.2So I utilize Voyant Sip trunks, following their recommended setup exactly (found here Voyant FreePBX Guide). I have a few servers up with different trunks, all no problems, except for this one particular server. Contacted the provider because I was seeing randomly rejected notices from the trunk, of course after the client tells me calls are failing. Fast forward, Voyant tells me that when a call goes in, and they send back a 486 Busy, we respond with an ACK and it has an invalid route line (Route: <sip:…:6000;lr>). That is verbatim, not masked. So when we send that ACK with the invalid route, Voyant disregards it, and it keeps trying and eventually they blacklist our server IP for 30 minutes because they think it’s spam / fraud.
Here is an image they sent me from their side with an example. Again, this only happens with 486 Busy.
Any suggestions on this? I cross checked the trunk setup side by side with another server that is working fine and they all match, minus the authentication information. I’m just not sure where header information can be modified for this particular case.
Thanks!
Posts: 1
Participants: 1
@carriba wrote:
Have fired the usual command line update commands for FreePBX:
sudo fwconsole ma updateall sudo fwconsole reloadThen when logging into the FreePBX web GUI, going to the “Dashboard” tab and incidentally selecting any time span under the “Memory” option of the “FreePBX Statistics” displet, I’m getting a red coloured pop-up window as depicted with:
Haven’t seen these red coloured pop-window in the past, thus not sure if it’s been introduced with the last FreePBX framework update.
With today’s update launched, the FreePBX framework version is now pumped up to 13.0.197.21.
Is this a bug or regression introduced with the latest update?
Posts: 4
Participants: 2
@toan_cr wrote:
I have trouble when i config the queue. I never seen it befor. I have queue 60 and one agent (309) in this queue, but the agent is not avalible(becasuse i turn off the IP Phone). Though when i call to the queue (insite with call direct to queue or outsite call in via DID) , the queue still ring and don’t leave when empty.
#queue show 60
60 has 0 calls (max unlimited) in ‘ringall’ strategy (0s holdtime, 0s talktime), W:0, C:0, A:7, SL:0.0% within 60s
Members:
309 (Local/309@from-queue/n from hint:309@ext-local) (ringinuse enabled) (Not in use) has taken no calls yet
No Callers#asterisk -rx"sip show peers" | grep 309
309/309 (Unspecified) D Yes Yes A 0 UNKNOWN#core show hint 309
309@ext-local : SIP/309&Custom:DND30 State:Idle Presence: Watchers 1about my system:
FreePBX : 14.0.11
Asterisk : 13.22.0
Core : 14.0.25.4
Queues : 14.0.2.25I check everything with ext 309 is normal (not DND, not Followme, not voicemail, not Froward,…)
Please help, i hop somebody help me in this case . I try to fine solution for this problem but it has not been fixed.
Thanks and hope for your soon answer .
Posts: 3
Participants: 2
@carriba wrote:
Have fired the usual command line update commands for FreePBX:
sudo fwconsole ma updateall sudo fwconsole reloadThen when logging into the FreePBX web GUI, going to the “Dashboard” tab and incidentally selecting any time span under the “Memory” option of the “FreePBX Statistics” displet, I’m getting a red coloured pop-up window as depicted with:
Haven’t seen these red coloured pop-window in the past, thus not sure if it’s been introduced with the last FreePBX framework update.
With today’s update launched, the FreePBX framework version is now pumped up to 13.0.197.21.
Is this a bug or regression introduced with the latest update?
Posts: 4
Participants: 2
@mvogel4949 wrote:
I have a system with 5 remote phones. The phones keep going Lagged and Unreachable. I find the following in the logfiles. Asterisk 13.19.1, do these impact phone connection or am I just looking at a crappy connection from the 5 remote phones?
[2020-01-16 07:43:44] WARNING[14437][C-0000016b] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 07:43:44] WARNING[14437][C-0000016b] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 07:43:44] WARNING[14437][C-0000016b] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 07:43:44] WARNING[14438][C-0000016b] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 07:43:44] WARNING[14438][C-0000016b] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 07:43:44] WARNING[14438][C-0000016b] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:33:00] WARNING[18410][C-0000016e] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:33:00] WARNING[18410][C-0000016e] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:33:00] WARNING[18410][C-0000016e] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:33:00] WARNING[18411][C-0000016e] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:33:00] WARNING[18411][C-0000016e] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:33:00] WARNING[18411][C-0000016e] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:57:29] WARNING[20359][C-00000170] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:57:29] WARNING[20359][C-00000170] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:57:29] WARNING[20359][C-00000170] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:57:29] WARNING[20358][C-00000170] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:57:29] WARNING[20358][C-00000170] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 08:57:29] WARNING[20358][C-00000170] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:03:24] WARNING[20880][C-00000172] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:03:24] WARNING[20880][C-00000172] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:03:24] WARNING[20880][C-00000172] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:11:43] WARNING[21513][C-00000173] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:11:43] WARNING[21513][C-00000173] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:11:43] WARNING[21513][C-00000173] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:19:44] WARNING[22476][C-00000174] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:19:44] WARNING[22476][C-00000174] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:19:44] WARNING[22476][C-00000174] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:15] WARNING[22571][C-00000175] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:15] WARNING[22571][C-00000175] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:15] WARNING[22571][C-00000175] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:15] WARNING[22571][C-00000175] taskprocessor.c: The 'subm:endpoint_topic_all-cached-00000008' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:15] WARNING[22571][C-00000175] taskprocessor.c: The 'subm:endpoint_topic_all-cached-00000068' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:31] WARNING[22585][C-00000176] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:31] WARNING[22585][C-00000176] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:31] WARNING[22585][C-00000176] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:31] WARNING[22585][C-00000176] taskprocessor.c: The 'subm:endpoint_topic_all-cached-00000008' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:31] WARNING[22585][C-00000176] taskprocessor.c: The 'subp:SIP/102-00000056' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:20:31] WARNING[22585][C-00000176] taskprocessor.c: The 'subm:endpoint_topic_all-cached-00000068' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:23:17] WARNING[22951][C-00000178] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:23:17] WARNING[22951][C-00000178] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:23:17] WARNING[22951][C-00000178] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:25:07] WARNING[23087][C-00000179] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000064' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:25:07] WARNING[23087][C-00000179] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000065' task processor queue reached 500 scheduled tasks again. [2020-01-16 09:25:07] WARNING[23087][C-00000179] taskprocessor.c: The 'subm:ast_channel_topic_all-cached-00000066' task processor queue reached 500 scheduled tasks again.
Posts: 1
Participants: 1
@darkpixel wrote:
We had a perfectly working FreePBX server a few weeks ago, except it was starting to get overloaded.
We purchased a new, larger server, backed everything up, and then restored to the new phone server.We found out very quickly that a “full backup” apparently doesn’t mean a “full backup”.
A lot of settings weren’t restored properly. One example is incoming routes. We had a handful set to ‘detect faxes’. These were magically flipped into ‘legacy mode’ so faxes were routed incorrectly. We had to manually change ~200 phone lines back to ‘yes’ instead of ‘legacy’…so this problem may be related, but I can’t seem to find it.When people call in, it goes to an IVR that asks them to press 1 if they are a new customer or 2 if they are an existing customer. The options are simply for tracking purposes on our end.
Pressing 1 sends them to a queue–and for the purposes of this issue I’m ignoring this option.
Pressing 2 sends them to a ring group.
The ring group consists of a handful of Digium D60 phones.
Dialing that ring group from my internal phone always works. It always rings the phones, and someone always answers.Calling in from a number of different sources (cell phone, home phone, Google Voice, etc…) will sometimes cause the phones to ring, and other times it immediately jumps to the ring group failover destination which is a time condition. If we are ‘in hours’ it goes to the queue I mentioned earlier. If we are ‘outside of hours’ it goes to voicemail.
It seems to be hit-or-miss, but when the phones in the ring group don’t ring, I will sometimes get dumped into the queue, and other times I will get dumped to voicemail.
Looking at the logs, I see:
== Spawn extension (from-internal, 4001, 1) exited non-zero on 'PJSIP/4002-00005f23' == Spawn extension (from-internal, 4001, 1) exited non-zero on 'PJSIP/4003-00005f24' == Spawn extension (from-internal, 4001, 1) exited non-zero on 'PJSIP/4010-00005f25' == Spawn extension (from-internal, 4001, 1) exited non-zero on 'PJSIP/4020-00005f26'If I immediately dial those extensions or the ring group on my desk phone, the call connects and the phones ring.
Each office has a firewall that is NOT running SIP ALG. UDP timeouts are set to 300 seconds, and nothing firewall-related has changed in months. It’s the same config that was working from before move to a new server. Each office connects out over the internet to our phone server. There is no VPN or ‘internal network’ involved in the phones communicating. The only phones that are on the same network as the phone server is the call center. The call center users are the ones in the queue I referred to previously.
Rebooting phones involves does appear to clear up the issue for a few days, then it comes back…but it still doesn’t explain why the queue will frequently send users directly to voicemail when there are agents signed in and ready to take calls…and calls from other desk phones are able to get through to the queue.
Posts: 2
Participants: 2
@dwsiemens wrote:
This is a issue with some sort of default setting,
if you reload app_voicemail you will get a message in console of
voice*CLI> module reload app_voicemail.so
Module ‘app_voicemail.so’ reloaded successfully.
[2020-01-17 02:35:44] WARNING[39573]: app_voicemail.c:14229 actual_load_config: maxsilence should be less than minsecs or you may get empty messagesIf I go to config edit, the file is not writeable. any thing that I should do to fix the warning?
Posts: 2
Participants: 2
@CraigT wrote:
Hi all,
Wasn’t there a module update for SIP a few days ago ? I have noticed that systems that only use ChanSIP have suddenly started showing the following error in the Full log from about 13 Jan20:ERROR[22850][C-00000000] pbx_functions.c: Function PJSIP_HEADER not registered
They come in blocks of 12 and could be inbound calls. I have been through all the settings and nothing has changed for a couple of years.
Given that PJSIP is not available on these boxes I am a little curious on how to rollback to an older module to check.
Posts: 1
Participants: 1
@mike366 wrote:
Went to reload a module update, got this error, how to fix?
retrieve_conf failed, config cannot be applied (shows as critical error)
Error 255
Posts: 2
Participants: 2
@sentinelace wrote:
Cannot apply config. See error
exit: 255
Unable to continue. Call to undefined function FreePBX\modules\Core\Drivers\version_min() in /var/www/html/admin/modules/core/functions.inc/drivers/PJSip.class.php on line 499 #0 /var/www/html/admin/libraries/Composer/vendor/filp/whoops/src/Whoops/Run.php(383): Whoops\Run->handleError(1, ‘Call to undefin…’, ‘/var/www/html/a…’, 499) #1 [internal function]: Whoops\Run->handleShutdown() #2 {main}
Posts: 6
Participants: 3
