No SIP in Sametime 7.5?
by Volker Weber
I know this is an awful slide. The boxes represent components that make up the "next" Sametime client. But this slide contains an interesting piece of information: "SIP ... not supported in Sametime 7.5". What does this mean beyond "no voice"?
Comments
There's a box labelled "Telephony". I wonder how this could be related to SIP ;-)
Perhaps coming post 7.5?
The RTC gateway isn't in the beta, so maybe this is what it means ?
When reading Telephony think CTI.
CTI surely doesn't give anyone the thrills in 2006…
Welcome to The World of Tomorrow, Lotus.
I think what they mean is no SIP in the 7.5 client (the focus of this release). SIP will be supported in the client in 8.0 timeframe I believe. Of course the diagram above does not look like it is a pure client diagram which is odd if what I say is true...
The diagram is a client side diagram. When talking about SIP mostly a SIP gateway is mentioned. So anything is possible.
:-) stw
Some points of clarification. The Sametime 7.5 client does not come with a SIP stack. A SIP stack can be added as a plug-in, and will be done so by IBM in the future. In a future reelase, the Sametime Server and Client will be able to use SIP as its native protocol.
With Sametime 7.5 connectivity to other IM systems will be via the forthcoming Real-Time Collaboration Gateway, which will support the Sametime protocol, IETF ratified SIP, and other variants of SIP (such as that required to connect to AOL).
Telephony/voice integration in Sametime 7.5 can be done in a number of ways. The embedded Voice Chat can be used to talk to other Sametime users (PC-to-PC), with up to 5 people in the conversation. The telephony APIs and SPIs can be used by partners to connect to their systems, with products in market and/or demoed by companies such as Avaya, Siemens, Nortel, and others. And IBM and Cisco have demonstated a Sametime softphone plug-in that talks SIP to Cisco backend.
Gucksdu hier: http://www-128.ibm.com/developerworks/lotus/library/d-ls-sip-sametime/
Post a comment
Recent comments
Alex Wokurka
on No surprises at the PhilNote at 23:14
Ragnar Schierholz
on No surprises at the PhilNote at 23:02
Volker Weber
on No surprises at the PhilNote at 21:53
Ben Poole
on No surprises at the PhilNote at 21:07
Pieterjan Lansbergen
on No surprises at the PhilNote at 21:03
Jan Tietze
on No surprises at the PhilNote at 20:48
Ben Rose
on No surprises at the PhilNote at 15:14
Ben Rose
on No surprises at the PhilNote at 14:46
Philipp Sury
on No surprises at the PhilNote at 13:40
Sascha Reissner
on No surprises at the PhilNote at 13:28
Ben Rose
on No surprises at the PhilNote at 12:10
Colin Williams
on No surprises at the PhilNote at 09:43
Adalbert Duda
on No surprises at the PhilNote at 09:33
Volker Weber
on No surprises at the PhilNote at 09:28
Jan Tietze
on No surprises at the PhilNote at 08:53
Ben Rose
on No surprises at the PhilNote at 08:14
Volker Weber
on No surprises at the PhilNote at 04:50
Amy Blumenfield
on No surprises at the PhilNote at 01:36
Richard Schwartz
on Peter O'Kelly: I am now a Microsoft employee at 02:49
Hanno Zulla
on Ente Chop Sui at 22:32
Kristof Doffing
on Ich helfe gerne aus der Autokrise at 15:03
Bruce Lill
on IBM is not going to send out a press release at 00:31
Thomas Cloer
on Events of the last few days at 12:38
David M Taylor
on Two screens or one? at 03:27
Henrik Heigl
on Events of the last few days at 18:51
Click here to subscribe
