Oracle通讯融合应用服务器4.0开发SIP应用指南

需积分: 1 42 浏览量更新于2024-07-23 收藏 628KB PDF 举报

Oracle® Communications Converged Application Server (简称OCAS) 发布的《Developing SIP Applications》是针对 Release 4.0 版本的一份专业指南。SIP（Session Initiation Protocol）是一种网络协议，用于建立、管理和终结多媒体通信会话，尤其在IP语音（VoIP）和视频通信领域中发挥着核心作用。这份文档详细介绍了如何利用OCAS平台开发SIP应用程序，包括但不限于设计原则、架构考虑、API使用以及实现关键功能的方法。该版本发布于2008年8月，强调了版权保护，所有内容受Oracle及其关联公司的版权协议管辖，用户只能在许可协议允许的范围内使用，如复制、修改或分发，且禁止未经许可的逆向工程、解码或反编译行为，除非法律要求为了兼容性目的。文档内容涵盖了以下要点： 1. **环境概述**：首先，读者可以了解到OCAS开发环境的基础配置和系统要求，确保在构建SIP应用时具备必要的硬件和软件支持。 2. **SIP基础知识**：对SIP协议进行深入解析，包括会话管理、请求/响应模型、媒体协商等核心概念，为开发者提供清晰的理论基础。 3. **OCAS API使用**：指南详细介绍了OCAS提供的SIP开发接口，包括如何创建SIP会话、发送和接收消息、处理事件以及集成第三方服务。 4. **示例代码与实践项目**：通过实际的代码片段和案例研究，展示了如何将理论知识转化为实际操作，帮助开发者提升技能。 5. **安全与认证**：强调SIP应用的安全措施，如防火墙配置、身份验证机制以及数据加密，确保通信过程中的信息安全。 6. **错误处理与调试**：提供了常见问题的排查方法，以及如何使用OCAS工具进行调试，以优化应用程序性能。 7. **合规性和法规遵从**：如果文档适用于美国政府或其代表，它还会包含关于联邦信息处理标准（FIPS）和相关法规的要求。 8. **更新和支持**：声明文档可能随时更改，且不保证无误，鼓励用户报告发现的任何错误以便后续改进。《Developing SIP Applications》为Oracle Communications Converged Application Server的用户提供了详尽的指导，旨在帮助他们在利用SIP技术构建高效、安全的应用程序时，充分利用OCAS的功能和优势。这是一份技术含量高且实用性强的参考资料，对于从事SIP应用开发的专业人员来说，具有很高的参考价值。

Overview of SIP Servlets

1-8 Developing Diameter Applications

z SDP (Session Description Protocol)—A protocol to define multimedia sessions used

between terminals. This protocol is defined in RFC2373.

z Presence Information—A message that describes presence information defined in CPIM.

z IM Messages—IM (instant message) body. User-input messages are stored in the message

body.

Since the message body is in a small size, processing it in a streaming way increases overhead.

SIP Servlet re-defines API to manipulate the message body on memory as follows:

SipServletMessage

void setContent(Object content, String contentType)

Object getContent()

byte[] getRawContent()

Roles of a Servlet Container

The following sections describes major functions provided by Oracle Communications

Converged Application Server as a SIP servlet container:

z Application Management—Describes functions such as application management by servlet

context, lifecycle management of servlets, application initialization by deployment

descriptors.

z SIP Messaging—Describes functions of parsing incoming SIP messages and delivering

appropriate SIP servlets, sending messages created by SIP servlets to appropriate UAS, and

automatically setting SIP header fields.

z Utility Functions—Describes functions such as sessions, factories, and proxying that are

available in SIP servlets.

Application Management

Like HTTP servlet containers, SIP servlet containers manage applications by servlet context (see

Figure 6). Servlet contexts (applications) are normally archived in a WAR format and deployed

in each application server.

Note: The method of deploying in application servers varies depending on your product. Refer

to the documentation of your application server.

Differences from HTTP Servlets

Developing Diameter Applications 1-11

A SIP servlet container receives the following three types of SIP messages, for each of which you

determine a target servlet.

z First SIP Request—When the SIP servlet container received a request that does not belong

to any SIP session, it uses filter conditions in the sip.xml file (described in the previous

section) to determine the target SIP servlet. Since the container creates a new SIP session

when the initial request is delivered, any SIP requests received after that point are

considered as subsequent requests.

Note: Filtering should be done carefully. In Oracle Communications Converged

Application Server, when the received SIP message matches multiple SIP servlets, it

is delivered only to any one SIP servlet.

z Subsequent SIP Request—When the SIP Servlet container receives a request that belongs

to any SIP session, it delivers the request to a SIP Servlet associated with that session.

Whether the request belongs to a session or not is determined using dialog ID.

Each time a SIP Servlet processes messages, a lock is established by the container on the

call ID. If a SIP Servlet is currently processing earlier requests for the same call ID when

subsequent requests are received, the SIP Servlet container queues the subsequent requests.

The queued messages are processed only after the Servlet has finished processing the

initial message and has returned control to the SIP Servlet container.

This concurrency control is guaranteed both in a single containers and in clustered

environments. Application developers can code applications with the understanding that

only one message for any particular call ID will be processed at a given time.

z SIP Response—When the received response is to a request that a SIP servlet proxied, the

response is automatically delivered to the same servlet since its SIP session had been

determined. When a SIP servlet sends its own request, you must first specify a servlet that

receives a response in the SIP session. For example, if the SIP servlet sending a request

also receives the response, the following handler setting must be specified in the SIP

session.

SipServletRequest req = getSipFactory().createRequest(appSession, ...);

req.getSession().setHandler(getServletName());

Overview of SIP Servlets

1-12 Developing Diameter Applications

Normally, in SIP a “session” means a real-time session by RTP/RTSP. On the other hand, in

HTTP Servlet a “session” refers to a way of relating multiple HTTP transactions. In this

document, session-related terms are defined as follows:

Oracle Communications Converged Application Server automatically execute the following

response and retransmission processes:

z Sending “100 Trying”—When WebLogic Communications Server receives an INVITE

request, it automatically creates and sends “100 Trying.”

z Response to CANCEL—When WebLogic Communications Server receives a CANCEL

request, it executes the following processes if the request is valid.

a. Sends a 200 response to the CANCEL request.

b. Sends a 487 response to the INVITE request to be cancelled.

c. Invokes a doCancel method on the SIP servlet. This allows the application to abort the

process within the doCancel method, eliminating the need for explicitly sending back a

response.

z Sends ACK to an error response to INVITE—When a 4xx, 5xx, or 6xx response is

returned for INVITE that were sent by a SIP servlet, WebLogic Communications Server

automatically creates and sends ACK. This is because ACK is required only for a SIP

sequence, and the SIP servlet does not require it.

When the SIP servlet sends a 4xx, 5xx, or 6xx response to INVITE, it never receives ACK

for the response.

Table 1-2 Session-Related Terminology

Realtime Session A realtime session established by RTP/RTSP.

HTTP Session A session defined by HTTP Servlet. A means of relating multiple HTTP

transactions.

SIP Session A means of implementing the same concept as in HTTP session in SIP. SIP

(RFC3261) has a similar concept of “dialog,” but in this document this is

treated as a different term since its lifecycle and generation conditions are

different.

Application Session A means for applications using multiple protocols and dialogs to associate

multiple HTTP sessions and SIP sessions. Also called “AP session.”

剩余101页未读，继续阅读

AlexChen0930

粉丝: 0
资源: 1

Oracle通讯融合应用服务器4.0开发SIP应用指南

Introduction to Python Programming and developing GUI applications with PyQT

Developing Flex Applications

DEVELOPING Intranet Applications with Java

Swift Developing iOS Applications 无水印pdf

Developing Android Applications with Adobe AIR

Developing Mobile Applications Development Using Java

Developing Web Applications for WebLogic Server

XML and Java: Developing Web Applications

java-instantcode-developing-applications

Developing Android Applications with Flex 4.5.pdf

最新资源