Arch2Arch Tab BEA.com
Syndicate this blog (XML)

Difference between WebLogic Communications Platform and WebLogic SIP Server

Bookmark Blog Post

del.icio.us del.icio.us
Digg Digg
DZone DZone
Furl Furl
Reddit Reddit

Ken Lee's Blog | September 10, 2005   9:52 PM | Comments (3)


It is important to understand that WebLogic Communications Platform is not a product, but rather a product family name, which consists of a SIP application server called WebLogic SIP Server, and a policy-based network access control engine called WebLogic Network Gatekeeper. So WebLogic Communications Platform is a product suite that delivers an application development and deployment platform, together with the ability to provide telco's with fine-grain control of which of these applications can access the carrier's network, and at what levels. The product which enables the development, and deployment of next-generation SIP applications is WebLogic SIP Server. VoIP is one use-case for SIP, but since SIP uses RTP (Realtime Transport Protocol) for it's media channel, this means any type of multimedia content type can be delivered as part of a SIP session.

Comments

Comments are listed in date ascending order (oldest first) | Post Comment

  • I have spoken with some large non-telco enterprises that are also considering to converge their networks onto one IP/MPLS based newtork. To me, this seems another large opportunity for bea's WLC. I have heard an example of a large insurance company that is using a SIP server to increase productivity of its call center employees. Obvioulsy, we have yet to see the tipping point for mass adoption of services over IP....Alexander

    Posted by: agnesmuylle on September 11, 2005 at 1:16 AM

  • To say "since SIP uses RTP (Realtime Transport Protocol) for it's media channel" is really to misrepresent the technology (plus it should be "its media channel", without an apostophe ;-) ).

    SIP doesn't have a media channel. SIP messages can carry payloads of arbitrary MIME types, but SDP (Session Description Protocol) is usually used for session setup. The session description in SDP may specify the use of RTP for audio or video, but may equally specify some other protocol or session type.

    Not only is VoIP only one use-case for SIP, so is the setup of an RTP-based session described using SDP.

    Posted by: hepwori on September 15, 2005 at 1:39 PM

  • Yes, SIP is independent of the media transport, and typically uses RTP over UDP, and as such, I wasn't implying that SIP has a pre-specified media channel. And as you've stated, IETF RFC 2327 Session Description Protocol (SDP), which is a structured, text-based media description format that is embedded in SIP messages, is most often used to describe the multimedia streams that are exchanged between the parties of a multimedia session. I completely agree that VoIP is just one "simple" use case of SIP/SDP/RTP, but the set-up of real-time, interactive, multiparty, multimedia sessions over RTP using SDP is the key enabling technology for the next-generation evolution of the Internet and telecom networks.

    Posted by: jusmagk on September 19, 2005 at 12:51 PM



Only logged in users may post comments. Login Here.

Powered by
Movable Type 3.31