@jacobs wrote:

Sorry maybe a really nooby question but i’m trying to learn how the dial() dialplan function works. Below I am trying to test if I call extension “1” it will dial out to my external cell phone number. When I dial extension “1” on a softphone no action is taken and the call just seems to hang until a timeout is reached. What am I doing that’s stupid here? In dial i’ve passed SIP, my trunk name which is configured correctly, and the number I want to dial (my cell phone). I’ve been able to get other basic commands to work like Playback, SayDigits, etc.

[from-internal-custom]
include = dial-my-number

[dial-my-number]
exten = 1,1,Answer
same = n,Dial(SIP/my_trunk_name/1234567890)

Posts: 1

Participants: 1

Read full topic

@ipvinner wrote:

Hello. I’m trying to use new API module. From Connectivity API we have following info

Client Credentials

Token URL :url/admin/api/api/token
Authorization URL :url/admin/api/api/authorize
GraphQL URL :url/admin/api/api/gql
Rest URL :url/admin/api/api/rest
Client ID :8053a9cdec3370652d9673ee71396934be5e95706b24e700d4c0a834c7b53ec1
Allowed Scopes :rest

Please copy your secret as you will not be able to retrieve it later

Client Secret :46cd058cf8be20431eda700a4be2cb93

I’d like to get token to show rest methods.
POSTMAN
POST request
url/admin/api/api/token
BODY
x-www-form-unlencoded
grant_type=authorization_code??? not sure how to get grant type here(password or code)
client_id=8053a9cdec3370652d9673ee71396934be5e95706b24e700d4c0a834c7b53ec1
client_secret=46cd058cf8be20431eda700a4be2cb93

RESPONSE:
{
“error”: “invalid_client”,
“message”: “Client authentication failed”
}

how to correct way or what’s wrong I did to show list of REST methods?

Posts: 1

Participants: 1

Read full topic

@NorColorNorName wrote:

Hello !

I’m using Asterisk 13.17.0 and FBX 13.0.

I want to configure my FBX to receive php request to create extensions for new user of sipML5.
I said php but i’m open for any other solutions.

My task is to create extensions for new users without the need to reload asterisk.

I heard about virtual extensions, is that a good way to start?

I’m a bit noob with FBX and asterisk but any advices will help,
Thanks by advance,
NCNN.

Posts: 1

Participants: 1

Read full topic

@travisdietrich wrote:

Is there a way to tell what system recordings are in use and where?

I am trying to clean up files from our IVR and I find that if a system recording id in use and deleted, the place in use just reverts to “None” with no warning.

Want to delete some recordings, but don’t want to inadvertently break an announcement somewhere.

(Even a config file I can look thru would be great)

Thanks,

Posts: 3

Participants: 2

Read full topic

@chrischevy wrote:

I need to move a FreePBX to another cloud server. The original FreePBX is version 13 and the new one is version 14. I used the migration tool in the past and I know that it works fine, but I have a question:

The target FreePBX needs to be activated. If I deactivate the source FreePBX to activate the target FreePBX, will it still work ? I can’t remember if I did this when I used the tool in the past.

https://wiki.freepbx.org/display/PPS/Elastix+and+PBXinaFlash+to+FreePBX+Distro+Conversion+Tool

Posts: 3

Participants: 2

Read full topic

@badmin wrote:

We need to remove entries on our FreePBX that are older then six month. I found other topics from 2017 but wanted to make sure that this is still the way to go. Can anybody confirm that?

Create a script called (for example) “DeleteCDR8Mos.sql” in your “asterisk root directory” or in the “root” home directory. The example below assumes it’s in the “/root” directory.

use asteriskcdrdb;
repair table cdr;
repair table cel;
delete from cdr where calldate < DATE_SUB(NOW(), INTERVAL 6 MONTH);
delete from cel where eventtime < DATE_SUB(NOW(), INTERVAL 6 MONTH);
optimize table cdr;
optimize table cel;
exit;

In your crontab on the server (important part, since access to the database is limited to localhost), add something like:

X X X X X X mysql -u root asteriskcdrdb < /root/DeleteCDR8Mos.sql

The “X” entries are there for your time/date/day entries […]

We are running PBX Firmware: 12.7.6-1904-1.sng7 with PBX Service Pack: 1.0.0.0.

Posts: 1

Participants: 1

Read full topic

@GSnover wrote:

[this post and three that follow moved from unrelated thread - mod]

Ok - Quick question - I have just removed the forwarding for Port 80 on all our Hosted Boxes - but provisioning is on port 84 - is it vulnerable? Let’s Encrypt was using Port 80, so I can leave that off for a little while until the dust settles - I am getting the feeling from the thread that Apache is the problem - does provisioning use Apache to serve the files? Is HTTPS vulnerable?

Posts: 7

Participants: 4

Read full topic

@mustachio wrote:

Hello,

I am having a hard time clearing this notification from one of my boxes. I have rebooted it twice, and ran checks on both yum and module updates, and it reports back with “no updates”. GUI does not show any updates either. Is there a command i can run that will clear this box out?

image.png656×653 25.6 KB

Posts: 1

Participants: 1

Read full topic

@fdoula01 wrote:

Hi everyone!

I was running my Freepbx 13 on a Dell PowerEdge R610 hardware with no problems. I tried to upgrade from 13 to 14 and ran into too many problems (mainly NIC card issues with new naming as they said it will likely to happen) that i decided to reformat and install the fresh copy of the Freepbx 14 Distro. After installations and all the configurations and everything done, system was running fine. Till recently, when I could not access the GUI, even though everything is working. and i have to go and do “restart httpd service” command every time i need to access the GUI now. Doing that it will fix the issue but puttying in and doing that every time is a bit annoying. I wanna save myself the hassle. I tried to look up for a solution, but most were complaining about the Apache server not starting or cannot access because of the ban. Mine is just the httpd service keeps going offline and needs a kick in a butt!

Any help or advise is greatly appreciated. I am a novice in Linux but i can find my way around the problem if i am pointed to the right direction.

Any ideas? what am I missing here? i have not done any changes but to occasionally install the updates on the modules that i get warned about.

Thank you so much in advance
Sean

Posts: 1

Participants: 1

Read full topic

@ngingras wrote:

Hello,

I’ve received a report from a customer that when they park a call on their primary device it rings back to their secondary device once the timeout is reached. This is on 12.7.6-1904-1.sng7 with Asterisk 13.22

I’ve had a tech onsite to confirm this, and can’t see anything in the config that would impact this. Anyone encountered and/or solved this problem before?

Take care,

Nate

Posts: 1

Participants: 1

Read full topic

@RealRuler2112 wrote:

This is going to be a very long shot since Lorne wasn’t able to resolve it & he seemed very, very knowledgeable.

In short, I have two PBXact 13 appliances configured in HA mode. Due to our users familiarity and comfort level with our existing Cisco phones and overall cost involved with replacing 70+ phones, it was decided to keep the old Cisco 7960 phones, flash them to SIP, and utilize them with our new phone system for the majority of our phones; basically, managers & our call center got Sangoma phones - everyone else has a 7960. After I figured out how to do this, setting them up went relatively smoothly. (Figuring out how to flash them & the exact config file structure/content the phones needed was the hard part. On a side-note, would anyone be interested in a how-to style guide on how to do this?) Being old, they provision using TFTP and I have option 66 enabled on our DHCP server to point them to the cluster IP address. This went well and the phones work as expected with PBXact.

However, while configuring the server, I noticed something very odd.

Whenever I factory reset a 7960 to remove all settings from it, it will not pull it’s config from PBXact. I can see the TFTP connection coming into the server using a packet sniffer, but the server refuses to respond and there’s nothing in /var/log/messages from the tftp daemon, even though verbose logging is turned on. If I disable the firewall temporarily from the command line (service iptables stop), the phone receives it’s configuration and registers perfectly. The firewall restarts after a 5-7 second delay, but this is more than enough time for the phone to pull it’s config. After a given phone has registered once, it can then boot up normally without needing to disable the firewall to let it through. If a functional phone is factory reset though, it is again not allowed through the firewall and refuses to pull it’s configuration until I manually disable the firewall.

If I change the eth0 to ‘Local (trusted traffic)’ instead of ‘Internet (default firewall)’ under Firewall->Main->Interfaces, this problem does not present itself. Obviously, this is not something I wish to run with long-term. I have already set the phone subnet /24 to be ‘Local (trusted traffic)’ under Firewall->Main->Networks, but this does not seem to have any effect - the ENTIRE interface needs to be set to ‘Local (trusted traffic)’ in order for the phones to provision.

I tried disabling the responsive firewall in Firewall->Main->Responsive Firewall, but this had no effect either - the entire firewall needs to be disabled or have eth0 be set to Local in order for them to provision. I also set TFTP to be allowed in the Internet zone in Firewall->Services->Extra Services, but alas this did not change the symptoms either. There are 0 ‘Rate Limited’ or ‘Blocked Attackers’ shown in Firewall->Status->Blocked Hosts. I also added the entire subnet to the whitelisted clients under System Admin->Intrusion Detection on the off-chance that this is what was causing it.

The last thing I tried was to upgrade the firewall module from 13.0.57.1 that was on the system when installed to edge release 13.0.60.2, then re-save & apply, but again this had no impact.

After opening a support ticket, Lorne found out that apparently, I’m affected by a bug that’s supposed to be fixed already:

https://issues.freepbx.org/browse/FREEPBX-14483

Unfortunately, nobody seems to know how it was fixed in the past. I tried loading the TFTP connection tracking module as the bug report suggests, but this had 0 impact on the issue.

Thankfully, my PBXact system is protected by a Meraki edge device, so I can use that to shield it from the internet & leave the entire interface configured as being completely trusted/local. (It was this or disable the firewall entirely.) I would much rather have the firewall on & functioning as it should to provide another layer of protection, but simply do not have the knowledge/experience to do so; the fact that I set TFTP to be allowed in the Internet zone and it still won’t work makes me think there’s a flaw in the GUI or firewall rule generation. Lorne went back & forth with R&D and a decision was made to not spend any more time on it.

I was wondering if anyone here has experienced this, has a solution, or is a wizard at iptables and could perhaps provide an auxiliary rule that might alleviate this issue. (Frankly, it’s been years since I used iptables; I use BSD for most of our servers & so know/like pf MUCH more; it’s so much simpler and easier IMO. Looking at the iptables output on the PBX makes me slightly dizzy… )

Posts: 1

Participants: 1

Read full topic

@bajramia wrote:

Hi All,
I have a customer who i have setup a warm spare and backing up nightly we are having issue with ghost voicemails, if en extension receive a voicemail and haven’t read when back up runs that voicemail moves to the other server and phones receiving alerts from standby you have a new voicemail when customer checks it says you dont have no voicemail.

Thank you

Posts: 6

Participants: 2

Read full topic

@mikeaph wrote:

Experiencing a strange issue that is completely random.

I have FreePBX running on a PC, on premise. I have no audio issues when I call out or when people call in. However, on a regular basis, when I, or any of our users, call out to someone’s cell phone and get their voicemail, the voicemail does not recognize that anyone is speaking. One of two things happens depending on the number we are calling that we are calling (Verizon, T-mobile, Spint, etc.); the call hangs up after 30 seconds or so because it thinks no one is there, or, the voicemail system will cut you off while you are leaving a message telling you that no message has been recoded because we are not speaking. I have also noticed that when this happens, if I hit # or any other key, the voicemail system does not recognize the key press. So either the call is disconnected or we hang-up and then call the number right back and this time it will work with no problems. The voicemail will answer and I am able to leave a message.

I have been able to duplicate this issue on two other systems. Both of those systems are FreePBX running in the cloud on a Vultr. And the exact same scenario occurs.

I can literally call a phone number, get the persons voicemail and leave a message with no problem, or call the same number and experience the issue that I described above. Then, call the number again and it will work with no issue.

I have no clue if this is a FreePBX issue, firewall issue, trunking issue (using Flowroute on all)…

Considering that they are different instances of FreePBX, different hardware and different firewalls, I’m not sure what the problem could be.

Posts: 5

Participants: 3

Read full topic

@wassy83 wrote:

Hi to all,
I have a freepbx box over a mikrotik ipsec/l2tp VPN.
pbx is 192.168.25.200
my side is 192.168.25.0/24 through l2tp ip 10.0.25.1
remote side is 192.168.26.0/24 through l2tp ip 10.0.25.2
I can ping from remote side the pbx and all phones are correctly registered with no issues, but I cannot access from remote side any services like ssh or web gui. I tried to disable any possible firewall rules on both mikrotik and freepbx side without success, I also tried to add into freepbx firewall any public or local related ip, but still cannot access, but as I said things are working

I’m thinking that maybe this is related on some returning route but I think is impossibile cause freepbx is the only service that I cannot reach from the remote side, any other ssh server will work and furthermore ping is returning back!

The strange think is that if I tried to connect over openvpn to my side mikrotik I can easly reach the pbx webui.

I tried a tcp dump command like this to see what happens on my freepbx

tcpdump port 80 and ‘(tcp-syn|tcp-ack)!=0’

and I cleraly see this traffic on my freepbx when trying to connect to web gui from remote side

10:49:48.471536 IP 192.168.26.131.59248 > freepbx.sangoma.local.http: Flags [S], seq 3877414963, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:48.471612 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:48.471627 IP 192.168.26.131.59249 > freepbx.sangoma.local.http: Flags [S], seq 8771055, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:48.471637 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:48.722735 IP 192.168.26.131.59250 > freepbx.sangoma.local.http: Flags [S], seq 478317604, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:48.722761 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:49.571546 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:49.771546 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:49.771563 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:51.471685 IP 192.168.26.131.59248 > freepbx.sangoma.local.http: Flags [S], seq 3877414963, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:51.471738 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:51.471766 IP 192.168.26.131.59249 > freepbx.sangoma.local.http: Flags [S], seq 8771055, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:51.471782 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:51.722491 IP 192.168.26.131.59250 > freepbx.sangoma.local.http: Flags [S], seq 478317604, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:51.722540 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:53.571536 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:53.771545 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:53.771577 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:57.471386 IP 192.168.26.131.59248 > freepbx.sangoma.local.http: Flags [S], seq 3877414963, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:57.471458 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:57.472498 IP 192.168.26.131.59249 > freepbx.sangoma.local.http: Flags [S], seq 8771055, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:57.472515 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:49:57.723069 IP 192.168.26.131.59250 > freepbx.sangoma.local.http: Flags [S], seq 478317604, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:49:57.723104 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:01.571537 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:01.771530 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:01.771561 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:09.571525 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:09.720075 IP 192.168.26.131.59252 > freepbx.sangoma.local.http: Flags [S], seq 422826850, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:09.720144 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:09.771536 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:09.840517 IP 192.168.26.131.59253 > freepbx.sangoma.local.http: Flags [S], seq 4129128216, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:09.840544 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:09.971549 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:10.771583 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:10.971537 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:12.720818 IP 192.168.26.131.59252 > freepbx.sangoma.local.http: Flags [S], seq 422826850, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:12.720892 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:12.840522 IP 192.168.26.131.59253 > freepbx.sangoma.local.http: Flags [S], seq 4129128216, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:12.840547 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:14.771555 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:14.971541 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:18.721456 IP 192.168.26.131.59252 > freepbx.sangoma.local.http: Flags [S], seq 422826850, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:18.721551 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:18.840164 IP 192.168.26.131.59253 > freepbx.sangoma.local.http: Flags [S], seq 4129128216, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:18.840195 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:22.772556 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:23.172543 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:25.572549 IP freepbx.sangoma.local.http > 192.168.26.131.59249: Flags [S.], seq 1362958868, ack 8771056, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:25.972536 IP freepbx.sangoma.local.http > 192.168.26.131.59250: Flags [S.], seq 4252251233, ack 478317605, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:25.972551 IP freepbx.sangoma.local.http > 192.168.26.131.59248: Flags [S.], seq 109440904, ack 3877414964, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:30.772553 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:31.172592 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:35.744756 IP 192.168.26.131.59255 > freepbx.sangoma.local.http: Flags [S], seq 3939391748, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:35.744846 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:35.745396 IP 192.168.26.131.59256 > freepbx.sangoma.local.http: Flags [S], seq 1099449442, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:35.745417 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:35.994955 IP 192.168.26.131.59257 > freepbx.sangoma.local.http: Flags [S], seq 2434359832, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:35.995029 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:36.972573 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:36.972605 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:37.372564 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:38.744536 IP 192.168.26.131.59255 > freepbx.sangoma.local.http: Flags [S], seq 3939391748, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:38.744608 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:38.745168 IP 192.168.26.131.59256 > freepbx.sangoma.local.http: Flags [S], seq 1099449442, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:38.745183 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:38.997023 IP 192.168.26.131.59257 > freepbx.sangoma.local.http: Flags [S], seq 2434359832, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:38.997053 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:40.972548 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:41.172554 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:41.372527 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:44.745424 IP 192.168.26.131.59255 > freepbx.sangoma.local.http: Flags [S], seq 3939391748, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:44.745485 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:44.745513 IP 192.168.26.131.59256 > freepbx.sangoma.local.http: Flags [S], seq 1099449442, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:44.745521 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:44.997053 IP 192.168.26.131.59257 > freepbx.sangoma.local.http: Flags [S], seq 2434359832, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:50:44.997110 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:46.972563 IP freepbx.sangoma.local.http > 192.168.26.131.59252: Flags [S.], seq 1588306684, ack 422826851, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:47.172528 IP freepbx.sangoma.local.http > 192.168.26.131.59253: Flags [S.], seq 1751636961, ack 4129128217, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:48.972560 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:49.172561 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:49.572553 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:57.172547 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:57.172573 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:50:57.572533 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:13.172557 IP freepbx.sangoma.local.http > 192.168.26.131.59255: Flags [S.], seq 1432836671, ack 3939391749, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:13.172575 IP freepbx.sangoma.local.http > 192.168.26.131.59256: Flags [S.], seq 1270498086, ack 1099449443, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:13.572548 IP freepbx.sangoma.local.http > 192.168.26.131.59257: Flags [S.], seq 3319616153, ack 2434359833, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:26.761336 IP 192.168.26.131.59261 > freepbx.sangoma.local.http: Flags [S], seq 1435327049, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:26.761432 IP freepbx.sangoma.local.http > 192.168.26.131.59261: Flags [S.], seq 4024768948, ack 1435327050, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:26.761445 IP 192.168.26.131.59262 > freepbx.sangoma.local.http: Flags [S], seq 3416228626, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:26.761455 IP freepbx.sangoma.local.http > 192.168.26.131.59262: Flags [S.], seq 622931806, ack 3416228627, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:27.011849 IP 192.168.26.131.59263 > freepbx.sangoma.local.http: Flags [S], seq 3681864362, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:27.011875 IP freepbx.sangoma.local.http > 192.168.26.131.59263: Flags [S.], seq 2416441355, ack 3681864363, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:27.972558 IP freepbx.sangoma.local.http > 192.168.26.131.59262: Flags [S.], seq 622931806, ack 3416228627, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:28.172554 IP freepbx.sangoma.local.http > 192.168.26.131.59261: Flags [S.], seq 4024768948, ack 1435327050, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:28.372531 IP freepbx.sangoma.local.http > 192.168.26.131.59263: Flags [S.], seq 2416441355, ack 3681864363, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:29.761439 IP 192.168.26.131.59261 > freepbx.sangoma.local.http: Flags [S], seq 1435327049, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:29.761464 IP freepbx.sangoma.local.http > 192.168.26.131.59261: Flags [S.], seq 4024768948, ack 1435327050, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:29.765103 IP 192.168.26.131.59262 > freepbx.sangoma.local.http: Flags [S], seq 3416228626, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:29.765127 IP freepbx.sangoma.local.http > 192.168.26.131.59262: Flags [S.], seq 622931806, ack 3416228627, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:30.013382 IP 192.168.26.131.59263 > freepbx.sangoma.local.http: Flags [S], seq 3681864362, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:30.013412 IP freepbx.sangoma.local.http > 192.168.26.131.59263: Flags [S.], seq 2416441355, ack 3681864363, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:31.972545 IP freepbx.sangoma.local.http > 192.168.26.131.59262: Flags [S.], seq 622931806, ack 3416228627, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:32.172535 IP freepbx.sangoma.local.http > 192.168.26.131.59261: Flags [S.], seq 4024768948, ack 1435327050, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:32.372491 IP freepbx.sangoma.local.http > 192.168.26.131.59263: Flags [S.], seq 2416441355, ack 3681864363, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:35.761006 IP 192.168.26.131.59261 > freepbx.sangoma.local.http: Flags [S], seq 1435327049, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:35.761044 IP freepbx.sangoma.local.http > 192.168.26.131.59261: Flags [S.], seq 4024768948, ack 1435327050, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:35.765687 IP 192.168.26.131.59262 > freepbx.sangoma.local.http: Flags [S], seq 3416228626, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:35.765711 IP freepbx.sangoma.local.http > 192.168.26.131.59262: Flags [S.], seq 622931806, ack 3416228627, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:36.013497 IP 192.168.26.131.59263 > freepbx.sangoma.local.http: Flags [S], seq 3681864362, win 64240, options [mss 1410,nop,wscale 8,nop,nop,sackOK], length 0
10:51:36.013522 IP freepbx.sangoma.local.http > 192.168.26.131.59263: Flags [S.], seq 2416441355, ack 3681864363, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:39.973536 IP freepbx.sangoma.local.http > 192.168.26.131.59262: Flags [S.], seq 622931806, ack 3416228627, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:40.173544 IP freepbx.sangoma.local.http > 192.168.26.131.59261: Flags [S.], seq 4024768948, ack 1435327050, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:40.573510 IP freepbx.sangoma.local.http > 192.168.26.131.59263: Flags [S.], seq 2416441355, ack 3681864363, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:47.973529 IP freepbx.sangoma.local.http > 192.168.26.131.59262: Flags [S.], seq 622931806, ack 3416228627, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:48.173535 IP freepbx.sangoma.local.http > 192.168.26.131.59261: Flags [S.], seq 4024768948, ack 1435327050, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:51:48.573526 IP freepbx.sangoma.local.http > 192.168.26.131.59263: Flags [S.], seq 2416441355, ack 3681864363, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:52:00.389388 IP 192.168.25.79.13512 > freepbx.sangoma.local.http: Flags [S], seq 1991768228, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
10:52:00.389427 IP freepbx.sangoma.local.http > 192.168.25.79.13512: Flags [S.], seq 3945284748, ack 1991768229, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
10:52:00.389440 IP 192.168.25.79.13513 > freepbx.sangoma.local.http: Flags [S], seq 3612611044, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
10:52:00.389455 IP freepbx.sangoma.local.http > 192.168.25.79.13513: Flags [S.], seq 2205060571, ack 3612611045, win 29200, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0

any suggestions?
many thanks

Posts: 1

Participants: 1

Read full topic

@jamesg224 wrote:

Background info:
I’ve been running FreePBX for just over a year now and it has been incredibly stable with SIP trunks (no POTS). There are no ports forwarded as I am using SIP registration. Established/related traffic is allowed for time/system/firmware updates etc. Otherwise everything is on a private LAN behind a firewall.

Question:
This week I have been asked to connect a POTS line so that anyone who calls this legacy number will still get through until the contract runs out. Previously we were just using one separate phone. During testing the system connectivity between the SPA-3102 and the PBX, everything is fine. As soon as I connect the POTS line to the SPA-3102, I am receiving IPS messages from my firewall (current Unifi USG). This has occurred twice, both times about 10 minutes after connecting the SPA to the line. Since I have started using FreePBX, there have been no other IPS hits so this is new behaviour.

This is my IPS message:
Message: IPS Alert 2: Misc Attack. Signature ET TOR Known Tor Relay/Router (Not Exit) Node Traffic group 276. From: 193.224.163.43:11371, to: mypbxaddress:48860, protocol: TCP

As far as I know port 48860 is not in use for anything so I’m puzzled as to what this could be (it could also just be a false positive!). Any input would be greatly appreciated. Thanks.

Posts: 2

Participants: 2

Read full topic

@dotcomm wrote:

Hello,

When trying to record a new system recording via FreePBX, it fails and shows in the logs:

-- Executing [s@macro-user-callerid:34] Gosub("Local/445@from-internal-000001f3;2", "macro-user-callerid,lang-playback,1(hook_1)") in new stack
-- Executing [lang-playback@macro-user-callerid:1] GosubIf("Local/445@from-internal-000001f3;2", "1?macro-user-callerid,en,hook_1():macro-user-callerid,en,hook_1()") in new stack
-- Executing [en@macro-user-callerid:3] Playback("Local/445@from-internal-000001f3;2", "beep&im-sorry&your&simul-call-limit-reached&goodbye") in new stack

It’s the same notification as you see when you are trying to dial with a device where no user is linked to it. (We have a devices & users setup.)

Just before the issue showed up, I was playing with the commands “database del AMPUSER & database put DEVICE/xxx user none”… so I think I may have deleted too much.

I already did a force download & install of the system recordings module, without luck.

Any of you guys have an idea to fix it?

Thanks for your help!

Posts: 1

Participants: 1

Read full topic

@jacobs wrote:

I have written some custom dialplan that allows passing in a set of numbers with a * between them. The issue is that when a softphone dials the custom number and hits the dialplan the call is not recorded. I have tried setting call recording to forced my trunk, outbound route, and softphone extension with no luck. When dialing in using DISA if I dial the custom dialplan code manually the call successfully records. Any idea why the softphone call might not be recording?

Posts: 1

Participants: 1

Read full topic

@bajramia wrote:

Hi All,
we are deploying about 600 extension throughout our hospital i want to ask question about endpoint manager templates,
I need to setup templates for area and I did but i only can make one internal default so how do i pick a template i want for the phone from the floor.
this is how I’m thinking to deploy the phones i have 600 IP phones Snagoma 705 we start with one area open the phone plug in the network login in with extension.
Question is can i have a template for VLAN or any other way to differentiate templates based on area they are deployed.

Thank you
ALL

Posts: 1

Participants: 1

Read full topic

@manimo wrote:

Dear FreePBX community!

I have 4 locations that I would like to connect with VOIP. Geographically, I am based in Europe with 3 of the locations being in one country and the 4th - could be considered the HQ in a different one. 3 locations have regular copper internet connections with unlimited data, while one uses a 4G cellular signal. I would also prefer all communications to be encrypted and if that means increasing the upfront cost by choosing more powerful CPUs I would be willing to do so.

On stage 1 of this project I would like to achieve the following:

Installing 1-3 phones at HQ and a 2nd location. Using an ATA FXO device/converter to connect an existing POTS line at location 2 to the system, so I can avoid paying for international calling from my HQ to the country with the 3 other locations.

Stage 2:

I would like to add the ability to use my POTS line at location 2 from anywhere with an iPhone

Stage 3: adding the remaining two locations(with 1-3 phones) and perhaps adding a two more POTS lines one at HQ and one at one of the locations.

I have some knowledge about FreePBX thanks to youtube videos. I’m assuming that I would need to setup VPNs between the 4 locations and have a central FreePBX server at the HQ. I’m assuming that this needs to be setup using the routers at each of these location, currently I’m using an edge router at HQ and basic router AP combos at the other locations, however I have considered upgrading all locations to Ubiquiti USGs as these would seem to be easier to manage remotely.

I would like to ask for help for choosing the correct infrastructure and software and hardware to achieve these goals.

Please excuse me, if I made any technical mistakes or posted this in the wrong subforum. Thank you in advance for your help

Posts: 1

Participants: 1

Read full topic

@VOIPDummy wrote:

My FreePBX subscribes to external MWI notifications with a line in SIP_gen_custom like this:
mwi => 1234:password@sip.anveo.com:5010/301

This works for an hour, until the subscription expires. Then the VOIP provider sends a notification that includes this:
Subscription-State: terminated;reason=timeout

Asterisk replies with a Bad Event like this:
Status-Line: SIP/2.0 489 Bad event

After that, Asterisk does not re-subscribe and does not receive MWI notifications until I do a reload or a restart.

Has anyone run into this before? Anyone have any ideas on how to solve it? I can’t find anything about this on any FreePBX or Asterisk sites, I’m stumped. Need help from someone smarter than I am.

Thanks.
Peter

Posts: 2

Participants: 2

Read full topic