BEAWebLogic SIP Server - Oracle
BEA WebLogicServer Release NotesVersion 3.0Revised: December 13, 2006SIP
CopyrightCopyright 1995-2006 BEA Systems, Inc. All Rights Reserved.Restricted Rights LegendThis software is protected by copyright, and may be protected by patent laws. No copying or other use of this software ispermitted unless you have entered into a license agreement with BEA authorizing such use. This document is protectedby copyright and may not be copied photocopied, reproduced, translated, or reduced to any electronic medium or machinereadable form, in whole or in part, without prior consent, in writing, from BEA Systems, Inc.Information in this document is subject to change without notice and does not represent a commitment on the part of BEASystems. THE DOCUMENTATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDINGWITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. FURTHER, BEA SYSTEMS DOES NOT WARRANT, GUARANTEE, OR MAKE ANYREPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE DOCUMENT INTERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.Trademarks and Service MarksCopyright 1995-2006 BEA Systems, Inc. All Rights Reserved. BEA, BEA JRockit, BEA WebLogic Portal, BEAWebLogic Server, BEA WebLogic Workshop, Built on BEA, Jolt, JoltBeans, SteelThread, Top End, Tuxedo, andWebLogic are registered trademarks of BEA Systems, Inc. BEA AquaLogic, BEA AquaLogic Data Services Platform,BEA AquaLogic Enterprise Security, BEA AquaLogic Interaction, BEA AquaLogic Interaction Analytics, BEAAquaLogic Interaction Collaboration, BEA AquaLogic Interaction Content Services, BEA AquaLogic Interaction DataServices, BEA AquaLogic Interaction Integration Services, BEA AquaLogic Interaction Process, BEA AquaLogicInteraction Publisher, BEA AquaLogic Interaction Studio, BEA AquaLogic Service Bus, BEA AquaLogic ServiceRegistry, BEA Builder, BEA Campaign Manager for WebLogic, BEA eLink, BEA Kodo, BEA Liquid Data forWebLogic, BEA Manager, BEA MessageQ, BEA SALT, BEA Service Architecture Leveraging Tuxedo, BEA WebLogicCommerce Server, BEA WebLogic Communications Platform, BEA WebLogic Enterprise, BEA WebLogic EnterprisePlatform, BEA WebLogic Enterprise Security, BEA WebLogic Express, BEA WebLogic Integration, BEA WebLogicJava Adapter for Mainframe, BEA WebLogic JDriver, BEA WebLogic Log Central, BEA WebLogic Mobility Server,BEA WebLogic Network Gatekeeper, BEA WebLogic Personalization Server, BEA WebLogic Personal Messaging API,BEA WebLogic Platform, BEA WebLogic Portlets for Groupware Integration, BEA WebLogic Real Time, BEAWebLogic RFID Compliance Express, BEA WebLogic RFID Edge Server, BEA WebLogic RFID Enterprise Server,BEA WebLogic Server Process Edition, BEA WebLogic SIP Server, BEA WebLogic WorkGroup Edition, BEAWorkshop for WebLogic Platform, BEA Workshop JSP, BEA Workshop JSP Editor, BEA Workshop Struts, BEAWorkshop Studio, Dev2Dev, Liquid Computing, and Think Liquid are trademarks of BEA Systems, Inc. AcceleratedKnowledge Transfer, AKT, BEA Mission Critical Support, BEA Mission Critical Support Continuum, and BEA SOASelf Assessment are service marks of BEA Systems, Inc.All other names and marks are property of their respective owners.
Contents1. WebLogic SIP Server 3.0 Features and ChangesWhat’s New in WebLogic SIP Server 3.0? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Based on WebLogic Server 9.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Geographically-Redundant Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Diameter Base Protocol and IMS Ro, Rf Interface Support . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Engine Tier Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2RDBMS Storage for Long-Lived Call State Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Minimal Transactional Latency with JRockit Deterministic Garbage Collection . . . . . . . . 1-3Production Upgrade for Converged SIP/HTTP Applications . . . . . . . . . . . . . . . . . . . . . . . . . 1-3SCTP Support for Diameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3DNS Support for Proxy Discovery and Response Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3IPv6 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Configurable Server Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Configuration of SIP Message Header Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Extended API for Resolving TelURLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5SAR File Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Extended Profile API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Connection Pooling for Re-Use of TCP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Support for Globally-Routable User Agent URIs (GRUU). . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6WebLogic SIP Server Headers and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6What’s New in WebLogic SIP Server 2.2? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7New RFC Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7WebLogic SIP Server 3.0 Release Notesiii
Changes for 3GPP Application Server Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7Diameter Sh Interface, Relay Node Support, and Profile Service API . . . . . . . . . . . . . . . . .1-8Support for SIP UPDATE Method (RFC3311). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9Path Header Support (RFC3327). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9Support for SIP REFER Method (RFC3515). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9Changes to SIP Request Authentication for 3GPP TS 24.229 . . . . . . . . . . . . . . . . . . . . . . . .1-10Support for X-3GPP-Asserted-Identity Header (3GPP TS 33.222) . . . . . . . . . . . . . . . . . . . .1-12Converged Application Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12Production Application Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12Improved Failover Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12Content Indirection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13Reliable Provisional Responses (RFC 3262). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13Support for Modifying Contact Header Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-14New Example Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-14Support for Generating SNMP Traps from SIP Servlets . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-14Default SIP Servlet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15What’s New in WebLogic SIP Server 2.1? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15Architectural Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16Application Porting Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16New Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17datatier.xml Changes (Formerly statetier.xml) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17Load Balancer Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17Changes in Queue Length-Based Overload Protection . . . . . . . . . . . . . . . . . . . . . . . . .1-17sipserver.xml Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18Network Configuration Using Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18Access Logging Configuration Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18Container Changes for send() Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-19ivWebLogic SIP Server 3.0 Release Notes
What’s New in WebLogic SIP Server 2.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Deprecated Features in WebLogic SIP Server 2.0 SP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-192. WebLogic SIP Server 3.0 Known Issues3. Resolved Problems in WebLogic SIP Server 2.24. Resolved Problems in WebLogic SIP Server 2.15. Resolved Problems for Service Pack 2WebLogic SIP Server 3.0 Release Notesv
viWebLogic SIP Server 3.0 Release Notes
CHAPTER1WebLogic SIP Server 3.0 Features andChangesWelcome to BEA WebLogic SIP Server 3.0! WebLogic SIP Server integrates SIP Servlettechnologies with J2EE 1.4 and 1.3 and other leading Internet standards to provide a reliableframework for developing highly available, scalable, and secure telecommunicationsapplications. WebLogic SIP Server’s seamless integration of disparate, heterogeneous platformsand applications enables your network to leverage existing software investments and share theenterprise-class services and data that are crucial to building next-generation telephonyapplications.The following sections describe the new features and changes made in the WebLogic Server 3.0general release and in intermediate releases:z“What’s New in WebLogic SIP Server 3.0?” on page 1-1z“What’s New in WebLogic SIP Server 2.2?” on page 1-7z“What’s New in WebLogic SIP Server 2.1?” on page 1-15z“What’s New in WebLogic SIP Server 2.0 SP2” on page 1-19z“Deprecated Features in WebLogic SIP Server 2.0 SP1” on page 1-19What’s New in WebLogic SIP Server 3.0?This section describes new features and functionality introduced in WebLogic SIP Server 3.0.WebLogic SIP Server 3.0 Release Notes1-1
We bLo gi c SI P S e r v e r 3 . 0 F e a t ur e s a nd C h an gesBased on WebLogic Server 9.2WebLogic SIP Server 3.0 is deployed on the core BEA WebLogic Server 9.2 product, whichintroduces many key features such as J2EE 1.4 compliance, improved systems management, andhigher performance, scalability, and availability. See What's New in WebLogic Server 9.2 in theWebLogic Server 9.2 documentation.Geographically-Redundant PersistenceWebLogic SIP Server can be installed in a geographically-redundant configuration for customerswho have multiple, regional data centers, and require continuing operation even after acatastrophic site failure. The geographically-redundant configuration enables multiple WeblogicSIP Server installations (complete with engine and data tier clusters) to replicate call statetransactions between one another. Administrators can then choose to redirect all network trafficto the secondary, replicated site to minimize lost calls if they determine that a regional site hasfailed. See Configuring Geographically- Redundant Installations in Configuring and ManagingWebLogic SIP Server.Diameter Base Protocol and IMS Ro, Rf Interface SupportIn addition to the Diameter Sh protocol provider introduced in WebLogic SIP Server 2.2, version3.0 includes new providers for the Ro and Rf protocols. The base Diameter protocolimplementation is also now available for developers who want to implement additional Diameterapplications. See the following links in Developing Applications with WebLogic SIP Server formore information:zUsing the Diameter Base Protocol APIzUsing the Diameter Rf Interface Application for Offline ChargingzUsing the Diameter Ro Interface Application for Online ChargingEngine Tier CachingThe engine tier can now optionally cache a portion of the SIP call state data available in data tierreplicas. The cache can be used in combination with a SIP-aware load balancer to increaseperformance when accessing call state data. See Enabling the Engine Tier Cache in Configuringand Managing WebLogic SIP Server.1-2WebLogic SIP Server 3.0 Release Notes
W ha t ’s New in W ebL ogi c S IP Ser ve r 3.0 ?RDBMS Storage for Long-Lived Call State DataWebLogic SIP Server 3.0 enables you to store long-lived call state data in an Oracle RDBMS inorder to conserve RAM. The data tier persists a call state’s data to the RDBMS after the calldialog has been established, and retrieves or deletes the persisted call state data as necessary tomodify or remove the call state. BEA also provides an API for application designers to provide“hints” as to when the data tier should persist call state data. See Storing Call State Data in anRDBMS in Configuring and Managing WebLogic SIP Server.Minimal Transactional Latency with JRockit DeterministicGarbage CollectionWebLogic SIP Server can be licensed in a “real time” configuration, which uses the JRockitdeterministic garbage collector to greatly improve latency performance for SIP transactions. Toenable this garbage collector, see Using JRockit Deterministic Garbage Collection in theConfiguration Guide.Production Upgrade for Converged SIP/HTTP ApplicationsWebLogic SIP Server 3.0 introduces application upgrade support for converged SIP/HTTPapplications. Application upgrade support now closely models the upgrade support available inWebLogic Server 9.2, and provides for a SIP “administration channel” that can be used tosecurely testing applications in a production environment. See Upgrading Deployed SIPApplications in the Operations Guide.Note: As part of the new upgrade functionality, SipApplicationRuntimeMBean is nowdeprecated for obtaining information about the applciation name and version string. UseApplicationRuntimeMBean instead.SCTP Support for DiameterWebLogic SIP Server supports the SCTP transport protocol on certain operating systems forDiameter network traffic. See Configuring Diameter Client Nodes and Relay Agents inConfiguring Network Resources.DNS Support for Proxy Discovery and Response RoutingWebLogic SIP Server 3.0 now supports DNS for resolving the transport, IP address and portnumber of a proxy required to send a SIP message as described in RFC 3263. DNS may also usedWebLogic SIP Server 3.0 Release Notes1-3
We bLo gi c SI P S e r v e r 3 . 0 F e a t ur e s a nd C h an geswhen routing responses in order to resolve the IP address and port number of a destination. Priorto version 3.0, DNS resolution had to be performed by the individual UA or proxy application.See Enabling DNS Support in Configuring Network Resources.IPv6 SupportWebLogic SIP Server supports IPv6 for external network interfaces as described in RFC 2460:Internet Protocol, Version 6 (IPv6) Specification. To use IPv6, your underlying operating systemmust support the protocol, and you must configure IPv6 network channels on all engine tier servernodes. See IPv4 and IPv6 in Configuring Network Resources.Configurable Server HeaderThe Administrator can optionally configure the contents of the Server header that WebLogic SIPServer inserts into SIP message bodies. The entire header contents can be omitted to reduce themessage size for wireless networks, or it can be set to an arbitrary string value. Prior to version3.0, the header was always populated with the name and version of the WebLogic SIP Serverinstance. See server-header and server-header-value in the Configuration Reference.Configuration of SIP Message Header FormatsWebLogic SIP Server provides flexible configuration parameters and APIs for controllingwhether generated SIP messages use compact or long header forms. Header form rules can be setat three different levels:zContainer-level configuration: Set the default rules for using compacting headers usingelements in the sipserver.xml file. See use-header-form in the Configuration Reference.zMessage-level API: The WlssSipServletMessage interface provides thesetUseHeaderForm method to specify long or compact headers for a given SIP message.See Using Compact and Long Header Formats for SIP Messages in DevelopingApplications.zHeader-level API: The JSR 116 SipServletMessage interface provides the setHeadermethod to set a given header name a specific value. See the JSR 116 JavaDoc HeaderForm can be used in combination withSipServletMessage.setHeader and the container-level configuration to customize headerformats. See Using Compact and Long Header Formats for SIP Messages in DevelopingApplications for information about how the different settings interact with one another.1-4WebLogic SIP Server 3.0 Release Notes
W ha t ’s New in W ebL ogi c S IP Ser ve r 3.0 ?Extended API for Resolving TelURLsWebLogic SIP Server extends the javax.servlet.sip.TelURL interface with thecom.bea.wcp.sip.WlssTelURI interface. The extended interface enables applications toresolve Tel URLs present in the user portion of a SIP URI. The API parses a Tel URL into adomain name using the standard suffix, e164.arpa, as described in RFC 3761. It then performsa DNS NAPTR record lookup to produce an ENUM NAPTR record set.For example, for a Tel URL domain name of 4.3.2.1.5.5.5.5.1.4.1.e164.arpa, the APIperforms a DNS lookup to retrieve an ENUM NAPTR record set similar to: ORIGIN 4.3.2.1.5.5.5.5.1.4.1.e164.arpaIN NAPTR 100 10 "u" "E2U sip""! .* !sip:user@example.com!"IN NAPTR 100 20 "u" "E2U mailto" "! .* !mailto:info@example.com!"Methods in the WlssTelURI interface return either the full ENUM record set, an array of SIPURIs present in the record set, or only the highest-precedence SIP URI present in the record set.See com.bea.wcp.sip.WlssTelURI in the JavaDoc.SAR File DeploymentWebLogic SIP Server 3.0 supports deployment of applications in SAR file format. The SAR fileis similar in format to WAR files, and can contain deployment descriptor information for bothHTTP and SIP Servlets. SAR files need not include a weblogic.xml deployment descriptor.Extended Profile APIWebLogic SIP Server includes a public profile service API, com.bea.wcp.sip.profile.API,that you can use to create profile provider implementations. A profile provider performs the workof accessing XML documents from a data repository using a defined protocol. Deployed SIPServlets and other applications need not understand the underlying protocol or the data repositoryin which the document is stored; they simply reference profile data using a custom URL usingthe provider API, and WebLogic SIP Server delegates the request processing to the correctprovider. See Developing Custom Profile Providers in Developing Applications with WebLogicSIP Server.Connection Pooling for Re-Use of TCP ConnectionsWebLogic SIP Server includes a new connection pooling mechanism to minimize unnecessarycommunication with a Session Border Control (SBC) function or Serving Call Session ControlWebLogic SIP Server 3.0 Release Notes1-5
We bLo gi c SI P S e r v e r 3 . 0 F e a t
z“What’s New in WebLogic SIP Server 2.0 SP2” on page 1-19 z“Deprecated Features in WebLogic SIP Server 2.0 SP1” on page 1-19 What’s New in WebLogic SIP Server 3.0? This section describes new features and functionality introduced in WebLogic SIP Server 3.0.
SIP SIP phones Blustar 8000i NA SIP SIP phones 9112i, 9133i, 480i Not Supported SIP SIP phones 673xi ( A673xi), 675xi ( A675xi) NA SIP SIP phones 6735i, 6737i ( A6735i, A6737i) NA SIP SIP phones 6739i NA SIP SIP phones 6863i, 6865i, 6867i NA SIP MiVoice Conference phone (UC360
C O N T E N T S Configuration of SIP Trunking for PSTN Access SIP-to-SIP 1 Finding Feature Information 1 Configuration of SIP Trunking for PSTN Access SIP-to-SIP Features 1 Configuring SIP Registration Proxy on Cisco UBE 3 Finding Feature Information 3 Registration Pass-Through Modes 4 End-to-End Mode 4 Peer-to-Peer Mode 5 Registration in Different Registrar Modes 7
Call Flow Scenarios for Successful Calls This section describes call flows for the following scenarios, which illustrate successful calls: SIP Gateway-to-SIP Gateway—Call Setup and Disconnect, page 7-3 SIP Gateway-to-SIP Gateway—Call via SIP Redirect Server, page 7-6 SIP Gateway-to-SIP Gateway—Call via SIP Proxy Server, page 7-9
How To Guide: SIP Trunking Configuration Using the SIP Trunk Page 6(19) 2.2 The SIP Trunk Page The SIP Trunk pages are found under SIP Trunks. Several SIP Trunk pages may be defined if you have several PBXs or Trunk Services. You need to purchase Additional Trunk Group licensees to get more than one SIP Trunk page. Details are found below. s d he n
To support SIP trunks through a SIP trunk service provider, the SIP Trunk Groups folder was added to the SIP Peers folder in DB Programming. To create a SIP Trunk Group for Fusion Connect Service Provider, navigate to System- Device and Feature Codes- SIP Peers- SIP Trunk Groups and right click in the right hand pane. Then select "Create SIP .
4. SIP, VVoIP and QoS 5. SIP and Media Security 6. STIR/SHAKEN and the 'identity' problem 7. Firewalls, NAT and Session Border Controllers 8. SIP Trunking 9. Testing, Troubleshooting and Interoperability 10. ENUM, Peering and Interconnect 11. SIP in the Cloud 12. SIP in Cellular networks 13. SIP and Fax over IP 14. SIP in UC, UCaaS and .
How to Guide: SIP Trunking Configuration using the SIP Trunks page 4 2.2 The SIP Trunk Page The SIP Trunk pages are found under SIP Trunks. Several SIP Trunk pages may be defined if you have several PBXs or Trunk Services. You need to purchase Additional Trunk Group licensees to get more than one SIP Trunk page. Details are found below. s d he Tru
12/16/2017 5136637 lopez damien 12/16/2017 5166979 lorenzano adam 12/16/2017 5117861 mejia martin 12/16/2017 5113853 milner gabriella 12/16/2017 5137867 navarro david 12/16/2017 5109380 negrete sylvia 12/16/2017 4793891 piliposyan alexander
