gruz / fusionpbx-api Goto Github PK

root@ofispbx:/var/www/laravel-api# composer update
Do not run Composer as root/super user! See https://getcomposer.org/root for details
Loading composer repositories with package information Updating dependencies (including require-dev)
Nothing to install or update
Package guzzle/common is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/stream is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/parser is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/http is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Generating autoload files

Illuminate\Foundation\ComposerScripts::postUpdate
php artisan optimize
PHP Parse error: syntax error, unexpected '::' (T_PAAMAYIM_NEKUDOTAYIM) in /var/www/laravel-api/vendor/optimus/genie/src/Repository.php on line 262

[Symfony\Component\Debug\Exception\FatalErrorException]
syntax error, unexpected '::' (T_PAAMAYIM_NEKUDOTAYIM)

Script php artisan optimize handling the post-update-cmd event returned with error code 255

Hello,

I installed your fusionpbx-api according to your install process in readme.md, and have encountered the following reproducible errors.

[2017-10-28 19:56:50] local.ERROR: ErrorException: Undefined property: Api\User\Repositories\UserRepository::$database in /var/www/laravel-api/api/User/Repositories/UserRepository.php:66

This is prompted when using the curl method of going to the /signup/ uri for user and domain creation. It is also same when Authenticated Bearer is used as well.

I have a feeling that it is the latest laravel version that is causing this issue, as a previous install I have just worked. Just wanted to give you a heads up.

BR

krull

How to retrieve key authentication?

Example: <Fusion_IP>/app/api/contacts/api-key{747eea3-863b-4d22-812c-6291d2e0de28}?username=admin&key=i5pBIFDGDvPsXm2y5ZfD6KXuZjfzJzF4

I see this on 5 files searching for 'Modelsxtension'

FYI.

If reference code need is enabled in configuration, then user creation data must provide such a reference code (a code from a billing system to track calls to world) and the code must match a list of available codes.

The list of the codes will be taken from an external api in the future. For now this can be a table model.

Since we have already added email_verified_at column to v_users table anyway, we may add the reference code column as well.

Or maybe move these fields to a separate table not to intrude into FPBX tables. This seems to be a better option.

Hi guys! nice work has been done here...

This is not an issue!

I have question, I see this is a PHP integration... is there any endpoint to start a call? We are moving from FreePBX to FusionPBX. I would like to do something like:

127.0.0.1/app/api.php?func=call&call_from=1234567890&call_to=0987654321

And handle the call from a web browser (We are working on nodeJS / React).

Any advice? I'm not sure if something like this is done already, don't want to reinvent the wheel. Not sure either if FreePBX or FusionPBX are better for this... as far as I've seen, it looks like FreePBX have more API support?

Thanks a lot!
Chris

Dear,

Tried the first Post without luck.
It seems that fusionpbx schema db has changed. Where do i fix it?

Regards