SIP Server Requirements

(1)

SIP Server Requirements

By Van-Si Nguyen

Cyklone CTO and Co-Founder

(2)

Introduction

Our company Cyklone is in digital economy business, specialized in video over IP. We are looking for suppliers that can assist us in the development and deployment of Sip Server(s). Specifically, this we are looking for following information:

? Conceptual technical architecture alternatives based on requirements shown below (see Exhibit 1. SIP Requirements).

? Technical feasibility alternatives assessments for the most cost effective solution for SIP Server(s) that offer rich functionality combined with ease of use, installation, and administration:

? Open Source: priority is given to open source solution with full documentation, source code and technical support 24/7 in the USA and Canada.

? Significant attention needs to be paid to standards compliance (see Exhibit 2. Supported Specifications and RFCs) and interoperability.

? The implementation will be done remotely at a Linux server installed in Montreal, Quebec, Canada.

? Approximate cost information (i.e., order of magnitude, ballpark estimates, etc.) for alternatives. ? Schedule estimates.

? Ideas and suggestions that provide alternative approaches to designing, developing a Sip Server.

Suggested Response

Following is a suggested outline for a response to this job offer. This outline is intended to minimize the effort of the respondent and structure the responses for ease of analysis. Nevertheless, respondents are free to develop their response as they see fit.

Section 1 – Feasibility Assessment

Briefly describe the feasibility as matched against the functional requirements. Section 2 – Cost and Schedule Estimates

Provide cost estimates as matched against the functional requirements. Section 3 – Corporate Expertise

Briefly describe your company, your products and services, history, ownership, financial information, and other information you deem relevant.

Include any comments on the structure of the requirements for a formal RFP response. Section 4 – Additional Materials

Please provide any other materials, suggestions, and discussion you deem appropriate.

DISCLAIMER

All information received in response to this Project Offer that is marked Proprietary will be handled accordingly. Responses to the Project Offer will not be returned. Responders are solely responsible for

(3)

CONTACT INFORMATION

Following is the Point of Contact (POC) for this Project Offer, including the public information exchange meeting:

Mr. Van-Si Nguyen

Cyklone CTO and Co-Founder Email: [email protected]

Please submit responses via e-mail in Microsoft Office format by 4:00 PM on October 31st_{, 2006, to the} POC as shown above. You may also submit supplemental hardcopy materials such as brochures, etc. to the POC.

(4)

Exhibit 1. SIP Requirements

Operating

Environment

Component Minimum Requirement

OS

Microsoft Windows XP/2000, Red Hat Linux v8.x/9.x, Solaris 10

Preference: Red Hat Linux v8.x/9.x

Java JDK 1.4 or later Memory 256 MB Minimum Features Your Solution (Y or N) Phones:

? Polycom IP30x, IP50x, IP60x, IP4000, Attendant Console ? Cisco 7960, 7940, 7912, 7905 ? Snom 360 & 320

? Grandstream Budgetone and Handytone

? KDE kphone (softphone) ? Other?

Managed Phones,

Gateways, and

Servers

The Communications Server should support any SIP compliant phone and gateway. Gateways: ? Audiocodes MP1x4, MP1x8 ? Audiocodes TP260 ?

Cisco ATA-186/188

?

Other?

(5)

Managed Phones,

Gateways, and

Servers

Servers:

? Configuration and Management Server

? SIP Proxy Server ? SIP Registrar Server ? SIP Auth Proxy Server ? SIP Status Server ? Presence Server ? Call Park Server ? Conference Server ? Keep Alive Service ? Other?

Dial Plan & Call

Routing Features

? Built-in high performance SIP call router

? Web-based dial plan management ? Policy based call routing based on

individual user permissions ? User configurable call forwarding ? Support for emergency call handling ? Multiple PSTN gateways

? 900 number call blocking

? Definition of custom dialing rules from the Web UI

? Automated dial plan activation ? Rules defined using XML internally

SIP Server PLUG-IN

Accounting Plug in (For controlling a session or collecting call log data for

accounting purposes (ex., radius accounting)

Authentication Plug in (For authenticating

UAs using your own method, e.g. radius authentication)

(6)

IP PBX System

Features

Standards compliant native SIP Call Control Fully redundant call control (HA)

Supports all common PBX features

Supports any SIP phone and PSTN gateway Integrated Web-based management system No special HW required - runs on a Linux server

Plug & Play phone and gateway management

Comprehensive management of users with groups

Comprehensive management of phones with groups

Simple assignment of lines to phones Call park & pickup with multiple park extensions

Multiple line appearances

Call Admission and Authentication Control Direct Inbound Dialing (DID)

Flexible user names with alias

Integrated presence management with presence server

SIP URI dialing

(7)

Exhibit 2. Supported Specifications and RFCs

The following table lists common requirements or features that the SIP Server should support. The level of compliance is defined as follows:

- Yes indicates that The SIP Server container directly supports the feature or specification.

- Yes (Platform Dependent) indicates The SIP Server can host applications or components that implement the feature. However, the feature has no impact on the transaction layer of the protocol or on the behavior of the SIP Servlet container.

STANDARD COMPLIANCE COMMENTS

Advanced Encryption Standard (AES) Ciphersuites for Transport

Layer Security (TLS)

Authentication, Authorization, and Accounting Requirements for the

Session Initiation Protocol (SIP)

Best Current Practices for Third Party Call Control (3pcc) in the

Communicating Presentation Information in Internet Messages: The

Content-Disposition Header Field

Diameter Base Protocol

Diversion Indication in SIP

DoD Standard Transmission Control Protocol

Enumservice Registration for Session Initiation Protocol (SIP)

Addresses-of-Record

Extension to the Session Initiation Protocol (SIP) for Request History

Information

HTTP Authentication: Basic and Digest Access Authentication

Hypertext Transfer Protocol -- HTTP 1.1

Integration of Resource Management and Session Initiation Protocol

(SIP).

Introduction to Community-based SNMPv2

Management Information Base for Version 2 of the Simple Network

Management Protocol (SNMPv2)

Mapping of Integrated Services Digital Network (ISDN) User Part

(ISUP) Overlap Signaling to the Session Initiation Protocol (SIP)

Mechanism for Content Indirection in Session Initiation Protocol (SIP)

Messages

MIME media types for ISUP and QSIG Objects

Offer/Answer Model with Session Description Protocol (SDP)

Privacy Mechanism for the Session Initiation Protocol (SIP)

Private Extensions to the Session Initiation Protocol (SIP) for

Asserted Identity within Trusted Networks

Private Header (P-Header) Extensions to the Session Initiation

(8)

Protocol Operations for Version 2 of the Simple Network

Reliability of Provisional Responses in the Session Initiation Protocol

(SIP)

S/MIME Advanced Encryption Standard (AES) Requirement for the

SDP: Session Description Protocol

Security Multiparts for MIME: Multipart/Signed and

Multipart/Encrypted

Session Initiation Protocol (SIP) Authenticated Identity Body (AIB)

Format

Session Initiation Protocol (SIP) Basic Call Flow Examples.

Session Initiation Protocol (SIP) Extension for Event State

Publication

Session Initiation Protocol (SIP) Extension for Instant Messaging

Session Initiation Protocol (SIP) Extension Header Field for

Registering Non-Adjacent Contacts.

Session Initiation Protocol (SIP) Extension Header Field for Service

Route Discovery During Registration.

Session Initiation Protocol (SIP) Public Switched Telephone Network

(PSTN) Call Flows

Session Initiation Protocol (SIP)-Specific Event Notification

Session Initiation Protocol for Telephones (SIP-T): Context and

Architectures

Simple Network Management Protocol (SNMP)

SIP 183 Session Progress Message Draft

SIP: Session Initiation Protocol

SIP: Session Initiation Protocol (v1)

The Extensible Markup Language (XML) Configuration Access

Protocol (XCAP)

The PINT Service Protocol: Extensions to SIP and SDP for IP Access

to Telephone Call Services

The Reason Header Field for the Session Initiation Protocol (SIP)

The Session Initiation Protocol (SIP) "Join" Header

The Session Initiation Protocol (SIP) Refer Method.

The Session Initiation Protocol (SIP) Referred-By Mechanism

The Session Initiation Protocol (SIP) UPDATE Method

The SIP INFO Method

The TLS Protocol Version 1.0

Transport Mappings for Version 2 of the Simple Network

User Datagram Protocol

User Requirements for the Session Initiation Protocol (SIP) in