Slashdot Mirror

← Back to Stories (view on slashdot.org)

SIP: Creating Next-Generation Telecom Applications

Posted by michael on from the fun-with-java dept.

An anonymous reader writes "In this article, you'll discover how the Session Initiation Protocol (SIP) operates and, building on that knowledge, you will learn how to use the Java SIP Servlet API to build new applications that can run on telecommunications networks. The SIP tour concludes with code examples that demonstrate SIP application development in action."

3 of 18 comments (clear)

  1. Yes... by 4of12 · · Score: 3, Interesting

    Another great contribution to providing free public documentation by IBM. Kudoes to them.

    Meanwhile, there's that oncoming train about states requiring VoIP providers to become fully bureaucratically functional telephone providers....

    A good dose of well-meaning out-dated regulation ought to slow down the adoption rate of good new technology.

    --
    "Provided by the management for your protection."
  2. Re:how does SIP compare to Jabber? by Anonymous Coward · · Score: 1, Interesting

    Total agreement. Jabber at least has a consistant, simpler set of syntax and parsing rules, and is more willing to bend on the 'dumb core, smart edge' obsession that besets SIP to the point of idiocy.

  3. Re:When all you have is a hammer.... by isj · · Score: 2, Interesting

    First, IETF does not really control the standards. The standard committees and the working groups do. If a working group prefers HTTP request/response then so be it.

    Second, SIP was developed when HTTP request/response seemed like the new way of doing a lot of stuff. It has disadvantages (verbose, textual, lot of cruft you don't need) and advantages (already specified, clear way of extending it, MIME support)

    Third, SIP and other protocols used/specified by the telecom industry tend to have layer upon layer. If 1 layer is good, then 10 layers must be ten times as good. Have fun looking at OSP (Open Settlement Protocol)