FreeSwitch Binding (5.x)

Add-ons Bindings
, , ,
1

Hi,

long time ago a gave something back to the community :innocent:
Now its end of month, I am a little bit sick and there were a minor amount of KI-Quota left.

So I decided to checkout the Old openHAB1 Binding of FreeSwitch (which I quickly installed over docker and registered two old Snom821) and bringt it to the new 5.x standard.

If possible I post the org.openhab.binding.freeswitch-5.3.0-SNAPSHOT.jar here.
(Need additional adwises how to push it back to productive branches.)

The the most reason why write here, is that I am searching for Experts knowing what magic is possible with ESL. Everything I can get as Feedback will be also included in this Binding as Channel. :upside_down_face:

Until now I habe (1:1 from v1)

image
image1119×990 57.5 KB

(all except “Registered” are working) in OpenHAB 5.2.0

Following are open minded ideas, which I will try to include:

  • activeCallCount
  • agentState
  • callAnswerTime
  • callDirection
  • callEndTime
  • callStartTime
  • callUuid
  • codec
  • dnd
  • failedCalls
  • lastCallDuration
  • lastCaller
  • lastCallee
  • lastCallEndReason
  • missedCalls
  • networkAddress
  • partnerExtension
  • registrationState
  • ringing
  • successfulCalls
  • talking
  • userAgent
  • voicemailCount
  • ??
2

To make it easier for users to install and test, if you post to the marketplace they can install it from the Add-on store. When you post a PR to openhab-addons and it gets merged, you can remove the published tag from the marketplace entry to make it no longer show up for users.

3

I think I do not understand the difference between Add-on store and marketplace. For me the only source of truth is the git-repro and a final PR+Merge. Please explain all other ways (or link to them) and the reason why these exist. Thank you

PS: I have sucessfully integrated TTS and STT. But everytime I want to combine them like a real “assistent” my code breaks…

4

.jar or .kar file: You just post a link somewhere. Users must download the jar file and place it in the add-ons folder. The add-on “installed” in this way does not appear everywhere it should in MainUI but it works, until OH is updated to a new version. If the .jar file is not compatible with the new OH, OH itself will crash or get stuck while coming up with no errors.

This is the most labor-intensive way for users to have to install an add-on.

Marketplace: See Add-on Marketplace - openHAB Community. This is a place where you can create a new thread following a special template (the new thread will prepopulate with that template). You fill out information about the add-on, rule template, block library or widget and post a link to it. These will show up in MainUI and the user can just install them like they install official add-ons.

image
image1979×396 82 KB

No copying of files from random links. No needing to remember to remove the jar file after an upgrade. And the add-on appears everywhere in MainUI it’s supposed to.

You can set clear limits on the versions supported so it doesn’t even show up for users of versions of OH where it’s not supported.

The add-ons are cleared out automatically during an upgrade. However, that usually means the user must reinstall the add-on after an upgrade which is annoying, but better than OH crashing.

When the add-on gets merged, you can just remove the “published” tag and it will no longer show up to users as an option to install.

In general, the Marketplace makes it much easier for the users to install and test your add-on.