|
Author
|
Topic: SIP and H.323
|
KelvinW
Member Posts: 1
From:
Since: Feb 2003
|
posted 03 February 2003 11:13 PM
   
Lately SIP had made a lot of noise. However, it seems to me H.323 and Cisco Stinger still the dominat VoIP protocols.I did some search on internet trying to get a sense who is using SIP and who is using H.323 or else. However, almost all the hits I got are from vendors' websites which do not give accurate picture. I like to know who are using SIP now or who is thinking moving to SIP. My company is making serious decision on this subject. Unfortunately, we seem not be able to get clear picture. Appreciate your input. IP: Logged |
Keisuke Hashimoto
Sr. Member Posts: 377
From: Funabashi Japan
Since: Aug 2000
|
posted 04 February 2003 04:14 AM
There is one example here.Softfront, a Japanese company is offering SIP based solution.
http://www.softfront.co.jp/en/solution/iptel/personal.html But looks like they are also offering H.323 based solution as well. Also NTT Comware, a child company of NTT Holdings is developing SIP based videophone software. NTT-C is also developing conference server,web conferencing, along with CRM,ERP etc.. Just FYI if you are interested. keis
18:00 Feb.4,2003 JST +9GMT This message has been edited by Keisuke Hashimoto on 05 February 2003 IP: Logged |
AndyN
Wainhouse Research Posts: 345
From: Sarasota FL USA
Since: Jul 2000
|
posted 04 February 2003 10:07 AM
Significant SIP Sightings:
- Microsoft Messenger for Windows XP is SIP-based and includes audio, video, and data;
- IBM/Lotus Sametime 3.0 features a SIP gateway;
- RADVISION offers SIP software technology and SIP gateways.
AndyN
IP: Logged |
opatters
Member Posts: 1
From: Lubbock, Texas
Since: Feb 2003
|
posted 07 February 2003 10:14 AM
www.wave3software.com is developing a SIP solution for packed switched networks. Has anyone dealt with their "Solution" product by chance?IP: Logged |
gordon
Member Posts: 11
From:
Since: Mar 2001
|
posted 07 February 2003 01:41 PM
There are many companies facing the same difficult decision as you. It is unlikely that H.323 and SIP will simply co-exist forever as two completely separate standards. Either they will "merge" together or one will clearly overtake the other. But this determination process can easily take another 3-5 years. In the meantime you have systems and applications that you need to deploy.VCON's Media Xchange Manager is a combined Video Network Management System, Gatekeeper and Video PBX. It supports both H.323 and SIP devices. In addition to allowing a mixed network of H.323 and SIP devices, many customers see this dual protocol support as a major investment protection advantage. It allows them to deploy H.323 today but freely add or switch to SIP if appropriate in the future. A specific white paper on this topic can be found at www.vcon.com/solutions/white_papers/. Look for the paper titled "Delivering SIP-H.323 Convergence & Co-Existence". IP: Logged |
asgar
Sr. Member Posts: 71
From:
Since: Nov 2002
|
posted 10 February 2003 08:18 PM
Kelvin:
if you are evaluating SIP for audio, maybe its worth doing a serious evaluation.
But for video, at the moment I think better forget it. I just dont know any endpoint (with more than 1% market share) that supports SIP today (please tell me if I0m wrong). H323 is just starting its mainstream stage! So you will necesarily have compatibility troubles with existing world during at least a couple of year. And not to say about some funcionalities (like suplementary services) still not completely defined by standarts (as I know).
I think its already a significant challenge to solve the end users needs integrating correctly H323 and ISDN. Except if you like complexity and risk!
As I could check, SIP video equipments are "under development". Existing SIP products are essentially audio.In any case (both video and audio), why not evaluate the implementation with a strong H323 platform from a well established manufacturer (ie that will be still on the market in 3 years!) with some comitment to receive SIP upgrade in the future at low cost (or free!!) , and be aware of which components you will have to change? It seems to me that more and more the cost is in the endpoints (except some specific uses like MCU). So if the main part of the investment will survive the change (software upgrade), is the risk worth?
Hope someone disagree and can give me some input I dont have. IP: Logged |
WR Forums
UBBFriend: Email This Page to Someone! 
