Wednesday, September 29, 2004
Tuesday, September 28, 2004
IDC report on VoIP adoption
According to IDC the hosted IP voice services is expected to reach $60 Mn by end of 2004 and to grow with a CAGR of 282% to reach $7.6 Mn by 2008
Friday, September 24, 2004
Call Centers Charging for service
Analyst say that this wont catch as a wild fire, but I definitely think it will as more and more companies try to push their users to web self service. Only the terminlogy will differ. instead of saying taht they will charge you for serving over phone, they will say that they will give you a discount if you opt for Self service.
And I am sure it will catch up in a big way.
I am wondering why cant they use phone self service? agreed it is costlier than web self service, but definitely it is a good option.
And I am sure it will catch up in a big way.
I am wondering why cant they use phone self service? agreed it is costlier than web self service, but definitely it is a good option.
Tuesday, September 21, 2004
Global Broadband Marketshare
Global Broadband Tops 123M UK has 1/3 net users using broadband(DSL+cable modem)
Friday, September 17, 2004
Open source SIP based P2P application
EarthLink Intros SIP-Based P2P Prototype
USe this to understand how SIP works with P2P.
USe this to understand how SIP works with P2P.
Thursday, September 16, 2004
Bandwidth consumption of a VoIP call?
Click here for details.
Summary:
Codec BR NEB
G.711 64 Kbps 87.2 Kbps
G.729 8 Kbps 31.2 Kbps
G.723.1 6.4 Kbps 21.9 Kbps
G.723.1 5.3 Kbps 20.8 Kbps
G.726 32 Kbps 55.2 Kbps
G.726 24 Kbps 47.2 Kbps
G.728 16 Kbps 31.5 Kbps
iLBC 15 Kbps 27.7 Kbps
BR = Bit rate
NEB = Nominal Ethernet Bandwidth (one direction)
Summary:
Codec BR NEB
G.711 64 Kbps 87.2 Kbps
G.729 8 Kbps 31.2 Kbps
G.723.1 6.4 Kbps 21.9 Kbps
G.723.1 5.3 Kbps 20.8 Kbps
G.726 32 Kbps 55.2 Kbps
G.726 24 Kbps 47.2 Kbps
G.728 16 Kbps 31.5 Kbps
iLBC 15 Kbps 27.7 Kbps
BR = Bit rate
NEB = Nominal Ethernet Bandwidth (one direction)
Wednesday, September 15, 2004
GnomeMeeting - A window to the world...
GnomeMeeting is an opensource application, which delivers same functionality as Skype.
People at Gnome meeeting have scathing comments for Skype. Sample this:
The main problem is not that the program is not Open Source, the problem is that Skype is locking users into a proprietary protocol. Would you imagine the Internet with a proprietary equivalent to the HTTP protocol that only a given client could browse? That's what happens with Skype. Skype also has a great marketing force, some people even think that Skype has a superior audio quality. How could Skype have a superior quality when it is using the same codec (iLBC) than software like GnomeMeeting while introducing more latency by making calls go through a 3rd party? The only real advantage of Skype is that it is easily going through any type of NAT, using a 3rd user to proxy the call. But the day when the Linux kernel NAT will natively support H.323 or SIP, Skype will have lost its only advantage... Skype is hype...
This is really interesting.
Lets evaluate Gnomemeeting.
People at Gnome meeeting have scathing comments for Skype. Sample this:
The main problem is not that the program is not Open Source, the problem is that Skype is locking users into a proprietary protocol. Would you imagine the Internet with a proprietary equivalent to the HTTP protocol that only a given client could browse? That's what happens with Skype. Skype also has a great marketing force, some people even think that Skype has a superior audio quality. How could Skype have a superior quality when it is using the same codec (iLBC) than software like GnomeMeeting while introducing more latency by making calls go through a 3rd party? The only real advantage of Skype is that it is easily going through any type of NAT, using a 3rd user to proxy the call. But the day when the Linux kernel NAT will natively support H.323 or SIP, Skype will have lost its only advantage... Skype is hype...
This is really interesting.
Lets evaluate Gnomemeeting.
Friday, September 03, 2004
SIMPLE or XMPP
XMPP, is a ratified standard from IETF to allow IM interoperability. Jabber, IBM's Sametime work using XMPP. The industry is abuzz with rumours that Google is about to bring out their IM application in the market (Google recently acquired Picasa which has an IM client called Hello, working on proprietary standards, which allows users to share photos...I guess Google's offering will be an extension of this along with Blogger, gmail and search. Probably they will come up with interoperatability between Gmail and their IM client which will be a breakthrough).
At the same time, MS announced that its MS LCS will be an open standards based client, which will work using another protocol called SIMPLE. Now 1. SIMPLE is not yet ratified by IETF (i do not understand why they have two separate standards XMPP and SIMPLE)
2. MS's LCS is a part implementation of SIMPLE just like IE doesnt respect standards ( I guess tehy want to do the same thing to IM landscape as to what their IE did to NS).
3. Google's implementation of XMPP will fragment this space once again. There was some light at the end of tunnel after years of heated debate and frustrations, when AOL and Yahoo announced that their IM systems will interoperate with MS LCS
I dont think people will convert enmasse to Google, but yes, users of Blogger/gmail will start using this as an alternate as it will provide better functionality. (For example since I use Google to search and blogger as my webmail, Google toolbar became an obvious choice as compared to yahoo toolbar)
Jabber however has announced that it will develop a SIMPLE to XMPP gateway (why have two protocols in the first place?)
I am not a history buff, but I would love to know how email evolved? Comments anyone?
One potential application of SIMPLE is for devices to do presence detection. Fo example with the mobile revolution came the frustration of getting calls at any time of the day or night (yeah Alok, I know you well) (BTW, do not try this with me as when I am sleeping I switch off my mobile phone). Now the problem with mobile is that it being more personal, ppl do not think twice before calling you as they would have with a POTS.
Imagine the possibility that if I could update my status on the mobile phone, and anybody who has me in his phone list/address book can get that information on his mobile phone. It will really solve one big problem and it would give a better convenience to the users.
At the same time, MS announced that its MS LCS will be an open standards based client, which will work using another protocol called SIMPLE. Now 1. SIMPLE is not yet ratified by IETF (i do not understand why they have two separate standards XMPP and SIMPLE)
2. MS's LCS is a part implementation of SIMPLE just like IE doesnt respect standards ( I guess tehy want to do the same thing to IM landscape as to what their IE did to NS).
3. Google's implementation of XMPP will fragment this space once again. There was some light at the end of tunnel after years of heated debate and frustrations, when AOL and Yahoo announced that their IM systems will interoperate with MS LCS
I dont think people will convert enmasse to Google, but yes, users of Blogger/gmail will start using this as an alternate as it will provide better functionality. (For example since I use Google to search and blogger as my webmail, Google toolbar became an obvious choice as compared to yahoo toolbar)
Jabber however has announced that it will develop a SIMPLE to XMPP gateway (why have two protocols in the first place?)
I am not a history buff, but I would love to know how email evolved? Comments anyone?
One potential application of SIMPLE is for devices to do presence detection. Fo example with the mobile revolution came the frustration of getting calls at any time of the day or night (yeah Alok, I know you well) (BTW, do not try this with me as when I am sleeping I switch off my mobile phone). Now the problem with mobile is that it being more personal, ppl do not think twice before calling you as they would have with a POTS.
Imagine the possibility that if I could update my status on the mobile phone, and anybody who has me in his phone list/address book can get that information on his mobile phone. It will really solve one big problem and it would give a better convenience to the users.
Sarbanes-Oxley Act
You can find the full text of Sarbanes-Oxley at http://vscpa.com/Advocacy/SOtext.htm , and the most relevant sections for IT teams are nicely summed up in 'How CIOs Should Prepare for Sarbanes-Oxley' at http://www2.cio.com/analyst/report2271.html"
Wednesday, September 01, 2004
MS announces 2006 Target Date for Longhorn
1. Release Date advanced by a year for Longhorn client.
2. The new WinFS file system will not be available with Longhorn. The Longhorn server will be available in 2007 only (I believe with Win FS).
3. This is important. WinFX will be available for Win XP and Win2k3 Server also.
This will ensure that Application Developers worldwide can start racing ahead with re-designing their Applications to take advantage of Avalon -- the new graphics subsystem and Indigo -- which will ensure more secure and reliable inter-connected transactional system. When MS does a beta(Q3 05?), Application Development companies like us should start looking actively at how to harness the new UI metaphors to enhance the user experience.
WinFX availability on WinXP will give a taste of Avalon to millions of WinXP users (More than 50% of Computers hitting Google have Win XP today), and I believe MSFT is counting on them to getting hooked and easily moving on to Longhorn. (Nice strategy, eh)
http://www.microsoft.com/presspass/press/2004/Aug04/08-27Target2006PR.asp
Regards
HimS
PS: I believe with these developments, the upcoming threat to MS near dominance of the PC-OS market from Linux etc. stand a little muted.
2. The new WinFS file system will not be available with Longhorn. The Longhorn server will be available in 2007 only (I believe with Win FS).
3. This is important. WinFX will be available for Win XP and Win2k3 Server also.
This will ensure that Application Developers worldwide can start racing ahead with re-designing their Applications to take advantage of Avalon -- the new graphics subsystem and Indigo -- which will ensure more secure and reliable inter-connected transactional system. When MS does a beta(Q3 05?), Application Development companies like us should start looking actively at how to harness the new UI metaphors to enhance the user experience.
WinFX availability on WinXP will give a taste of Avalon to millions of WinXP users (More than 50% of Computers hitting Google have Win XP today), and I believe MSFT is counting on them to getting hooked and easily moving on to Longhorn. (Nice strategy, eh)
http://www.microsoft.com/presspass/press/2004/Aug04/08-27Target2006PR.asp
Regards
HimS
PS: I believe with these developments, the upcoming threat to MS near dominance of the PC-OS market from Linux etc. stand a little muted.
Subscribe to:
Posts (Atom)
