@dan_ce wrote:

Is anyone doing ethernet/wifi bridging with ZeroTier INSTEAD of doing VPN or port forwarding to their FreePBX instance? I would like to do it to enable a remote site’s ATA access to my FreePBX box…

Posts: 1

Participants: 1

Read full topic

@dan_ce wrote:

Is it possible to do the above?

Either to a schedule (like wake up calls) or based on a command line command (like how you can do with ‘call flow control’)

Use case: For an elderly member of the household to be able to use a physical push button to send an MQTT command to the host Pi that causes an extension to ring. When the extension is answered, it begins dialling a preset number.

Posts: 1

Participants: 1

Read full topic

@shivansos wrote:

This is driving me crazy as it makes no sence to me, i recently got a sip trunk from a local provider, before then i was using FreePBX with analogs ATA and PTSN lines. Now im trying to get a sip trunk working in an attempt to replace PTSN lines but i cant make it work stable.

This was the example config given by the provider:

Register => username@dnsname:password@dnsname

[username] (not placed this one, this is direct for asterisk config i belive)
type=friend
username= username
context= from-trunk
canreinvite=no
fromuser= username
secret= password
host=dnsname
insecure=invite
dtmfmode=rfc2833
disallow=all
;;;;CODECS IPT TRUNK
allow=ilbc
allow=g726
allow=gsm
;;;;CODECS ATI TRUNK
allow=alaw
qualify=yes
sendrpid=yes
trustrpid=yes

I a setup a chan_sip using those settings on outgoing and the register string on incoming.

It worked the FIRST TIME (actually im not sure if i setup everything correctly the first time), BUT then the internet went out and it NEVER RECONECTED AGAIN, the peer was “unreachable” and sip registration was “timed out”.

I played along with my router settings (mikrotik) beliving it may be a NAT issue, nope i could not pinpoint the issue, BUT i managed to place firewall rules to watch for outgoing and incoming packets to the sip server, and the server does not reply, i get not incoming packets from that ip, i can also se active conections and i see a conection from my freepbx server ip : 5160 port to sip server on 5060 port, with 0kb on RX meaning again, no reply.

With no way to figure this out i tryied to setup as PJSIP… to me suprise it worked… at first. But as PJSIP it is a similar issue, it goes unavalible with not inbound or inbounds calls for example last night it was working, right now it is not, i bet later on the day it will work again…

I really having a hard time figuring this out… not sure if is a misconfiguration OR it is just a network issue or the router blocking it.

Any help on how i could debug this?

Posts: 1

Participants: 1

Read full topic

@Mowser wrote:

Hi everyone. I know that oneway audio has been discussed alot in loads of other threads, but I have read through them all and none of them managed to help! I’ve been using FreePBX for years now, but only for systems that use FXO cards. I’ve now just taken on setting up a SIP Trunk becuase of the VoIP takeover.

Before posting logs or screenshots, here’s my setup. I have FreePBX running on a Promox VM. My router is a PFSense box (I think this is where my promblem is). I have two way audio between extensions, and I can dial out through the trunk and they can hear me at the other end, but I can’t hear them. I also can’t dial into the trunk.

I’ve followed every tutorial on how to configure PFSense as there has been issues with source port rewriting, but none of them seem to help. I’m not suspicious of my VM. Does anyone run FreePBX on Proxmox successfully?

I’ll gather some logs now if anyone out there is able to point me in the direction of a solution! Many thanks to everyone!

Posts: 2

Participants: 2

Read full topic

@bwLA wrote:

Hello - I have FreePBX on Raspberry Pi (raspbx) with latest upgrades using PJSIP. The device is a Yealink SIP-T40G set up for encrypted communications (TLS and SRTP). The wireshark shows what appears to be a successful TLS handshake. After but then the the FreePBX sends TLS “Finished” message it then sends TCP FIN and appears to end the connection.

TLS_handshake.jpg1582×351 188 KB

One known issue with my setup is that the framework module is disabled. I am having difficulty getting it upgraded and I am hoping it is not the source of the problem.

I have rechecked many points of my SIP and TLS configuration. I am not seeing any error messages or any useful log data. Can someone please steer me at some first steps at finding where the failure is?

Thanks!

Posts: 1

Participants: 1

Read full topic

@eric99wj wrote:

I’m having an issue with connecting to another IVR. I have a FreePBX system at a new office we are opening and our main office has an old Nortel PBX in place. What I am trying to do is when a user enters an option on the FreePBX IVR, I want to route that call to our main office IVR then pause for a split second then dial a 4 digit extension to match the hunt group on the Nortel to rout the call to the right group. for example call comes into freepbx, hits IVR, user dials option 2, free pbx then sends the call to the Nortel main number which hits the nortel IVR. then i would like freepbx to dial 1324 to get the call to the Nortel hunt group that matches the option they need. I have a misc destination setup currently, but cant figure out what i need to enter to get it to dial the 4 digit hunt group number. Any help would be appreciated!

Posts: 2

Participants: 2

Read full topic

@kr0490 wrote:

I pulled a CDR report on my PBX, and note i rarely make or receive calls on this system. Im trying to understand what all these results i am seeing in the CDR are. Is my PBX compromised?

Posts: 3

Participants: 2

Read full topic

@macjacfish wrote:

I rarely need to shutdown Vm’s running FreePBX but often reboot them. Reboot is working fine but I noticed while doing some routine maintenance that my Freepbx 14 Vm’s do not completely power off after issuing the sudo halt command. Seems to work with ESXI 6.7. Has anyone else had this issue and possibly have a suggestion. VMWare Tools is running of course.

Thanks!

Posts: 1

Participants: 1

Read full topic

@systemsageit wrote:

Hi Team,

We are having issue when call through NAT Router, We are having Pfsense with siproxd , through this proxy the voice (incoming and outgoing )is working fine.

Below find my trunk details

These are my trunk details.
type=friend
secret=xxxxxxxxxx
username=1111111111
host=domain.tld
dtmfmode=rfc2833
context=from-trunk
canreinvite=no
allow=ulaw&g729
insecure=port,invite
fromdomain=domain.tld

We have another server which is having exact same configuration but that server is working fine but the difference is working server is having older Freepbx version.

Posts: 1

Participants: 1

Read full topic

@LesD wrote:

Got a call with some issues with a system. It showed that pm2 was Disabled: Pending Upgrade to 13.0.7.1

Ditto for two other modules that depended on pm2.

Tried to install pm2 and the install failed.

Looks like there has been some automatic updating going on. It keeps retrying to do this each morning.

The critical lines in the logs in /home/asterisk/.npm/_logs seem to be:

113 error code UNABLE_TO_VERIFY_LEAF_SIGNATURE
114 error errno UNABLE_TO_VERIFY_LEAF_SIGNATURE
115 error request to https://registry.npmjs.org/needle/-/needle-2.1.0.tgz failed, reason: unable to verify the first certificate

Full log:

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’,
1 verbose cli ‘/usr/bin/npm’,
1 verbose cli ‘install’,
1 verbose cli ‘–only=production’ ]
2 info using npm@5.6.0
3 info using node@v8.11.3
4 verbose npm-session e45d8a99517ca27c
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall pm2@0.0.1
7 info lifecycle pm2@0.0.1~preinstall: pm2@0.0.1
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 silly install loadShrinkwrap
13 silly install loadAllDepsIntoIdealTree
14 http fetch GET 304 http://mirror1.freepbx.org/npm/pm2-2.10.6.tgz 811ms (from cache)
15 silly pacote remote manifest for pm2@http://mirror1.freepbx.org/npm/pm2-2.10.6.tgz fetched in 972ms
16 silly resolveWithNewModule pm2@2.10.6 checking installable status
17 warn registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning UNABLE_TO_VERIFY_LEAF_SIGNATURE: request to https://registry.npmjs.org/blessed failed, reason: unable to verify the first certificate
18 warn registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
19 http fetch GET 200 https://registry.npmjs.org/blessed 500ms (from cache)
20 http fetch GET 200 https://registry.npmjs.org/async 508ms (from cache)
21 http fetch GET 200 https://registry.npmjs.org/chokidar 503ms (from cache)
22 http fetch GET 200 https://registry.npmjs.org/cli-table-redemption 503ms (from cache)
23 http fetch GET 200 https://registry.npmjs.org/chalk 517ms (from cache)
24 http fetch GET 200 https://registry.npmjs.org/commander 521ms (from cache)
25 http fetch GET 200 https://registry.npmjs.org/debug 542ms (from cache)
26 silly pacote range manifest for async@^2.5 fetched in 591ms
27 silly resolveWithNewModule async@2.6.2 checking installable status
28 http fetch GET 200 https://registry.npmjs.org/cron 557ms (from cache)
29 silly pacote range manifest for chokidar@^2 fetched in 577ms
30 silly resolveWithNewModule chokidar@2.1.2 checking installable status
31 silly pacote range manifest for blessed@^0.1.81 fetched in 586ms
32 silly resolveWithNewModule blessed@0.1.81 checking installable status
33 silly pacote version manifest for commander@2.13.0 fetched in 580ms
34 silly resolveWithNewModule commander@2.13.0 checking installable status
35 silly pacote range manifest for cli-table-redemption@^1.0.0 fetched in 585ms
36 silly resolveWithNewModule cli-table-redemption@1.0.1 checking installable status
37 silly pacote range manifest for chalk@^1.1 fetched in 600ms
38 silly resolveWithNewModule chalk@1.1.3 checking installable status
39 http fetch GET 200 https://registry.npmjs.org/fclone 595ms (from cache)
40 http fetch GET 200 https://registry.npmjs.org/eventemitter2 598ms (from cache)
41 silly pacote range manifest for cron@~1.3.0 fetched in 606ms
42 silly resolveWithNewModule cron@1.3.1 checking installable status
43 silly pacote range manifest for debug@^3.0 fetched in 611ms
44 silly resolveWithNewModule debug@3.2.6 checking installable status
45 silly pacote version manifest for eventemitter2@1.0.5 fetched in 693ms
46 silly resolveWithNewModule eventemitter2@1.0.5 checking installable status
47 silly pacote version manifest for fclone@1.0.11 fetched in 720ms
48 silly resolveWithNewModule fclone@1.0.11 checking installable status
49 http fetch GET 200 https://registry.npmjs.org/moment 317ms (from cache)
50 http fetch GET 200 https://registry.npmjs.org/mkdirp 339ms (from cache)
51 http fetch GET 200 https://registry.npmjs.org/nssocket 356ms (from cache)
52 silly pacote range manifest for moment@^2.19 fetched in 374ms
53 silly resolveWithNewModule moment@2.24.0 checking installable status
54 silly pacote version manifest for mkdirp@0.5.1 fetched in 393ms
55 silly resolveWithNewModule mkdirp@0.5.1 checking installable status
56 http fetch GET 200 https://registry.npmjs.org/needle 373ms (from cache)
57 http fetch GET 200 https://registry.npmjs.org/pm2-axon 374ms (from cache)
58 http fetch GET 200 https://registry.npmjs.org/pidusage 382ms (from cache)
59 http fetch GET 200 https://registry.npmjs.org/pm2-axon-rpc 363ms (from cache)
60 silly pacote version manifest for nssocket@0.6.0 fetched in 396ms
61 silly resolveWithNewModule nssocket@0.6.0 checking installable status
62 http fetch GET 200 https://registry.npmjs.org/pm2-deploy 371ms (from cache)
63 http fetch GET 200 https://registry.npmjs.org/pm2-multimeter 302ms (from cache)
64 silly pacote version manifest for pm2-axon@3.1.0 fetched in 416ms
65 silly resolveWithNewModule pm2-axon@3.1.0 checking installable status
66 silly pacote range manifest for pm2-axon-rpc@^0.5.1 fetched in 403ms
67 silly resolveWithNewModule pm2-axon-rpc@0.5.1 checking installable status
68 silly pacote range manifest for pidusage@^1.2.0 fetched in 433ms
69 silly resolveWithNewModule pidusage@1.2.0 checking installable status
70 silly pacote range manifest for pm2-deploy@^0.3.9 fetched in 426ms
71 silly resolveWithNewModule pm2-deploy@0.3.10 checking installable status
72 silly pacote range manifest for pm2-multimeter@^0.1.2 fetched in 361ms
73 silly resolveWithNewModule pm2-multimeter@0.1.2 checking installable status
74 http fetch GET 200 https://registry.npmjs.org/pmx 365ms (from cache)
75 silly fetchPackageMetaData error for needle@2.1.0 request to https://registry.npmjs.org/needle/-/needle-2.1.0.tgz failed, reason: unable to verify the first certificate
76 silly pacote range manifest for pmx@^1.6 fetched in 436ms
77 silly resolveWithNewModule pmx@1.6.7 checking installable status
78 http fetch GET 200 https://registry.npmjs.org/promptly 267ms (from cache)
79 http fetch GET 200 https://registry.npmjs.org/semver 253ms (from cache)
80 http fetch GET 200 https://registry.npmjs.org/shelljs 234ms (from cache)
81 silly pacote version manifest for promptly@2.2.0 fetched in 288ms
82 silly resolveWithNewModule promptly@2.2.0 checking installable status
83 silly pacote range manifest for semver@^5.3 fetched in 276ms
84 silly resolveWithNewModule semver@5.6.0 checking installable status
85 silly pacote version manifest for shelljs@0.7.8 fetched in 262ms
86 silly resolveWithNewModule shelljs@0.7.8 checking installable status
87 http fetch GET 200 https://registry.npmjs.org/source-map-support 227ms (from cache)
88 http fetch GET 200 https://registry.npmjs.org/v8-compile-cache 236ms (from cache)
89 http fetch GET 200 https://registry.npmjs.org/sprintf-js 251ms (from cache)
90 silly pacote range manifest for v8-compile-cache@^1.1.0 fetched in 257ms
91 silly resolveWithNewModule v8-compile-cache@1.1.2 checking installable status
92 silly pacote range manifest for source-map-support@^0.5 fetched in 261ms
93 silly resolveWithNewModule source-map-support@0.5.10 checking installable status
94 http fetch GET 200 https://registry.npmjs.org/vizion 241ms (from cache)
95 silly pacote version manifest for sprintf-js@1.1.1 fetched in 281ms
96 silly resolveWithNewModule sprintf-js@1.1.1 checking installable status
97 http fetch GET 200 https://registry.npmjs.org/yamljs 242ms (from cache)
98 silly pacote range manifest for vizion@^0.2 fetched in 251ms
99 silly resolveWithNewModule vizion@0.2.13 checking installable status
100 silly pacote range manifest for yamljs@^0.3.0 fetched in 247ms
101 silly resolveWithNewModule yamljs@0.3.0 checking installable status
102 http fetch GET 200 https://tgz.pm2.io/gkt-1.0.0.tgz 613ms (from cache)
103 silly pacote remote manifest for gkt@https://tgz.pm2.io/gkt-1.0.0.tgz fetched in 633ms
104 silly resolveWithNewModule gkt@1.0.0 checking installable status
105 silly saveTree pm2@0.0.1
105 silly saveTree -- pm2@2.10.6 105 silly saveTree +-- async@2.6.2 105 silly saveTree +-- blessed@0.1.81 105 silly saveTree +-- chalk@1.1.3 105 silly saveTree +-- chokidar@2.1.2 105 silly saveTree +-- cli-table-redemption@1.0.1 105 silly saveTree +-- commander@2.13.0 105 silly saveTree +-- cron@1.3.1 105 silly saveTree +-- debug@3.2.6 105 silly saveTree +-- eventemitter2@1.0.5 105 silly saveTree +-- fclone@1.0.11 105 silly saveTree +-- gkt@1.0.0 105 silly saveTree +-- mkdirp@0.5.1 105 silly saveTree +-- moment@2.24.0 105 silly saveTree +-- nssocket@0.6.0 105 silly saveTree +-- pidusage@1.2.0 105 silly saveTree +-- pm2-axon-rpc@0.5.1 105 silly saveTree +-- pm2-axon@3.1.0 105 silly saveTree +-- pm2-deploy@0.3.10 105 silly saveTree +-- pm2-multimeter@0.1.2 105 silly saveTree +-- pmx@1.6.7 105 silly saveTree |– semver@5.6.0
105 silly saveTree ±- promptly@2.2.0
105 silly saveTree ±- semver@5.6.0
105 silly saveTree ±- shelljs@0.7.8
105 silly saveTree ±- source-map-support@0.5.10
105 silly saveTree ±- sprintf-js@1.1.1
105 silly saveTree ±- v8-compile-cache@1.1.2
105 silly saveTree ±- vizion@0.2.13
105 silly saveTree `-- yamljs@0.3.0
106 verbose type system
107 verbose stack FetchError: request to https://registry.npmjs.org/needle/-/needle-2.1.0.tgz failed, reason: unable to verify the first certificate
107 verbose stack at ClientRequest.req.on.err (/usr/lib/node_modules/npm/node_modules/pacote/node_modules/make-fetch-happen/node_modules/node-fetch-npm/src/index.js:68:14)
107 verbose stack at emitOne (events.js:116:13)
107 verbose stack at ClientRequest.emit (events.js:211:7)
107 verbose stack at TLSSocket.socketErrorListener (_http_client.js:387:9)
107 verbose stack at emitOne (events.js:116:13)
107 verbose stack at TLSSocket.emit (events.js:211:7)
107 verbose stack at emitErrorNT (internal/streams/destroy.js:64:8)
107 verbose stack at _combinedTickCallback (internal/process/next_tick.js:138:11)
107 verbose stack at process._tickCallback (internal/process/next_tick.js:180:9)
108 verbose cwd /var/www/html/admin/modules/pm2/node
109 verbose Linux 3.10.0-862.9.1.el7.x86_64
110 verbose argv “/usr/bin/node” “/usr/bin/npm” “install” “–only=production”
111 verbose node v8.11.3
112 verbose npm v5.6.0
113 error code UNABLE_TO_VERIFY_LEAF_SIGNATURE
114 error errno UNABLE_TO_VERIFY_LEAF_SIGNATURE
115 error request to https://registry.npmjs.org/needle/-/needle-2.1.0.tgz failed, reason: unable to verify the first certificate
116 verbose exit [ 1, true ]

Posts: 1

Participants: 1

Read full topic

@nickmcs wrote:

Hello all

We have 5 sites that connect to same FREEPBX server, but one site constantly (happens months apart) has issue that fixes by itself, I just waited a day or more to get it disappear and everything works normally again. Other 4 sites are operating now without this issue. Trying to get it fixed with Flowroute, my SIP provider, but every time they ask me for all info and tcpdumps from server or router (Edgerouter) they can’t tell me what’s going on.

how a can I troubleshoot this?

I reckon it is our ISP or the Flowroute and their peers that have bad routing.

I hope I can get to bottom of this before it fixes by itself again.

Thank you for reading.

Posts: 3

Participants: 2

Read full topic

@sentinelace wrote:

When attempting to update extensions I get /var/www/html/admin/libraries/utility.functions.php

This appears to be because mariadb is crashing

https://pastebin.com/9yKC6Q0V

Seems you can fix with a repair but it keeps happening

Posts: 2

Participants: 1

Read full topic

@bitbanger wrote:

FreePBX Distro 14.0.11

Getting the following error this afternoon on “yum check-update”. Tried three times.

http://sng7.com/os/7.5/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

Posts: 3

Participants: 2

Read full topic

@thender wrote:

I used this script to migrate everything from a FreePBX 13 to FreePBX 14 machine: https://vimeo.com/197184570

It worked great. Then I copied everything from /var/spool/asterisk/monitor , /var/spool/asterisk/voicemail , and /var/spool/asterisk/outgoing from the old PBX to the new.

The issue is, when I log in, I can not see the recordings in the UCP.

Is there anything else I have to do to get it to copy over the database of all the call recordings? It is important for us to retain these, as what people say we said, and what we actually told them over the phone are veeeeeeeery different things a lot of the time. I wish people were more honest.

Thank you so much!

Posts: 2

Participants: 1

Read full topic

@breakaway wrote:

Hi Guys

I’m running Asterisk v1.8.28.0 - it is a “PBX In A Flash” system (FreePBX Version 12.0.76.6) and I want to set up a simple call forwarding system.

The deployment is small - just one trunk with 2 DIDs. Calls come in and are routed directly to a ring group which has two members as extensions.

What I want is for any user in the office (total of 4 extensions) to be able to pick up their number, dial a feature code THEN enter the number they want to forward to and hang up.

Disabling the call forwarder would be accomplished by dialing another feature code.

The idea is to give users control over when/who to forward the call to, so that we can forward calls to the on-call person on rotation that night when the last staff leaves the office.

I have had a look in the “pbx in a flash” web GUI but I can’t find this functionality there. Any help appreciated.

Posts: 1

Participants: 1

Read full topic

@erikson wrote:

Hi,
i have installed FreePBX 14.0.5.25 with a sip trunk line and 5 extensions. As soft-phone, i’m using Linphone.
When i receive a call, there is a way to display on the soft-phone the name of the caller instead of the number?

Thanks!

Posts: 1

Participants: 1

Read full topic

@alexkg1 wrote:

Tell me whether the phones are compatible polycom soundpoint ip 321 with software PBX asterisk (freebpx).
I can not find the information on this model

Posts: 2

Participants: 2

Read full topic

@byerkes wrote:

Is it possible to create a PJSIP extension that can be used by both a webrtc client (not the built in webphone) AND a regular sip-phone?

Posts: 2

Participants: 2

Read full topic

@Noxee wrote:

Hi,

Could someone please explain to me exactly what the Agent Timeout Restart Yes/No setting does in a queue. I’ve searched all over the web for a deeper explanation than the included “If timeoutrestart is set to yes, then the time out for an agent to answer is reset if a BUSY or CONGESTION is received. This can be useful if agents are able to cancel a call with reject or similar.”
I’ve messed around with the setting and just don’t see any difference with it on or off.

Thank you!

Posts: 1

Participants: 1

Read full topic

@handleric wrote:

Hello,

I’m running into some firmware issues with a S705. The device is currently configured for Zero touch provisioning via HTTP, and I have the Firmware Slot 1 set to 1.54 (2.0.4.63) and Slot 2 1.53 (2.0.4.62). This device is brand new and was received with firmware version 3.0.4.55 installed, and I noticed it didn’t upgrade after it booted and provisioned, so I tried to manually upgrade it via the web interface on the phone itself.

as it was booting back up immediately after the manual upgrade I am able to login to the phone web interface see the new firmware version. but then it runs through checking firmware and downgrades back to 3.0.4.55. I cant explain what would b causing this, can anyone shed some light?

Im running Endpoint Manager 14.0.2.188 on FreePBX 14.0.11

Posts: 5

Participants: 2

Read full topic