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

No voice/audio on inbound/outbound calls

October 31, 2019, 11:58 am
$
0
0

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

↧
Search

"All circuits are busy now. Please try your call again later"

October 31, 2019, 12:24 pm
$
0
0

Hello. I have a little issue with Asterisk 13 con CentOS 7. See, I have configured my TRUNK and OUTBOUND ROUTES, and cannot make calls through the trunk to the other end and viceversa.

I leave with configuration from both ends to please help me out if I’m missing something.

When Going to CLI, I get this command to check my trunk is conencted to another end, but cannot make calls.

freepbx*CLI> iax2 show peers
Name/Username Host Mask Port Status Description
TO-MAQUINARIAS/ 172.16.34.20 (S) 255.255.255.255 4569 (T) OK (1 ms)
1 iax2 peers [1 online, 0 offline, 0 unmonitored]

↧
↧

FreePBX.org Repos Down?

October 31, 2019, 12:27 pm
$
0
0

yep they are backup - just came back to the post to update

↧

PJSIP not ringing both devices at once

October 31, 2019, 12:28 pm
$
0
0

I am using the bria mobile app. I need my desk phone and app to ring at the same time since it’s the same extension. I have max contacts set to 5 but only my app rings. Am I missing something?

↧

FreePBX 15 is Released!

October 31, 2019, 12:34 pm
$
0
0

Hey All,

Just wanted to let everyone know (who wasn’t aware yet) that FreePBX 15 is now officially in a released state. Read the release announcement at:

If you have any encounter any issues, feel free to create a ticket on issues.freepbx.org.

Best wishes to you all, and happy release day!

Matthew Fredrickson

↧
↧

FreePBX 13 Updates Fail Due to Data Type "bit"

October 31, 2019, 12:35 pm
$
0
0

Running module updates on 10.13.66-22 from CLI I just got

[Doctrine\DBAL\DBALException]
Unknown database type bit requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.

Here is the error in the GUI when I try to update Sound Languages 13.0.26 to 13.0.27:

Doctrine \ DBAL \ DBALException
HELP
Unknown database type bit requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.

/var/www/html/admin/libraries/Composer/vendor/doctrine/dbal/lib/Doctrine/DBAL/Platforms/AbstractPlatform.php
if ($this->doctrineTypeMapping === null) {
$this->initializeAllDoctrineTypeMappings();
}

    $dbType = strtolower($dbType);

    if (!isset($this->doctrineTypeMapping[$dbType])) {
        throw new \Doctrine\DBAL\DBALException("Unknown database type ".$dbType." requested, " . get_class($this) . " may not support it.");
    }

I get this on pageingpro, endpoint, soundlang and a number of other modules. I don’t see bit data types in any of those tables. What could cause this error?

I can’t do a reload now because " Unable to locate the FreePBX BMO Class 'Soundlang’A required module might be disabled or uninstalled. " which it is "Disabled; Pending Upgrade to 13.0.27 "

↧

Random Inbound Calls Failing

October 31, 2019, 12:43 pm
$
0
0

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

↧

FreePBX 15 is Released!

October 31, 2019, 12:50 pm
↧
Search

PJSIP not ringing both devices at once

October 31, 2019, 12:53 pm
$
0
0

How many devices show registered under sip-asterisk info-peers. There’s different push notification settings like single device takeover etc. I use bria teams mostly to avoid all that but it likely has to do with your bria registration type or push type. You can check this by seeing if bria is stealing the active registration from your phone.

↧
↧

PJSIP not ringing both devices at once

October 31, 2019, 12:55 pm
$
0
0

that’s probably the issue but can’t they be registered at the same time and ring at the same time?

↧

PJSIP not ringing both devices at once

October 31, 2019, 1:10 pm
$
0
0

Yes of course they can…but bria has settings for registration types…

There are four registration modes. Continuous and Standard are used if your VoIP service provider supports multiple registrations. Single Device Takeover and Single Device Emulation are used if your VoIP service provider does not support multiple registrations. Most VoIP service providers do support multiple registrations. The default value for new accounts is Single Device Takeover.

  • [OpenContinuous](javascript:void(0):wink:

The Continuous registration mode ensures that the Bria Push server is always registered on behalf of the Bria Mobile client. The Bria Mobile client still registers directly to the SIP server when in the foreground, but the Bria Push server does not de-register from the SIP server. In this mode, all inbound calls and all outbound calls from the Bria Mobile client are handled by the Bria Push server.

The Continuous mode, in particular, is used when a SIP server supports multiple registrations at the same time. This mode avoids any gap in SIP registration because the Bria Push server is always registered on behalf of the Bria Mobile client.

In the event of a call to the SIP account while the Bria Mobile client is in the foreground, the Bria Mobile client will receive an INVITE directly from the SIP server and via the Bria Push server. The Bria Mobile client will filter out these duplicate events and only allow one of the call attempts to progress.

  • [OpenSingle Device Takeover](javascript:void(0):wink:

The Single Device Takeover mode is an enhanced option of the Single Device Emulation mode. The Bria Mobile client and the Bria Push server take over registrations from each other without unregistering first . Neither the Push server or the Bria Mobile client sends SIP de-registration messages when transitioning from one element to the other. It aims to eliminate gaps that are present in the other registration mode. This mode is in some cases beneficial for SIP servers that only support single registration.

  • [OpenStandard](javascript:void(0):wink:

The Standard registration mode allows both the Bria Push servers and the Bria Mobile clients to register to a customer’s SIP account in an alternating manner. In this mode, there may be short overlaps of registration where both the Bria Push server and the Bria Mobile client are registered to the SIP server. Some PBXs, SIP servers or SIP services may have issues with this registration overlap. If you encounter an issue with registering to the SIP server or receiving push notifications, select a different registration mode.

  • [OpenSingle Device Emulation](javascript:void(0):wink:

The Single Device Emulation registration mode ensures that both the Bria Mobile client and the Bria Push server unregister before the other one registers. In other words, the Bria Mobile client and the Bria Push server never register to a PBX, SIP server, or SIP service at the same time. The Bria Mobile client controls the registrations by requesting the Bria Push server to register only after the Bria Mobile client has de-registered and alternately, by receiving confirmation that the Bria Push server has de-registered before the Bria Mobile client registers directly to the SIP server. The Bria Mobile clients will also not register while they are in a call delivered through the Bria Push server so that they do not cause potential issues with the call in progress being terminated by the SIP Server.

Note that when in the Single Device Emulation registration mode, there are periods of time (typically fractions of a second) when neither the Bria Mobile client or the Bria Push server will be registered to the PBX, SIP server or SIP service. This gap could lead to a missed call if the call is presented to the SIP server at the same time that neither element is actively registered. This is a downside of the requirement of the SIP server that only one element be registered at any one time.

↧

PJSIP not ringing both devices at once

October 31, 2019, 1:14 pm
$
0
0

I don’t know that bria’s registration settings are doing that…you need to check your server to be sure.

↧

FreePBX 15 is Released!

October 31, 2019, 1:22 pm
$
0
0

Thanks so much for the kind response @tm1000! The list would not be complete without recognizing your contributions and the other members of the community that contributed to the release as well. Hope you are doing well, and best wishes!

Matthew Fredrickson

↧
↧

P-Access-Network-Info SIP Header transmission for INVITE

October 31, 2019, 1:29 pm
$
0
0

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

↧

Initiate repeating page from 3rd party windows application

October 31, 2019, 1:44 pm
$
0
0

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

↧
Search

Restore of PBXact trouble

October 31, 2019, 2:20 pm
$
0
0

It’s PBXact, open a support ticket. That’s the whole point of PBXact, when stuff like this happens it’s Support’s problem, not yours.

↧

FreePBX 15 is Released!

October 31, 2019, 2:27 pm
↧
↧

Can no longer mount a USB stick

October 31, 2019, 2:48 pm
$
0
0

I have a PBXact installation where I mounted a USB stick to store periodic backups. It was working okay for a while, but recently I checked on it and the stick is no longer mounted and will not mount. It doesn’t error when trying to mount, just fails silently, like something is immediately unmounting it.

I was mouting on /var/spool/asterisk/backup/USB_Backup and writing a weekly backup.

This fails:
mount -o uid=995,gid=995 /dev/sdb1 /var/spool/asterisk/backup/USB_Backup

Also had this in fstab which also no longer works:
UUID=USB20FD /var/spool/asterisk/backup/USB_Backup auto nofail,uid=995 0 0

Is there some change in a recently release that unmounts things? Or maybe it no longer likes fat?

↧

Backup failed after upgrade to 15

October 31, 2019, 3:02 pm
$
0
0

Look at the filestore module and make sure the ftp location is correct. Then look at your backup and make sure it has that FTP in storage locations.

↧

FreePBX 15 is Released!

October 31, 2019, 3:16 pm
↧
Viewing all 227984 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>