Initiated Protocol Telephony Feasibility for the US Navy, Embedded Proof-of-Concept

摘要

The objective of this research paper is to document our experiences building an assured services SIP (AS-SIP) end instrument from a commercial, embedded SIP stack as defined by the DOD Unified Capabilities Requirements specification. The SIP stack chosen came from a company called Unicoi Systems. We chose an existing reference design. The reference design also included a complete SIP phone application embedded into a Fanstel ST-3116 phone. The Unicoi source code could also be cross compiled for nearly any host based platform such as Windows. This report is based on the following research and validation testing: - L-3 Maritime Systems internal research, - L-3 Maritime Systems VoIP lab research, - L-3 Maritime Systems prototyping of a VoIP Communications Terminal,- - Unified Capabilities Requirements 2008, Change 1 Final - L-3 Maritime Systems Technical Report Intelligent Advanced Communications IP Telephony Feasibility for the US Navy, Volumes 1 and 2 (ISRN L3COM/Maritime Systems/TR-2007/001). - Unicoi Fusion RTOS, SIP and networking stacks, call manager and voice engine - REDCOM Slice2100 soft switch with Transip, HDX - GL Communications VoIP quality test tool. - Unicoi Licensing requirements - Wireshark The major findings are: - SIP stack behavior and characteristics vary substantially among vendors. - Unlike traditional TDM based phones, SIP stacks and consequently SIP phones are somewhat switch specific in terms of compatibility. Where you can easily plug a TDM based phone into just about any TDM network, the same is not true for IP phones integrated with the SIP stack or at all. The inherent nature of the embedded environment makes the embedded solution far more secure than a typical PC based soft phone. A closed network environment on board a ship would provide an optimal environment for IP based communications.