There are many considerations as you begin offering VoIP services. VoIP Logic offers a complex set of systems for call processing and integration that are offered 'on demand' as your business grows. Please refer to the sidebar resources on this page or contact sales@voiplogic.com for a more detailed walk-through of our offerings.
Here are some articles about service creation the VoIP Logic way:
Outsourcing in the Service Creation Environment
This basic PBX IP diagram will help many people see how VoIP actually works. A PBX (Private Branch eXchange) is nothing more that a technology that connects more people and devices to the PSTN network than there are actual outbound phone lines (trunks).
The center of an IP based PBX system is Asterisk. It is an open source software that most commonly runs on Linux. The phones all connect to the same network as the IP PBX, and communicate with it. The PBX in turn connects the devices to the PSTN network either through standard POTS lines with zaptel hardware, or directly to a VoIP provider via SIP trunks that in turn terminates to the PSTN network.
Most people are aware of the mainstream trixbox PBX distribution, and the ever growing PBX-in-a-Flash distro, but recently people have been wondering what is available for Windows?
pbxnsip is a Windows based VoIP solution. It runs on Windows. The pbxnsip PBX is available for various platforms, including Microsoft Windows, Linux and NetBSD. You can choose what hardware and software platform is most efficient for you.
Windows-based operating systems: The PBX runs on Windows 2000, Windows XP, Windows 2003 Server and Windows Vista versions. pbxnsip also runs on Windows Server 2003 Web Edition. If you run the PBX on Windows Workstation editions, you might have limited number of TCP connections and calls.
Linux-based operating systems: pbxnsip supports RedHat ES4, SuSE 10 and Debian 3.1 for Intel-based platforms (Pentium-compatible). All images are compiled for the 32-bit memory layout, but also run on 64-bit machines.
You can download and install it from an .exe file right on Windows XP. Either way you go, you configure it through a web-browser such as Internet Explorer or Firefox. You do not need to use Linux like other PBX VoIP solutions require, however, you may install the Linux version on a Linux box if you wish.
The pbxnsip PBX has all the common features that you expect from other competing distributions. It has hunt groups, auto attendants, ITSP support, mailboxes, and conferencing. It also supports paging, call recording, and call agent groups.
pbxnsip is not open-source like other competing software based PBX’s. It is free to download and try, but you must buy a liscence n order to continue using it.
Using your cellphone to make phone calls using any wireless hot-spot may soon be a sought after feature on cellphones. With the processing power doubling or tripling every year on hand held devices, developers have already started developing programs to be used on Wi-Fi networks with the existing phones like the iPhone. An example of this being done can be found at free.fr. However many developers are selling their programs or making you sign up for a mailing list in order to receive them.
My question is how long will it be until VoIP applications start coming free with your cellphone so you don’t have to burn your wireless minutes at home using your cellphone? I can’t imagine any wireless provider just putting VoIP apps on your phone that will take away from their bottom line. They want your teen daughter blowing away minutes on your family plan talking about what her and little Jimmy did over the weekend, or texting until her thumbs look like they are broken in 3 different places.
So for now, install fring on your jailbroken iPhone, and watch at&t’s revenue dry up like a salty slug in summer.
vb_ebook.jpg (80.8 KB, 5 views) vb_ebook2.jpg (33.5 KB, )
Building_Forums_with_vBulletin.zip (4.16 MB, )
Readers are cautioned not to rely on this article as legal advice as it is no substitution for a consultation with an attorney in your state. Based on jurisdiction and time, the law varies and changes.
Software escrow means deposit of the software's source code into an account held by a third party escrow agent. Escrow is typically requested by a party licensing software (the "licensee"), to ensure maintenance of the software. The software source code is released to the licensee if the licensor files for bankruptcy or otherwise fails to maintain and update the software as promised in the software license agreement.
Source code is the software's programming code represented in a particular programming language that humans can write and understand.
Either the licensor or licensee should pick an escrow agent. Generally, the licensor should pick and pay for the agent so that the owner of the software has the choice of which third party will be responsible for storing and handling the source code. Additionally, the licensor often will have more than one licensee request escrow, and having the same agent each time makes the record keeping and contract negotiation much simpler.
Often, licensees will allow the licensor to pick the agent if the licensor also pays the escrow fees. When picking an agent, be sure to investigate the background and financial status of the company. An agent with no assets and without substantial insurance coverage is not a good choice. The agent should have substantial resources, so that the parties to the escrow agreement may be protected in the event of the agent's negligence and ensuing litigation, or in the event of loss of the code and financial reimbursement by the agent's insurance company.
Software escrow fees are typically between $1000 and $2000 per year per licensee. There is some variation based on different pricing structures. Some companies will reduce the rates for licensors who have substantial numbers of licensee deposits.
The software escrow agreement is a three party contract that governs the procedures and terms of the escrow process between the licensor, licensee and agent. Usually, the software license agreement will contain a clause that states that the parties agree to escrow and will execute a separate agreement to cover those terms. As this agreement involves three parties, the negotiations can be more difficult than usual.
The party that chooses and pays the agent should negotiate its terms with the agent prior to bringing the third party into the negotiations. This will save time in that two of the three parties will already have agreed on the contract wording prior to the third party reviewing the agreement.
Procedures
The agreement should outline the procedures for the deposit and handling of the code by the licensor and agent, including what will be deposited (updates, customizations, etc.) and how often the deposits should occur. How the agent is to receive the code, and where and how it is to be stored should also be addressed.
The agreement must also define the procedures for release of the code after an event that's recognized as triggering its release. These procedures should include notice to the parties, deadlines for response and counter argument, opportunity to seek court order, and so on.
The agreement should state what events result in release of the code to the licensee. These may include:
The licensor should always try to limit the release events solely to failure to provide maintenance. If any of the other events above occur and the licensor continues to provide maintenance as agreed, there is no reason to justify release of the source code and release may cause substantial damage to the licensor in this event.
