gruz / fusionpbx-api

9 stars 10 forks source link

Issue with First API Post #13

Open inoutglobal opened 3 years ago

inoutglobal commented 3 years ago

Dear,

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

Regards

image

gruz commented 3 years ago

Hi. I work at dev branch currently. And I'm going to release a new version, heavily reworked in a while. But still not perfect.

What are your requirements? So I can additionally focus on them before the next release.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, June 21st, 2021 at 20:46, Edson Lopes Filho @.***> wrote:

Dear,

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

Regards

image

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

inoutglobal commented 3 years ago

Good to know you are still working on it.

I just want an FusionPBX API where is possible to create the basic - new Domain, Extension, Extension Group, Gateway, Routes, IVR,etc..

I wish i could contribute somehow. Regards!

gruz commented 3 years ago

@inoutglobal I'll post here when ready to ask you to test

sgosain commented 3 years ago

Hi. I work at dev branch currently. And I'm going to release a new version, heavily reworked in a while. But still not perfect. What are your requirements? So I can additionally focus on them before the next release. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, June 21st, 2021 at 20:46, Edson Lopes Filho @.***> wrote: Dear, Tried the first Post without luck. It seems to fusionpbx schema has changed. Where do i fix it? Regards image — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

To create Objects like extensions are you using identical logic as in fusionpbx/app/extensions extensions.php and extensionedit.php whereby when creating a new extension not only do we create the db record but also the associalted voicemail directory. In other words - are your copying the fusionpbx logic for the relevant business object endpoint (e.g. extension) or somehow are you able to invoke the fusionpbx code (as socket for example) to create the business object?

gruz commented 3 years ago

Hi. I work at dev branch currently. And I'm going to release a new version, heavily reworked in a while. But still not perfect. What are your requirements? So I can additionally focus on them before the next release. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, June 21st, 2021 at 20:46, Edson Lopes Filho @.***> wrote: Dear, Tried the first Post without luck. It seems to fusionpbx schema has changed. Where do i fix it? Regards image — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

To create Objects like extensions are you using identical logic as in fusionpbx/app/extensions extensions.php and extensionedit.php whereby when creating a new extension not only do we create the db record but also the associalted voicemail directory. In other words - are your copying the fusionpbx logic for the relevant business object endpoint (e.g. extension) or somehow are you able to invoke the fusionpbx code (as socket for example) to create the business object?

It was my first thought to reuse native FusionPBX code, just to simulate form submit preparing $GLOBALS. I tried this approach in 2017 and I don't remember why I gave up. I don't remember the reasons. Sometimes I think to try this approach again, but I have no time.