Voip became one of the web apps

From voip gadgets blog - A company called Innivative Systems of Communications launched flash based voip services SDK and server.

web : http://www.innosystems.ru/

From web:

Products

Zingaya Media Server

ZMS is a platform which allows to create SIP-based VoIP services. Such services can work right in web-browser via Adobe Flash technology.

System’s main feature is that end users don’t have to download any specific software. Due to Adobe’s research data more than 90% of Internet users have Adobe Flash Player installed.

ZMS opportunities:


ZMS works via HTTP through port 80 so it has no problems with NAT and firewalls
SIP 2.0 compatibility allows to use ZMS for interference with contemporary IP-telephony systems: softphones, IP PBX (Asterisk for example), call-centers, SIP proxy servers. It gives an opportunity (for VoIP operators) to create convenient services which allow users to make calls directly from web page without downloading any specific software

ZMS works with VoIP codecs G.711 and G.729

Integration with existent infrastructure at database level allows companies to implement ZMS-based solutions quickly and easily
Horizontal scalability, large-user-number systems building opportunity
Windows and Linux compatibility

Convenient API for client applications development in FlexBuilder 2/3, Flash CS3
ZMS allows to make own non-VoIP apps for Java-based server

Client apps are cross-platform due to Adobe Flash technology which is accessible at Windows, MacOS, Linux and works with most of contemporary browsers


Looks another 2.0 Voip.
© yankandpaste®

The 2.0

Its time of 2.0s

Web 2.0, Voice 2.0 Video 2.0 Telco 2.0 Business 2.0

BT is trying to be Telco 2.0. Have a look on

http://web21c.bt.com/

New SDK for Web21C Web Services.Create services for the Telco 2.0. Lot talks on integrating with social networks and second life. The last expectation is by 2011, this should make above $1 Billion :-)

© yankandpaste®

Voip ? Telecom Startups ?

A yank and paste from gigaom , I liked it.


Take This Job And Shove It — Why I Retired From Telecom
Guest Column, Monday, December 24, 2007 at 12:13 PM PT Comments (18)
Written by Brian McConnell

I have been designing phone services and starting phone companies for about 15 years, since I was in college. But I recently retired from telecom, concluding after all this time that it is not a good industry for entrepreneurs, especially those who don’t have access to vast amounts of capital or who don’t want to take on institutional financing.

There was a brief period in the mid-to-late 1990s when garage-based phone companies really were possible. The last remnants of Ma Bell had been deregulated, and there was an explosion of new technologies (VoIP, new switch architectures, the web as a distribution channel, etc). Big companies were disoriented by this, and had little clue as to how to deal with the rapid change. As a result, there were lots of big and small opportunities for startups to exploit new and rapidly growing niches.

Most of the profitable niches in telecom are now gone. Home phone service, long distance, small business phone service, conference calling, mobile — all have become low-margin commodity markets dominated by established companies. The capital costs of prototyping new phone services have declined, but not nearly as much as retail pricing, and hence, the margins are near zero. The liquidity and exit opportunities for small telecom companies are also not good. You either need massive amounts of capital, or you need to be bought by a phone company (the stereotypes about phone companies exist for a reason). There are exceptions, of course, but they are rare.

Mobile should be a huge opportunity for developers, but unless and until the carriers open their platforms and create something like Ad Sense for developers, it’s a rotten business to be in. The mobile operators micromanage application developers, and they do not share revenue freely. They often charge for network access when they should be rewarding you for stimulating usage.

The industry is currently clogged with VoIP services whose main offering is cheap phone service, because as a commodity product the only thing that matters is the price. Services like Jaxtr and Jahjah may get a lot of hype locally, but I don’t see how what they’re doing is all that different from what all those prepaid card vendors have been doing for years. The prices seem about the same, and the prepaid cards work from any phone.

Where does this leave today’s better-known telecom startups? Unfortunately, some combination of distribution problems and consumer apathy will kill most of them. Ooma is a good example. They make an appliance that allows you to make free calls by rerouting calls between their hubs over the Internet.

It sounds neat, but most consumers don’t spend enough time on the phone to make it worth using. For the majority of users, phone service is “cheap enough,” and once a product reaches that threshold, convenience outweighs price – which is the main reason mobile operators can charge a premium for essentially the same product. I think it’s only a matter of time before companies like Metro PCS set the norm with flat-rate pricing for mobile. But then where does that leave VoIP?

There are a few standouts that I think will find success, but these are mostly platform companies that are doing serious R&D. In VoIP, Gizmo is a favorite. I don’t think the economics of Gizmo as a service by itself are great, but they have been steadily developing a broad platform that enables standards-based VoIP on almost any device — not a trivial task. Someone will eventually buy them for their service plus this technology base.

When I compare telecom to the web, the big difference I see is that the web is both a destination and a distribution channel. This really makes it a unique medium. Telephone services, on the other hand, are products that are only loosely coupled to the web, if it all. A cool web site attracts users because it is clever or interesting. A phone service, at the end of the day, is just a dial tone. I think Skype was a hit because it was really a clever instant messaging client that happened to allow free/cheap phone calls. There were many VoIP services before Skype — Delta Three, Net2Phone and Dialpad, to name just a few.

What’s the message in all of this for entrepreneurs? Telecom seems like a great industry. After all, billions of people use cell phones. The problem is that there is nothing like the web for mobile, and by that I mean the entire set of standards and business practices that have grown around it. It’s hard to see this changing significantly in the near future. It’s also important to learn from history. If you’re building a phone product, spend some time on the former site for PhoneZone, the first company I started in California before selling it to Helio Direct in 1999. Some of my favorite products from that time, such as the Internet PhoneJACK (the first low-cost VoIP peripheral) and the Jetstream FrontDesk (great SoHo phone system), are also all long gone.

This is why I decided to quit telecom and focus on completely different projects. I am spending the next several years working on the Worldwide Lexicon, which aims to do for translation what Wikipedia did for encyclopedias. It may or may not turn out to be a good business, but it’s an interesting project, and it’s something new, whereas if I stayed in telecom, I’d be spending the next several years designing more bad IVR systems for banks and airlines.

No thanks.

Orginal link :http://gigaom.com/2007/12/24/take-this-job-and-shove-it-why-i-retired-from-telecom/
© yankandpaste®

Worst of 2007: VoIP

Copyright 2008 by Virgo Publishing.
http://www.newtelephony.com/
By: Kelly M. Teal
Posted on: 12/28/2007

--------------------------------------------------------------------------------


VoIP clearly has moved into the mainstream, but 2007 marked a year of high-profile stumbles that appear to signal the end of standalone IP telephony.

Vonage Holdings Corp.’s tribulations seemed to make headlines more than any other tech company in 2007. The pro-vider in March lost a patent suit to Verizon Communications Inc. and, in September, another to Sprint Nextel Corp. In mid-October, Vonage announced it also was being sued by AT&T Inc. for patent infringement. Through it all, Vonage stock plummeted to its lowest point, the balance sheets still don’t show a profit and CEO Michael Snyder resigned. Given all of that, not to mention the millions Vonage must pay Verizon and Sprint, there’s much conjecture about the future of Vonage. Will a rival buy the company? Will Vonage close up shop? Or will it keep swimming against the tide?

Those questions have yet to be answered. But one thing is clear about 2007: with all incumbent mergers cleared and cable MSOs ramping their VoIP offerings, it was the perfect time for the big guys to fend off standalone VoIP companies such as Vonage, says Infonetics Research analyst Stéphane Téral.

Increasing pressure from larger carriers appears to be one reason why SunRocket Inc. unexpectedly ceased opera-tions in July. The second-largest consumer VoIP provider also had a flawed business plan that worked against it in an age of bundling. The firm bet on a combination of low usage and a rapidly decreasing cost of termination services while pro-moting discounted prepaid annual subscriptions, says Téral. “If you do this, you need to bring in short-term cash at the risk of recurring revenue. And, in addition, you need a very low operating cost structure, which they did not have because SunRocket required users to have SunRocket hardware to access their network,” he says. That added burdensome over-head to SunRocket’s operations. Despite the signs, nearly everyone seemed caught off guard by SunRocket’s sudden closure last summer, another apparent victim of a VoIP gold rush gone sour.

Then, just this fall, there came news that online auction giant eBay Inc. has been unable to make good on its $2.6 bil-lion purchase of Skype Ltd. As a result, the promise of monetizing a free VoIP service looks less likely. That’s not surpris-ing, given that eBay’s logic went against basic Economics and Business 101 principles, Téral says. Skype started as a freebie and “when you start that way, it is impossible or at best extremely difficult to turn free users into paying users.” The real goal was to buy Skype’s large user base “to tap into as a new engine to increase eBay’s user base,” he says. “As it turns out, it did not really work that way.”

If eBay is going to keep Skype, it needs to figure out how to make money off Skype’s 220 million users and get the technology better integrated into auction operations, says Sally Cohen, an IP analyst for Forrester Research Inc. eBay originally wanted to allow users to call one another on the P2P network — potential buyers could ask questions of auc-tioneers, rather than waiting for e-mail responses. That assimilation hasn’t fully materialized.

eBay is trying to remedy its missteps. In October, Skype co-founders Niklas Zennstrom and Janus Friis left their ex-ecutive posts at Skype; this was somewhat expected given that the two had made no secret of their desire to focus on their new Internet TV project, Joost. Now the industry rumor mill says Skype could go mobile, although that presents new challenges of its own (for example, why would users pay extra to connect to a free service when they already pay for cell minutes?).

Turning Skype around will be a struggle. eBay reported a third-quarter 2007 net loss of $936.6 million, or 69 cents per share, due mostly to a $900 million write-down in Skype’s value. That marked eBay’s first quarterly loss since 1999.

Overall, 2007 set the stage for big changes in the VoIP industry. VoIP is no longer an adventure, an opportunity for startups, says Téral. “It’s a serious telephony business taken over by giant telcos. … You can’t stay pure-play forever.”




© yankandpaste®

Guilty as charged Plus, 10 nasty questions to ask your VoIP supplier

This story appeared on Network World at
http://www.networkworld.com/columnists/2007/110607-jericho-forum.html


VoIP security industry: Guilty as charged
Plus, 10 nasty questions to ask your VoIP supplier


The Jericho Forum By Paul Simmonds, Network World, 11/05/07

Simmonds is a member of the management board of the Jericho Forum, an organization pushing for innovation in e-commerce security, and is also chief information security officer for a large, global chemicals corporation. Here, Simmonds speaks out about why the Jericho Forum regards today’s VoIP systems as “guilty” of not meeting a necessary level of security. For anyone discussing this with your vendors, Simmonds has also drawn up a “Ten ‘nasty’ questions to ask your VoIP supplier” that’s included at the end of this column.

We in the IT security industry are collectively guilty for allowing a fundamentally insecure system such as VoIP to be launched into the market.

We’ve known for years that only “secure out of the box” should be the default. Yet VoIP is not only insecure by default, it’s almost impossible to make natively secure. What’s worse, VoIP end-devices (the phones) are a full computer – usually with their own Web browser, and (insecure) File Transfer Protocols to manage the firmware updates. So just as organizations are coming to grips with managing the vulnerabilities on their PCs, we have just doubled the management nightmare.

The return-on-investment claims made for moving to VoIP rarely stand up to proper scrutiny. The phones cost more than a standard “business” phone, and have a reduced replacement cycle. Gartner says in its November 2006 report “IP telephony technology, in many cases, can be more expensive than equivalent TDM-based PBX Systems.”

The ability to benefit from toll-bypass (routing your voice traffic over your private WAN to take advantage of spare WAN capacity) is frustrated by the fact that peak time for voice traffic is also the peak time for data traffic on the WAN. Most network managers that I know are looking for ways to offload peak traffic from congested, expensive corporate WAN links – not add huge volumes.

The ability to integrate your computer and your phone is another “benefit” that is on the salesperson’s list, with features such as Click to Call, Find Me/Follow Me and Unified Messaging, but in reality companies rarely take any advantage of such CTI (computer-telephony integration) options.

Then toss in all the extra Band-Aid solutions you need to add, from VoIP firewalls to specialist VoIP security assessments (just run a Google search for “VoIP security solutions”), to make it even partially secure, and the extra management for firmware upgrades, vulnerability assessment and mitigation, and of course the WAN upgrades and all of a sudden those incredible savings the sales-person promised magically disappear.

VoIP is, in essence, a time bomb, poised for a massive exploit. With VoIP gaining traction in the corporate world, from boardrooms to the world's financial trading floor, VoIP is a public security exploit waiting to happen – with the large potential consequences. But unfortunately, this may be what is needed before the industry agrees to take VoIP security seriously.

The historical problems with being able to listen in to conversations that people assumed were secure (or where people assumed security through complexity) are well known: In the 1980s, the world became aware of problems with analog cell phone security when tabloid journalists printed details of an intimate cell-phone conversation between Prince Charles (than married to Princess Diana) and Camilla Parker Bowles. We’re at the stage now with VoIP that something like that is likely to happen, but with consequences far more serious than embarrassment on the part of the British royal family.

At the 2006 Black Hat conference, David Endler and Mark Collier spent a very entertaining hour abusing a mix of VoIP phones, from being able to set up a call and listen in without the called phone ringing to a full corporate denial-of-service attack by making all phones repeatedly ring every 10 seconds (with no one there when answered).

“If it’s not broken, don’t fix it,” doesn’t apply here
At the 2007 Black Hat Conference, there were no less than five presentations on the insecurity and general problems with VoIP.

VoIP does have advantages in certain business situations, such as running an international follow-the-sun help desk or an overseas call center operation, but those business cases are limited and the security risks of VoIP should far outweigh most ROI cases.

Getting the security right, and according to Jericho Forum principles, will finally give a true business case with real ROI: The ability to securely integrate disparate sources of VoIP phones (from VoIP clients on cellular devices, to BlackBerry, Wi-Fi VoIP phones and PC soft phones, as well as the traditional desk phone) connected on LAN connections that probably will not be on a LAN managed by your organization.

Oddly enough, when I used VoIP to discuss this Network World column with a colleague in the United States, the call dropped five times. I gave up and switched back to my cell phone.

Do I like VoIP? It has great potential, but for now the answer is no.

The 10 nasty questions to ask your VoIP supplier:

1. Do all phones and the central infrastructure use 100% secure protocols?

2. Will you warrant this system to operate on the raw Internet with no further add-on devices?

3. Can you manage all VoIP devices automatically, simply, with a scalable, easy-to-manage solution that will support all VoIP end-client including soft phones and end-devices that are connected on the Internet?

4. Explain how phones are, by default, securely provisioned. Including devices that you do not have physical possession of during the provisioning process.

5. Explain how you can conclusively prove that a phone using your system was provisioned by you.

6. Explain how you can conclusively prove that when I make a call, (say from my hotel room) I can be 100% assured that my phone is connecting to the corporate exchange (without using extra security devices such as IPSec).

7. Explain how users are strongly authenticated when connecting their devices. Ideally both device and user should authenticate.

8. Will your system allow federation of identities so we do not need to maintain (yet another) autonomous authentication system?

9. Is there segregation of duties? For example: can the administrator access voice mail and set passwords without the user being aware.

10. Are voice mail systems encrypted, and are all backups encrypted (voice mail, user-names, configuration, passwords)?

All contents copyright 1995-2007 Network World, Inc. http://www.networkworld.com

A Hitchhikers Guide on Jingle

Abstract

The Jingle is subject of numerous specifications produced by XSF. It can be difficult to locate the set of documents or lot of documents where the big picture lies in a different group.This document serves as a guide to the jingle series. It lists the specifications under Jingle umbrella, briefly summarizes and groups into categories.



Table of Contents

1. Introduction 
2. Scope of this Document 
3. Jingle Session management Specifications
3.1 Overall session management 
      Jingle
      XMPP Core
3.2 Content formats
      Jingle Audio
      Jingle Video
      Jingle File Transfer
3.3 Transport formats
      Raw UDP
      ICE
3.4 General Support specifications
      Resource Application Priority 
      Service Discovery
      External service Discovery
      Jingle DTMF
3.5 Other documents
      Bootstrapping Implementation of Jingle

4. Interworking

5. Security Mechanisms 

1.0 Introduction

The Jingle is subject to numerous specifications produced by XSF. It is tough to get the big picture of the related technologies and relevance with jingle as the different technologies spread across different standard bodies. By giving emphasis on the big picture, this document tries to give the big picture and helps to identify the areas and importance.


2.0 Scope of this Document:


This document does not update jingle or related specifications. This is an informational document meant to guide newcomers, implementers and deployers to the Jingle suite of specifications.


3.0 Jingle Session management Specifications

Jingle consists of three parts, each with its own syntax, semantics, and state machine

         Overall session management 
         Content description formats (the "what") 
         Content transport methods (the "how")

3.1 Overall session management

The Overall session management represents the group of specifications that defines the core session generation,maintenance and tear down.

Jingle Core

This document defines a framework for initiating and managing peer-to-peer multimedia sessions (e.g., voice and video chat) between two Jabber/XMPP endpoints in a way that is interoperable with existing Internet standards.

Jingle is defined in XSF XEP 0166 http://www.xmpp.org/extensions/xep-0166.html


Extensible Messaging and Presence Protocol (XMPP): Core

This memo defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints. While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779.

Extensible Messaging and Presence Protocol (XMPP): Core is defined in IETF RFC 3920 ( http://www.faqs.org/rfcs/rfc3920.html )


Content description formats


Jingle Audio

This document defines methods for negotiating Jingle audio sessions that use the Real-time Transport Protocol (RTP) for media exchange.

Jingle Audio is defined in XSF XEP 0167 http://www.xmpp.org/extensions/xep-0167.html


Jingle Video

This document defines methods for negotiating Jingle video sessions that use the Real-time Transport Protocol (RTP) for media exchange.

Jingle Video is defined in XSF XEP 0180 http://www.xmpp.org/extensions/xep-0180.html

Jingle File Transfer

This document defines methods for negotiating Jingle file transfer sessions that use the Real-time Transport Protocol (RTP) for media exchange.

Jingle File transfer is defined in an expired draft in XSF http://www.xmpp.org/extensions/inbox/jingle-ft.html

This is a not an approved standard.

Transport description formats

Raw UDP

This document defines a Jingle transport method that results in sending data over a raw User Datagram Protocol (UDP) connection.

Jingle Raw UDP Transport is defined in http://www.xmpp.org/extensions/xep-0177.html


ICE

This document defines a Jingle transport method that results in sending data between two entities using the Interactive Connectivity Establishment (ICE) methodology.

Jingle Ice transport is defined in http://www.xmpp.org/extensions/xep-0176.html


General Support specifications


Resource Application Priority

This document defines an XMPP protocol extension to indicate the presence priority of XMPP resources for applications other than messaging.

Resource Application Priority is defined in http://www.xmpp.org/extensions/xep-0168.html


Service Discovery
This document defines an XMPP protocol extension for discovering (1) information about Jabber entities and (2) the items associated with such entities.


Service discovery is defined in http://www.xmpp.org/extensions/xep-0030.html


External service discovery

This document specifies an XMPP protocol extension for discovering services external to the XMPP network.

External Service discovery is defined in http://www.xmpp.org/extensions/xep-0215.html

Jingle DTMF

This document specifies an XML format for encapsulating DTMF data in informational messages sent within the context of Jingle audio interactions.

jingle DTMF is specified in http://www.xmpp.org/extensions/xep-0181.html

Other support Documents

Bootstrapping Implementation of Jingle

This document provides guidelines to client and library developers for bootstrapping implementation of the encrypted sessions technology.

Bootstrapping Implementation of Jingle is defined in http://www.xmpp.org/extensions/xep-0208.html

4. Interworking
In progress, A draft is in progress for interworking with SIP.

5. Security Mechanisms

Currently jingle supports secure transport as specified in RTP Over DTLS via a profile of "UDP/TLS/RTP/AVP".


DTLS extensions for SDP is defined in XSF http://tools.ietf.org/html/draft-fischl-mmusic-sdp-dtls-03

HD softphone

from website
Mirial Softphone is the most advanced software-only client for professional quality videoconferencing in H.323 and SIP environments - the first in its class with HD 720p support.

With Mirial Softphone, a webcam and a laptop or desktop PC every user can immediately start taking advantage from video conferencing and collaborative work, while enjoying an amazing visual experience: the product is the first softphone to support 720p High Definition and H264, thus providing a sharp, clear, outstanding video quality in both encoding and decoding.



our comments:
Not sure how its going to work on a normal laptop with a DSL or cable based internet connection. But for future - yes we need these steps.

Link : http://www.mirial.com/products/Mirial_HD_720p.html

© yankandpaste®

patent-pending call-routing algorithm-Distributed Termination

From ooma's web site :

ooma's patent-pending call-routing algorithm-Distributed Termination-uses the internet to connect local calling areas throughout the United States for free instead of relying primarily on traditional phone switches, known as the PSTN (Public Switched Telephone Network). As a result, each ooma customer who maintains their landline helps grow the ooma network. ooma's call-routing technology ensures a completely transparent experience so that the ability to make and receive phone calls is not impacted when their line is in use by another ooma caller.

As an example: Let's say you want to call "Claire" in Boston. You simply pick up the phone and dial. The ooma call is routed via the internet to an ooma customer with a landline in the 617 area code (let's call her "Cassy"). Cassy's ooma device (in Boston) completes the call by acting as a gateway and routes the call from her broadband to her landline, which is used to place a free call to your friend Claire. All this is done without any interruption to Cassy's phone service. In fact, Cassy doesn't even know her landline is in use and shall still be able to make and take phone calls.

What this means ? Simple words ?

You are an ooma custmer with a land phone, attach a record machine and you may able to get some other ooma cusomter's creditcard , personal talks and other secrets !!.

Nice for a movie story thread with getting hits of a murder or some theft through recording your own phone and finally getting criminals to law. But mostly the actual may be different - some body can listen to your private talk and black mail or stole personal information ( like creidcrad, otehr secrets u say by phone )

Do you think this kind of a system worth patent ? and the security threat u want to have by subscribtion ?

From : http://www.ooma.com/learn/ooma_faq.php


© yankandpaste®

A maemo answer for google phone wish list

1) First and foremost, I want an easy to use OS. Sorry, Symbian and Windows Mobile--though both these mobile OSes have plenty of power, they're not the easiest for the smartphone newbie to understand. Palm is a fine OS, but it's getting to be rather dated and sadly underpowered. Ideally, the Android platform will be as easy to use as OS X on the iPhone, but with a lot more flexibility.

Ans : Interface, GUI is not OS. maemo uses gnome mobile, Open source, themes supported.

Link : http://www.gnome.org/mobile/


2) Google has already come to my aid with the second feature I want--the ability to install and use a wide range of applications. I would be happy with the Google apps alone--I use GMail and Google Calendar religiously, and Google Docs would be great to have--but if Google truly believes in the open-source movement, they would open the doors for their competitors to enter the gate as well. This means I want to see apps from Yahoo and Microsoft on here along with all the other third-party ones.

Ans : Mozilla based web browser with flash and other support.


3) Following up on number 2, these are the applications I want on the phone: A fast and well-built browser that supports Flash as well as Java, a multiple IM client, an e-mail client that supports POP and IMAP, compatibility with Microsoft's Exchange server for work e-mail, and perhaps this is a pipe dream, but I want a VoIP client. Ideally, I'd like a mobile Skype app, as well as compatibility with something like T-Mobile's HotSpot @ Home, where I get to make free calls via WiFi.

Ans : garage.maemo.org - you will see more than 409 projects ( skype is already there )

4) It needs to be fast. That means I want 3G, and I want Wi-Fi as well (OK, so this is encroaching on hardware territory a bit). Thankfully, Qualcomm has mentioned that 3G will be a big part of Android, so this isn't too far from reality. That said, 3G and Wi-Fi together in one package would be ideal.


Ans : I don't know how many 3Gs are already deployed,
I don't understand why you need even 3G when WIMAX or 4G ( all ip based infrastructure) rolls out


5) Open up Bluetooth as much as possible. That means I want stereo Bluetooth as well as the ability to tether my PC to the phone via Bluetooth and use it as a modem. This combined with the phone's 3G abilities would obviate the need for a separate EV-DO or HSDPA PC card.

Ans : have a looks on

"7.4 Bluetooth
A high level API for Bluetooth is offered as part of the maemo connectivity subsystem.Using its D-BUS API a program can find remote Bluetooth devices such as phones,send files over OBEX object push and create pairings with remote devices. For thesetasks it’s recommended for application to use this framework as it not only has a lot simpler API but makes the applications look and behave consistently. For Bluetooth operations that aren’t supported by the maemo connectivity framework maemo includes a lower level BlueZ D-BUS API, which is also the main Bluetooth interface for all Linux systems. The BlueZ API has features for practically all aspects of Bluetooth systems, and as a consequence its a lot more complex than the higher level Maemo Connectivity subsystem’s offerings.The Maemo Connectivity Guide[41] describes the high level D-BUS API and its usage. More information about the BlueZ API can be found at BlueZ web site [3]. The maemo-example package also includes example code about both libraries.

[41] Maemo connectivity guide. http://maemo.org/development/documentation/
how-tos/4-x/maemo_connectivity_guide.html.

[3] Bluez project’s home page. http://www.bluez.org/.



Link : http://crave.cnet.com/8301-1_105-9811364-1.html
To read : www.maemo.org

tailpiece : its easy to write a blog with eyes closed. Opening the closed eyes is important.


© yankandpaste®

The Flash Phone

Thanks to Tom Keating (TMC lab ) for talking about the flash phone. I rushed to the flashphone site for a trial.

Clicked the link flashphone.ru - waiting, waiting and waiting -- nothing happened.

Entered http://www.flashphone.ru/en/main , yep the response is fast.

Registered and got a mail for activating my account. Tried to activate my account - no response :-(.

Today morning while checking my mail, found a mail asking whether i got the activation mail. I replied saying clicked and nothing happened. 5 minutes - they send back a mail saying my account is activated.

Rushed in to the site, made the first call, wow works!!. Normal idea executed nicely.

I didn't try the sip call because my 3 call limit got over with 3 PSTN calls and i am sure all the SIP HYPERs will do that first than PSTN call. I think the sip should change its name to HYPE because always a lot HYPE marketers make it live.They don't bother a business system build on top of sip is struggling from SUEs (vonage). They don't want to address those issues but want to say SIP SIP and SIP.

I am not sure it works only for sip because if its an asterisk at backend, it can make calls to other protocols also. I was to try but my 3 call limit is over :-(.

The first look says me it works in this way.

                                                                                                                                         
Client<----> Web server (flash media server)
                 |
                 V
Custom channel driver or interface 
to existing channel 
               |
               v
           An asterisk 
           or a softswitch 
               |
               +----> PSTN Cloud
               +----> SIP
                                                
       

and the client talks to web server using custom protocol with the primitives

===
login
createCall
createSipCall
setCallId
disconnectCall

play
onStatus


_result

===
No firewall traversal problems because call always goes to server( no peer o peer) but expensive at server side for network bandwidth. Again this i didn't explore that detail because the PSTN calls always need to go to a gateway.

The security ? yep looks they still believe in md5 for encrypting password.

Business model : its a video advertisements model. So we say when you make a call,ring with a video and audi on, then video ( only video because there is only one mic ) advertisements. May be they change, if no body buy them.

The news link : http://feeds.feedburner.com/~r/voipgadgets/~3/180638564/flashphone-beta-running-on-adobe-flash-launches.asp
The site : http://www.flashphone.ru/en/main

End result :

good job !!!, People can use it easy, don't bother about technology ,Its easy to use.



© yankandpaste®

The e28

Google phone, every body is excited. media is making lot sound. Where is it ?

I believe that last days indiasmart and e28 has a lot of hits. It nice to see E28 is getting more attention. I dont understand why not the nokia N series is not in the picture ( maemo platform ).


I too added some hits to the site.
© yankandpaste®

Rex - The new softphone from GIPS

Gips is expanding to domain of servers, clients from the core audio engine product.


The gips site says : REX PC is a comprehensive communication solution that leverages the Internet to deliver advanced features such as PC based calling, IM and voicemail. REX also provides the features and functions that service providers seek in a softphone. The customizable GUI allows service providers to deploy a softphone with the look and feel of their choice..


This ends up lot small scale developers.


web : http://www.gipscorp.com/rex/rex.html

© yankandpaste®

Vonage Goes To Court III - The AT&T Suit

"AT&T has filed a lawsuit against Vonage, claiming patent infringement. This is the third major lawsuit to have been brought against Vonage by a major phone company. Vonage lost the previous two lawsuits, brought by Sprint-Nextel and Verizon. How much more money can Vonage afford to give away? How can Vonage educate a jury on prior art? 'It said in a filing to the U.S. Securities & Exchange Commission that AT&T is seeking injunctive relief, compensatory and treble damages and attorneys' fees in unspecified amounts. Vonage said the lawsuit was filed in the U.S. District Court of the Western District of Wisconsin on October 17.'"

from : http://yro.slashdot.org/article.pl?sid=07/10/20/0022232&from=rss

poor voip
© yankandpaste®

Summary of best and worst with promise

Lot lot things , i feel i missed a lot because i didn't write timely

A) The best is qtopia's full open source phone: yep qtopia relased full source code.

Link : http://qtopia.net/modules/devices/

B) The worst is Vonage's Loss on IPR issue: read the Patent and felt sad to the people who allowed it to be a patent ( ex: a server which responses to queries to translate uri to a phone no: etc ). I wonder its just an application of database and its a server - i don't know its a database server - ODBC can do this, or if the patent is for combination of server, transaction etc then DNS do it. I belive the patents need to be more better.

C) Exciting ones ?

Yep its telepathy : http://telepathy.freedesktop.org/wiki/

Why ?

Look at http://laptop.org/laptop/ . An excellent stuff. I really love to get one or some hands on this for some time.

Look at N800 from Nokia: a full Linux tablet. An excellent device to have potential to replace all mobile phones in future with Wimax with sprint ( Sprint CEO stepped down - so what 'll happen to the wimax project ). Acanac offerd me one for free ( thanks to them - they are my VOIP provider )

Link:

http://www.nseries.com/products/n800/

Both uses telepathy and jabber.

© yankandpaste®

VoIP will make money, not save it

There are two problems with the hype around IP telephony.

First, it probably will not save users as much as they would end up spending on extra hardware to maintain call quality ­ the promise of savings is a red herring.

But there is a bigger problem in that most people punting IP telephony completely miss the point about its real value. They are stuck in a 130-year-old mindset in which telephony begins and ends with the ability of two people to talk when they are apart. Several embellishments have been added ­ voicemail, caller ID, call forwarding ­ but it is still all about talking. If all that has changed is the way the voice signal is carried, then voice over IP (VoIP) changes nothing.

But if voice is simply another data stream, then it can be mixed up and enriched with other data streams. Once that happens ­ once phone systems are connected to financial and customer records ­ a world of opportunities opens up. Business can start being extracted from a system that was previously just part of the furniture.

Link caller ID with other information, for example, and suddenly when customers call, their profiles pop up on screen even before the call has been answered. Everything can be seen ­ from outstanding invoices, to what happened last time the customer called the company, to how profitable the account is.

Making well-integrated information available to the right people as soon as or even before they need it makes for better, faster customer service and happier customers.

Even better, an integrated system makes it easy to keep information up to date. Suddenly, a customer relationship management system simply is an address book and it automatically tracks every phone call, SMS or email exchanged with every customer. The customer database is always up to date and shared throughout the organisation. It can also become a rich source of information for new business creation.

That is the true value of VoIP. Forget about saving pennies on phone calls and look instead to the new business it can create

from : http://www.dailypayload.com/2864
© yankandpaste®

Voip on Nitodo ( TV to UCD )

Change the world, or move with the changed world.

TV is not going to die, TV is going through its evolutions and becoming UCD

Exiting TV shows ...
Boring TV shows ...
IPTV ... ( apple Tv )
Game place

Now to a phone .....

and TV continues to be the central point of your house.

read on this new software which works on Nintendo DS.

http://libw11.free.fr/svsip/index.html

What next ? wii or on your PSP and Xbox, attend calls with your TV, watch IPTV with TV,Play game with TV, Browse and do a lot more with TV.

Is it now TV ? display ? unified communication display ( © UCD - my term, copyright belongs to me )


Enjoy !!
© yankandpaste®

gOOgle phOne

talks on google phone :-), says a five facts

The operating system will be a "mobile variant of Linux" capable of running Java Virtual Machines.

Second, all the on-board applications will be Java-based, including the music/video player.

Third, the user interface is based in Java, is "very responsive", features a "search box", and will be "typical of mobile phones."

Fourth, the web browser -- also in Java -- will have pan and browse.

Lastly, there was initially one prototype, but since then the mobile OS has been seen running on between 3 and 5 devices, all of which rock the QWERTY.


Our view : google phone will be a mobile device capable of surfing internet (may be WIFI or WIMAX or 1X or EVDO or GPRS ( we dont expect GPRS because of low speed).
It will not be the normal mobile phone and will be running a linux OS and capable of running all the google app including gmail, search, talk ( expect call out and callin from googletalk with a dial pad ).google apps, maps youtube videos and all other google applications. The main focus will be adv displays with content.

It's time of voip and web to common man, every body needs it.

© yankandpaste®

Story of stolen $1 million worth of voice minutes

A combination of simple dictionary and brute-force attacks in combination with Google hacking enabled a criminal pair to break into VoIP-provider networks and steal $1 million worth of voice minutes, says one of the duo who has pleaded guilty to his crimes.



more details at :
http://www.networkworld.com/news/2007/081007-voip-hacker.html?netht=081307dailynews1&
© yankandpaste®

mundu - The garment IM

The mundu is a garment worn around the waist in Kerala and Maldives related to the Dhoti as well as the Lungi. In South Canara district of Karnataka state the Tulu speaking folk and Beary community do use mundu. It is normally woven in cotton and coloured white or cream. The colour is dependent on whether the cotton is bleached or unbleached. Kaddar mundu is another kind which is made using handlooms. When unbleached the mundu is called a neriyathu. In modern times, two types of mundu are prevalent - the single and the double. A single mundu is draped once around the waist, while the double is folded in half before draping. A mundu is usually starched before use.


http://www.mundu.com/ talks about an IM product which claims: A comphrehensive Instant Messaging platform to help you build, grow and monetize your user community.


Another web 2.0 company playing with multi messaging ( i am not sure whetehr there 'll be a day when i can have one account and talk to different servers).The sadest part is i was not able to find even a single reference to any standards in the site. so i assume it as another propratory IM.

Unfortunatley the http://www.mundu.com/platform/platformfeatures.php?top=3&leftIndex=3 link gave more than enough confusion. Just put some blocks and say its a platform features without any explantion

any way i think the wed designers managed to push a lot of open standard words in the platform features as features (looks the person who made the picture never know what he was drawing ).It more resembled me a preson who dont know english draws "To let" as "Toilet".I tried to download but looks slow , so i left it as it is :-)

© yankandpaste®

ICE to RFC ? Noooooooo expect 18

Was wondering Ice going to be RFC.

http://tools.ietf.org/html/draft-ietf-mmusic-ice-17

Nooo , today was browsing my mails and find yet another version to come.

miles to go before i sleep ( now change it RFC ) :-)

© yankandpaste®