P2P, Skype, IM Proof of Concept App

This project is just to develop a "proof of concept" to help us find the right developer to build our main much larger project. The main project is centered around computers on unrelated networks being able to communicate with one another over the Internet. For this Proof of Concept, we'll assume they're all Windows PC's, but ultimately they could be Mac Linux, Android or even iOS devices. I want any "client" PC to be able to communicate with any other "client" PC. Clients could be behind NAT networks, or on Corporate networks, and could have public facing IP's, or most likely private IP's. The Client PC Windows installation App you develop needs to install seamlessly from an install wizard with minimal input from the user (ie assume they're non-technical). This means they should not need to know about configuring firewalls or changing UPNP settings on routers etc! At most, Windows and/or their PC Security/firewall software should prompt them to allow the app to install and pass traffic and that is all. In other words, it needs to operate like Skype, P2P, VoIP or Instant Messenger type apps, that all manage to work seamlessly so that even a beginner can install them, regardless of router, firewall and type of network the user is on. You can use a combination of UPNP libraries and/or a Relay Server and/or any other technologies necessary to make it work. You'll need detailed understanding of how apps like Skype, P2P, VoIP or IM etc work, so that you'll know all the issues to take into account to get this simple Proof of Concept to work. ## Deliverables This project is just to develop a "proof of concept" to help us find the right developer to build our main much larger project. The main project is centered around computers on unrelated networks being able to communicate with one another over the Internet. For this Proof of Concept, we'll assume they're all Windows PC's, but ultimately they could be Mac Linux, Android or even iOS devices. I want any "client" PC to be able to communicate with any other "client" PC. Clients could be behind NAT networks, or on Corporate networks, and could have public facing IP's, or most likely private IP's. The Client PC Windows installation App you develop needs to install seamlessly from an install wizard with minimal input from the user (ie assume they're non-technical). This means they should not need to know about configuring firewalls or changing UPNP settings on routers etc! At most, Windows and/or their PC Security/firewall software should prompt them to allow the app to install and pass traffic and that is all. Functionality for this Proof of Concept: Client App: 1. Register itself with the Master Server 2. Accept messages from any other client and display them in a window 3. Allow a message to be typed back to the other client 4. See a lits of other Clients currently "online" that can then be "messaged" Server Master App: 1. Show List of all clients ever registered (datetime first registered, PC Name, Public IP, Port etc) 2. Show list of currently active Clients, same info as above + current session datetime, current Public IP and Port etc The most important thing I am looking for in this Proof of Concept is the Client Windows Apps to be able to seamlessly install on any Windows PC (ideally XP, Vista and Windows 7) and be able to communicate without having to worry about configuring routers, UPNP or firewalls (beyond basic Windows Firewall questions on initial installation). In other words, it needs to operate like Skype, P2P, VoIP or Instant Messenger type apps, that all manage to work seamlessly so that even a beginner can install them, regardless of router, firewall and type of network the user is on. You can use a combination of UPNP libraries and/or a Relay Server and/or any other technologies necessary to make it work. You'll need detailed understanding of how apps like Skype, P2P, VoIP or IM etc work, so that you'll know all the issues to take into account to get this simple Proof of Concept to work.