I prefere to use asterisk and node js with ari-client package.

Thanks Brian

We just released an Rtcomm sample that only requires the Mosca MQTT broker running on Node.js along with angular-rtcomm. Instructions are on the angular-rtcomm page. I’m with you, Node.js and WebRTC are a perfect pair.

-Brian

+1 for Sam. First hand account that his codelab is solid.

we are using node.js for signalling . Everyhting works great for a video conferencing solution without plugin.

Prior to starting @twelephone, I built (and sold) a Node.JS PaaS called Nodester. We supported web sockets on the platform and could handle approximately 1M web socket connections per AWS server. You can horizontally scale web sockets across multiple servers for the same site if needed by using Redis. In fact, Socket.io supports Redis scaling out of the box! https://github.com/LearnBoost/Socket.IO/wiki/Configuring-Socket.IO

Today’s developers are solving the signaling issue with one of these three technologies: websockets, xmpp/jingle, and sip. All of them are good choices. I happen to prefer websockets. If you use a websocket framework like socket.io, they handle fallback technologies for you automatically to run on all web browsers (http://davidwalsh.name/websocket).

Hope this helps…
Chris

Thanks for the reply. When i goggle i get to know that scalability(clustering) is an issue wrt to node.js when compared to openfire or ejabberd . Aslo , using the following link , http://stackoverflow.com/questions/9924822/scalability-issues-relating-to-socket-io . I found that websocket.io can handle max of 10,000 requests , what should we do if requests >10,000

Hanumesh,

Node.js is a server side technology – as such it has no limitation on the web browser side.
What you should be “concerned” about is probably the Socket.io side of the story, and its support is detailed here: http://socket.io/#browser-support