Basic Q & A of the SIP Session Initiation Protocol

The SIP Session Initiation Protocol has been added in many systems. Therefore, we have summarized and summarized some problems of the SIP Session Initiation Protocol, hoping to help you solve some problems. For the sip faq, the Session Initiation Protocol SIP Servlet 1.0 support (JSR 116) was added for the first time in IBM WebSphere Application Server V6.1. Since then, the SIP Session Initiation Protocol function and a large number of questions about details have been added. The following are some of the most common questions I have heard about the support of SIP Servlet 1.0, and provides some good reference material links to help you answer many other questions ｡

Which versions of WebSphere Application Server have the SIP Servlet function?

IBM WebSphere Application Server V6.1 basic edition and Express edition have independent SIP Servlet support, but do not provide high availability support. WebSphere Application Server V6.1 Network Deployment has high availability features, including stateless SIP proxy, this proxy provides session Association support for Application Server instances. WebSphere Application Server V7 also provides the SIP Servlet function ｡

Does WebSphere Virtual Enterprise and WebSphere eXtreme Scale include the SIP function?

Yes, both products provide the application server's SIP Session Initiation Protocol deployment function ｡

WebSphere Virtual Enterprise provides the SIP proxy and application server functions, this improves the manageability and quality of the services provided by basic WebSphere Application Server. One function of WebSphere Virtual Enterprise to enhance the management function of SIP applications is, provides the ability to seamlessly upgrade applications while still supporting sessions of existing applications. Another feature is the smart license control function, monitors resources on backend application servers and manages service policies and quality levels based on user sessions, to ensure that appropriate decisions are adopted to ensure that end-to-end latency is met. Many other WebSphere Virtual Enterprise features are applied to all applications and application servers, such as virtualization, application placement, and server health management ｡

WebSphere eXtreme Scale provides better service quality for SIP session replication. In addition, it provides more options for High Availability Topology Design than basic WebSphere Application Server. To improve service quality, webSphere eXtreme Scale provides asynchronous and synchronous replication that allows replication between sessions to ensure the required service level ｡

Can I associate an EJB with a SIP Session Initiation Protocol?

For StateLess Session Bean (SLSB), there is no association or association mechanism. Therefore, SLSB requests cannot be bound to a SIP Association. For StateFul Session Bean, SFSB), the State is maintained after the first access to the Bean. This means that SFSB is often used in such scenarios: When SFSB starts a dialog box and may want to expose the operation in this dialog box ｡

In this case, when the SFSB creation dialog box is displayed, you can ensure that SFSB is called on the same computer that has the SIP dialog box. Our SFSB implementation in WebSphere Application Server uses the Data Replication Service (DRS) as the SIP Session Initiation Protocol). A common setting for sip drs is simply to configure two servers for each replication domain, essentially supporting only peer replication. To bind this SIP-SFSB, this setting is required. Then, if SFSB replication domains are set in the same way, stateful beans are always on the same computer in the startup dialog box. If a Failover occurs, SFSB and SIP sessions fail over to the unique peer in the replication domain ｡