Hughes Software Systems

Organization Name of software Contact Type Description 
Hughes Software Systems User Agent Framework
(NEW !!)
siphone@hss.hns.com Framework Framework Library for RAD SIP UA development :
 
  • Maintains SIP call state 
  • Exposes extremely simple APIs like makeCall(), breakCall() which can be used with minimal knowledge of SIP
  • Handles automatic SDP media matching
  • Handles advanced media functions like call hold, codec change etc very simply
  • Support for ISUP bodies
  • Does not dictate any closed-box architecture on the user
  • Easily extendable to perform specialised actions
  • Provides user with high level SIP APIs which can also be directly integrated with the calling application to drastically reduce code.
Hughes Software Systems SIP Lite Stack (NEW !!) siphone@hss.hns.com SIP Stack Small memory footprint ANSI-C based SIP Stack
  • Ideal for small devices
  • Extremely memory efficient
  • Performs complete parsing of SIP messages
  • Handles  torture SIP messages completely.
  • One time parsing
  • Takes less than 150k of memory
  • Footprint can be reduced further and customised as per requirements
  • bis-02  compliant
  • optimised for performance
  • Ideal for embedded systems 
  • Supports any SIP message that is compliant to the SIP BNF, e.g., INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER, INFO
Hughes Software Systems ProtoQuick(tm) SIP Stack siphone@hss.hns.com SIP stack Core SIP Stack based on ANSI-C:
  • C++ APIs for easy development (NEW !!)
  • Support for DCS extensions (plugin-module) (NEW !!)
  • Support for REFER (NEW !!)
  • Fully compliant to SIP bis-02 (SIP) and Notes and Clarifications document
  • Fully compliant to RFC 2327 (SDP)
  • Uses Lex and Yacc-like tools for grammar parsing
  • Supports any SIP message that is compliant to the SIP BNF, e.g., INVITE, ACK, BYE, CANCEL, OPTIONS, REGISTER, INFO
  • Platforms currently supported: Solaris, Linux, Windows, VxWorks. (Other ports available on request)
  • Supports proposed extensions PROPOSE. SIP Caller Preferences draft (Schulzrinne & Rosenberg), SIP-BCP-T, Reliable Provisional Responses, 183 Message, Multipart MIME bodies, and many more.
  • The Stack can support any new message that may be standardized which is compliant to the SIP grammar; 
  • Supports selective header and body parsing for optimizing performance. Also allows users to correct malformed/incorrect headers from other popularly used 3rd party SIP entities.
  • Very easy to plug out components and make the stack more light weight (ideal for handheld devices).
  • Supports both "by Value" and "by Reference" mode of operation of all SIP message components, making development of C++ wrappers very easy.
Hughes Software Systems SIP ADF (Application Development Framework) siphone@hss.hns.com Framework for Rapid Application Development for SIP Registrars, Proxies, Redirects and UAs The SIP ADF is based on the core SIP Stack and provides a very easy -to-use abstraction  which enables 3rd party developers to build SIP entities. The ADF is a powerful framework that encapsulates all the essential SIP behaviours within itself and exposes to the user a very simple set of callbacks and invocations through which the framework can be controlled.
Some salient features:
  • Written in ANSI  C with an Object Oriented approach making it ideal for powerful servers to small handheld devices.
  • Framework components cleanly divided and can be compiled out if not needed (eg one can compile out the Proxy Framework if only a Redirect application is needed).
  • Implements all core functionalities of the SIP protocol and exposes very simple invocations and callbacks to the user .
  • Highly customisable. The user has full control on all policy related parameters as well as parameters where there are more than one possible ways to handle.
  • Higly flexible. The developer can extend the framework to incorporate any new components that s/he may want to add on using well defined interfaces to plugin the same into the ADF.
  • Compliant to all protocol and behaviourial dimensions of the latest SIP RFC (bis draft submitted for RFC).
  • Provides invocation into the core stack as well for users who want to use the simplicity of the framework as well as the raw power of the core stack in certain situations.

Last updated  by Henning Schulzrinne