Search for project
More than 2000 projects issued through our platform and this
amount increases very fast.
Kool Tel Mobile Telephone Project (ID:2275)
| Project Creator: |
KoolAndrew
FC Member For 6516 Days
Credits 30 Completed Proj. Num. 0 / 1 Total payment USD Avg Daily Online 0.00 h (From 21/5/2007) Available on MSN/Skype Yes Last Login 6/5/2007 Peers Rating 0.00% 
|
|---|---|
| Budget: | Not Sure/Confidential |
| Created: | 4/26/2007 3:08:31 AM EST |
| Bidding Ends: | 5/26/2007 3:08:31 AM EST ( Expired ) |
| Development Cycle: | 30 Days |
| Bid Count: | 5
|
| Average Bid: | 3,400.00 |
| Project Description:
There are four stages to the development of this project. They can be done in concert and require different skills sets. Project Outline Kool Tel wants to provide mobile phone users an alternative method of making outbound calls. KoolTel will offer customers two methods, ani dialing and callback. In each case, there will be premier features available to enhance the experience. Service offer KoolTel wants to offer the customers a more seamless method of dialing long distance and/or local calls from the mobile device. Currently, customers need to dial some type of access number then wait for some type of prompt and dial another number. KoolTel has a few methodologies that are seamless and will offer these to prospective customers. 1. Direct ANI. i) The customer? phone will dial a local access number from their phone pause and then dial the phone number that they wish to call. This will take place very quickly as the initial call will be answered immediately and the second call will be placed almost simultaneously. The outbound call will be authenticated by either the customer? telephone number or by a pin which will prepend the number. ii) The alternative method will dial the phone number and the customer will be told to either say the number, the persons name and location (i.e. Andrew Wells home) or dial it (see Technological requirements section 3). 2. Callback i) The customer? phone would dial a number and hang up. The server would capture the number that the customer is dialing and immediately call the customer back and dial the outbound number. The outbound call will be authenticated by either the customer? telephone number or by a pin which will prepend the number. ii) The alternative method would be the same as above except that it would use call back; therefore the customer would hang up the phone and the server would call back and he would hear the same as in section 1.ii. In each case, the customer would be able to hit ** to start the process all over again to make another call. Technological requirements 1. Website. The customers would need to be able to download a Java applet from the KoolTel website. This would be available to any customer upon signing up for the service as their will be different downloads (see section 2). 2. ANI/Callback server. This would be a combination of trixbox for the ani/callback application and asterisk2billing for the authentication methods. There are many other available open source applications. 3. Festival Speech to Text/Uploading of Outlook/Yahoo contacts list. This is an open source application which is part of trixbox. In this case, the customer would need to set up his account and probably count to ten and say a few words so it would recognize his voice. For example, he may also have to say home, office, business, mobile, cell etc so he could state the person? name and the location. Also, the customer would be given an access point to easily upload the contact info which could be stored on our servers in which the customer could easily access. Methodology Basically, it could work one of two (or several ways as you may have a suggestion) whereby it will redirect the way a customer makes a telephone call. Here are some ways that I see. Two are different for two different applications with the same results. 1. As the customer signs up for the service, he would be asked if he would be asked for his local cell phone number. This would determine later on, what service he would be offered. If we don? offer a local number in that area, then we would be forced to use callback. Since many cell phone companies offer inexpensive rates for callback, we need to ask the customer if he wishes to have local calling included as well. 2. He would then download the appropriate java applet to his phone. At this time there would four different applets, depending upon his service requirements. It is important for a customer to be able to change his download if necessary should he wish to change his service requirements. 3. The java applet would be set up as follows. i) A code is imbedded in the dial plan of the phone whereby the customer is required to enter an *, for example, before all the contacts (or ones that he chooses in the phonebook of his phone) or preferably it will add all the ones that are 11 digits or more and not in the same area code, depending if he wants local calling or not. ii) When the customer dials a number, the system will have hidden a number for the * plus a pause, a pin for authentication and that number will be dialed plus the actual number of the number the customer is dialing. iii) It would be preferable if this applet could be turned on and off by the customer in case he is roaming or if he has unlimited local calling in the evening. We could even match the customer? plan so local calls would be done using his provider? network during the unlimited hours (i.e. m-f after 8pm-6am and weekends). iv) We need to send the customers ANI on the outbound leg of the call if possible. We could do this in stages; the most important part is an easy way for customers to make calls to our network without having to dial two numbers. 4. The Call Back/ANI system would be set up only to generate Pins and or authenticate the customer. There will two levels of authentication. i) Customer recognition. If the customer does not have a pin and/or phone number that is recognized, then he would should a voice prompt that we don? recognize his account, please dial 1 XXX-xxx-xxxx to activate your account. ii) Account Status. If the customer doesn? have funds in his account, he will either be directed to call customer service like above or redirected automatically to customer service to resolve his account issues. This information would be stored in the billing server. 5. Uploading of Contacts. We need a very simple application for this. Obviously, when the customer makes a call, he will be able to access his contact list through voice commands as outlined in section 6 and his contact will be dialed. 6. Festival Speech to Text. The customer would be required to call a number to set up their account. Maybe it would be on the first call of the cell phone. But he would be required to say specific words so it could figure out who they are trying to call. Developer requirements The developer must have experience in Java (j2me, j2ee), Asterisk (and asterisk app?), MySql, PHp and potentially .net. Developer Selection: The developer will be selected based upon his experience, knowledge, in development. The developer needs to quote the project in sections as follows: 1. Java development 2. Asterisk server 3. Uploading of contacts 4. Festival speech to text. The first section needs to be developed first. The company will provide the appropriate server for section 2. The winning bid may be more than one project developer depending upon the time frame, price and development of the components. |
|
| Job Type | .NET, Java, PHP, Javascript, Other |
| Attached Files: | N/A |
