I’m using FreePBX verison 15.0.23 for VoIP and openfire for IM. I used the Jitsi for both XMPP & SIP but it stopped update by official. Do we any new alternative method?
Any help will be appreciated.
Related
We have a game that is written with Adobe Flash and the server side is NodeJS and they communicate with socket.io.
We consider moving to Haxe, the problem is that when I try to google for Haxe and socket.io, I only find indications for it to operate together using haxe-js-kit.
Does anyone have any experience with Haxe and Socket.IO?
How is the performance of using haxe-js-kit for socket.io support?
Can I use haxe-js-kit both on browser and mobile and it will work properly?
Any information regarding the issue would be greatly appreciated!
Following twitter there are a fresh socket.io externs
For experience/recommendations go to haxe group
There are probably no pure Haxe port of Socket.io. If you intent on using it for OpenFL/Kha/etc. you'll want to port a Flash library to Haxe.
Already i built chatting application in(Android, iOS & windows phone) & established in asp.net WebAPI, Now performance is very poor.
After googling i found, XMPP is the best & free(I am planning to use free open source tool, don't suggest paid lib)
Instead of XMPP, why we can't try with signalR?
Suggest me, which one should I go & start establishing the API.
I know compared to SignalR, XMPP have lot of features.
Of course you can do it also with SignalR, or even as a combination of XMPP and SignalR.
XMPP is a complete presence and messaging protocol with lots of features and many available extensions (also non IM features). Its in production for over a decade now. It gives you all you need to build a IM/Chat app for free. So why to reinvent the wheel and rebuild all the existing functionality on your own with SignalR when you can just install an existing XMPP server, get a client XMPP library and start coding your chat application.
I am looking to implement WebSocket communication via ejabberd xmpp server...
The only module that I have found so far is this repository:
ejabberd-websockets
This repository has not been updated for 4 year so I do not feel very comfortable using it.
Any alternatives or reviews on above mentioned repository?
From ejabberd 15.03 version, WebSockets are fully supported, as stated here:
ejabberd 15.03 released, with Websockets support
You could also try node-xmpp-bosh which is a node.js based connection manager that sits in front of the XMPP server and handles BOSH and XMPP over WebSockets. The XMPP server sees all traffic as standard XMPP traffic.
I know that the BOSH part works well, but haven't tried WebSockets.
I have implemented two way SMS communication using IBM worklight V6.1 .But I wanted to know is it possible to send SMS without internet connection.Because I am not able to hit worklight server without internet connection
If you are using SMS Gateway Ultimate app as the gateway then you would need internet connection (dataplan/wifi). This article might be of help
https://www.ibm.com/developerworks/community/blogs/worklight/entry/testing_worklight_push_notifications_over_sms?lang=en
I'm experimenting with mqttjs and websockets and I wish to be able to send messages from a webpage using websockets without a bridge to an MQTT broker that is run by mqttjs. I can't find any information if this is available or even possible.
I've looked at mosquitto and they have "experimental" websocket support and I would love to find a Node.JS MQTT broker which could offer the same.
Thus far I got the communication working with pywebsocket and Socket.IO. I would really appreciate pointers in any direction if it is possible to use websockets to mqtt without bridging.
Thanks.
Is old question but is good to share my findings.
You can use the mosca broker that is written in node.js and is using mqtt.js
The mosca is supporting classic mqtt connection and mqtt over WS :
MQTT-over-Websockets
Mosca can operate in two modes: Standalone and as a node.js module.
In general mosca can support many types of brokers:
Mosca-advanced-usage
HiveMQ supports native websockets, which means you can use any Javascript MQTT library (like Eclipse Paho.js with websockets. It's perfectly possible to connect some clients vie websockets and other clients via standard TCP connection. The websocket support is stable and used in production.
The only drawback for you could be that HiveMQ is not written in Node.JS.
Disclosure: I am one of the developers of HiveMQ.