Arch2Arch Tab BEA.com
Syndicate this blog (XML)

What's New in WebLogic SIP Server 2.2

Bookmark Blog Post

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

Sheng Sheen's Blog | May 18, 2006   6:51 AM | Comments (0)


  • Improved system performance
  • Converged Application API that allows for application-based monitoring and call control
  • Supports for Reliable messaging
  • Manage large content payloads through indirection
  • Supports for the Diameter Sh interface for user-profile lookups
  • Improved the ability to do quick application upgrades\transitions
  • Made the server more reliable on its own and in a cluster

New RFCs Supported:

  • RFC 2543: SIP: Session Initiation Protocol (v1) backward compatibility is supported
  • RFC 3262: Reliability of Provisional Responses in the SIP is supported
  • RFC 3327: SIP Extension Header Field for Registering Non-Adjacent Contacts is supported
  • RFC 3515: The SIP REFER Method is supported

RFC 3262: Reliability of Provisional Responses in the SIP is supported

  • As defined in http://www.ietf.org/rfc/rfc3262.txt
    SIP Servlets can acknowledge a provisional response (and stop retransmissions of prvisional response)
  • Create a PRACK request using com.bea.wcp.sip.WissSipServletResponse.createPrack() method
  • Also JSR116’s SipServletResponse.createAck() was modified to automatically return a PRACK request instead of an ACK request for provisional responses
  • Either method can be used to acknowledge provisional responses





  • Requireed by 3GPP IMS, WLSS provides limited support for modifying Contact header parameters
  • Applications can use the SipServletMessage.getAddressHeader(“Contact”) method to return a Contact address object whose parameters can be modified
  • Additionally, UAS can modify Contact header parameters for a 200 response to an OPTIONS request, as required in RFC 3261





RFC 3515: The SIP REFER Method is supported
WLSS supports the SIP refer-to header and REFER method for applications that implement services such as:
  • Unattended call transfer
  • Attended call transfer
  • Third-party call control (3PCC)

Main difference in SIP dialog processing:

  • Implicit subscription is used
  • WLSS maintain a SIP dialog after the REFER method is used even if a subsequent BYE message is sent to ensure call transfer applications can re-establish the original session (via an INVITE) if the call transfer fails
  • Extends the JSR116 SipServlet class to provide a method for handling the REFER request, extend com.bea.wcp.sip.WissSipServlet and implement doRefer()






  • WLSS 2.2 enables you to store call state data in an Oracle RDBMS instead of using a cluster of data-tier servers
  • Only recommended if you have a very large amount of long-lives call state data and you do not have strict requirements for latency performance
  • New failover detection mechanism to improve failover performance for data tier server
  • Engine tier caching is available optionally, used with SIP-aware load balancer to increase performance
  • Upgrade a deployed SIP application to a different version without losing calls that the application is currently processing
    Supports two different versions of the same application



More information can be found in the new product documentation:
http://edocs.bea.com/wlcp/wlss22/notes/new.html#whatsnew


Comments

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



Only logged in users may post comments. Login Here.

Powered by
Movable Type 3.31