Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am working on an XMPP client, using ejabberd as server.
My question is how can I support offline file transferring?
I only want to do the offline file transferring for image files.
For example,
I can transfer an image to John even if he is offline.
When John comes back online,
the server will send him the image.
How can I do that?
There is currently no extension for XMPP to allow offline file transfers.
Presumably this would need to be supported by the recipient's server, and it would need to be implemented as a server-specific plugin.
Alternatively a project that may be of interest to you is Jabber Disk, which allows you to upload a file via XMPP, and then returns a HTTP URL you can send to people (for example as an offline message).
XMPP had an extension for this - XEP-0129: WebDAV File Transfers - but it is deferred!
I am searching for the same solution. I came across it, but did not find a XMPP server still supporting it.
Still searching for a solution.
We implemented offline file transfer is TextOne mobile client, but we had to do a custom module. There is no good specification for that yet.
However, for a simple need as you have, I think you could implement it purely client side (uploading to an HTTP server) and use XMPP for signaling.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I know this is an big open question, but I'm more interested in the email functionality of a helpdesk.
If I were to build an online web application / help desk for my site how does the email monitoring work? How would the application retrieve the emails and create or update a ticket based on the ticket ID in the subject line?
I've never understood this and considering the attempt.
You assign some email addresses to the application, then set up email handling to route messages for that address to the application. This can be something simple like running fetchmail to pull email from the inbox on the email server and piping it to the application. Or you can update your email server to forward messages to the helpdesk server and set up an MTA like postfix to accept the messages and pipe them to the helpdesk application.
There are 100's of open source helpdesk applications, so I would recommend finding one in your language of choice and adding a feature rather than re-implementing this one feature. Handling email properly is very difficult because the specs are detailed and confusing, and you'll get a bunch of email that doesn't follow the specs.
If you just want to understand how it works, try setting up one of the open source applications and running some email through it. Turn on debugging and you can then find and read all of the code. Request Tracker (RT) is one option. rt-mailgate is the program that handles email. The basic instructions for setting up email aliases are covered in the README in step 10.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm looking at WebRTC and I'm wondering how to implement a solution where the client connects to the PTSN via SIP. It seems like a pretty new technology so I assume that this would not work on IE browsers; is this correct?
Basically, I have a dialpad UI on the page and users who have an SIP account. Can WebRTC enable the end-user to make calls to the PTSN and what does it take to implement such solution?
I'm looking into this as an alternative to Java or Flash based webphones.
Thanks for your suggestions.
WebRTC is indeed new and isn't available on IE or Safari. It is available in beta/alpha on other browsers. IE will probably support it in the future and Safari probably won't for some time.
WebRTC does only the media parts of the negotiation, and as such it means that it does no signaling of its own. SIP can work well with WebRTC, but you will need a JS implementation of SIP (over WebSockets) and then you'll need to unwrap the SIP signaling on the server side and "migrate" it to UDP or TCP.
Asterisk are working on such a server side platform: http://blogs.digium.com/2012/05/23/asterisk-11-webrtc/
More about doing SIP in conjunction with WebRTC can be found here: http://bloggeek.me/html-sip/
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to create a chatting application that enable users that connect via XMPP to chat with another users that connect using web socket (perhaps using Netty or Jetty) or vice versa. So every users that connect using web application can chat with other user that connect using web socket.
I am not sure that websocket currently have a default standard that enable it to communicate with other protocols. Let me know your opinion and suggestion.
Very much like on top of TCP, you can implement rich business protocols over WebSockets as well. Kaazing offers XMPP as one of several protocols over WebSockets (in addition to JMS and AMQP).
You can check out the XMPP edition of the Kaazing WebSocket Gateway here, and find the documentation and tutorials here. The developer version of the product, up to 50 concurrent connections, is a free download. The community edition is open-source licensed under the Apache 2.0 license.
There exists a draft for XMPP over WebSockets. It's a year since it was submitted, but I think work on it will continue once WS itself stabilizes.
There exists experimental implementations of XMPP over WS, but since WS has been a moving target, they aren't implementing the latest versions (AFAIK).
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Is there a library or any way to embed video chat capability in a ios application ?
I work at 2600hz, I'm new to stack overflow so if I'm screwing something up, let me know.
You can use Kazoo, our fully open-source cloud voip stack for this, our APIs allow you do all the sip signaling and proxying for Facetime style video connections (we do this for audio calls now, and video works in our lab but we haven't rolled it out to our community yet. Basically you'd need to do some QA).
If you'd like to play with it, I can send you an invite to our hosted cluster OR you can install it directly from our Git repos here: https://github.com/2600hz/kazoo
Yes, there are a few solutions:
First of all, no API from Apple.
Second, OpenTok does seem to solve your problem, Client & Server side easily.
If you want to implement it yourself, I know Spirit & Vidyo, which are paid VoIP & Video stacks.
You may also use iDoubs, or PJSip, both are open-source solutions, but they are using x264 encoder which its license is GPL and not good enough for the AppStore.
Either way, you'll need a 3rd party library for that & you must have a server side as well (Probably a SIP server).
If anyone knows more open-source / paid solutions, please share.
Build Video Chat Into Your Mobile Apps with OpenTok
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
What are the best options to encrypt the data in iPhone?
I want to send the encrypted key over the network. Please suggest.
Unless you have a good understanding of cryptography use SSL/HTTPS. It's designed for transferring data securely over the net.
Assuming that you are connecting with a web server over HTTP, then install an SSL certificate on the web server and you will be able to use HTTPS. All you need to do in your code is change the URLs from http:// to https://.
If you need to add an additional layer of security, then I recommend that you look into the CommonCryptor library and using CCCryptorCreate/CCCryptorUpdate/CCCryptorFinal methods.
unlike Mac OS X, iPhone doesn't have openSSL included. You can compile and add it in if you want, but HTTPS is far, far easier.
If you are using a socket connection, you can use TLS.
If you want to tread the hard way, check this out. You don't have to write a custom algo to encrypt/decrypt data. You may try out the encryption/decryption supported in the iOS.