Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signaling Servers #47

Open
jcrubino opened this issue Apr 7, 2014 · 3 comments
Open

Signaling Servers #47

jcrubino opened this issue Apr 7, 2014 · 3 comments

Comments

@jcrubino
Copy link

jcrubino commented Apr 7, 2014

Is there a backend server that devs can run and build upon for phono?

@steely-glint
Copy link
Contributor

Phono is built to work with Tropo's phono gateway product. They run a public cluster of servers for devs to use. They also license (I believe) the phono server. Those are the supported options.

However, since PhonoClient speaks something that looks very like jingle-over-BOSH,
with some slight tweaking you can use openfire or any other jingle capable BOSH server to route the signalling. Of course by doing this you lose Tropo support and the other facilities the gateway offers (like simple bridging to SIP for example).

@jcrubino
Copy link
Author

jcrubino commented Apr 7, 2014

@steely-glint thanks... based a brief look, the tropo forum had questions hanging from 2011 so I got the feeling I might need to run a server where I can also look at the code.

@steely-glint
Copy link
Contributor

If all you want to do is place peer-to-peer audio and video calls between webRTC endpoints, then openfire or prosody can be made to work with the open source phono client code pretty easily.
If you want calls to PSTN,SIP, flash fallback for non-webrtc browsers, failover etc then you should talk to sales@tropo.com and I'm sure they will help you out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants