SIP Connector is a key component of SDSE and implements the standardized Session Initiation Protocol signaling stack, fully compliant with IETF RFC 3261 and its several related RFCs. Since SIP stack is a built-in core Connector of Media Routes SDSE, It is implemented in pure ANSI C. It is internally composed of three logical software layers stacked on top of each other:


Transport layer

This is the bottom layer of SIP stack and manages UDP and TCP transport connections for communicating with external entities. It supports sending and receiving SIP messages on transport connections and other tasks as identified in section 18 of SIP RFC 3261, incuding the parsing of incoming SIP messages.


Transaction layer

This layer is stacked on top of the transport layer. It is the central layer of 4G SIP stack. It implements the complete transaction management of SIP protocol as specified in section 17 of SIP RFC 3261. It handles INVITE and non-INVITE SIP transactions in a fully RFC compliant manner.


Connection Manager

This layer is stacked on top of the transaction layer. It manages SIP sessions created as a result of receving a new INVITE or any other non-INVITE message that could create a new session. It manages session objects that act as containers for SIP transactions belonging to the same session. It passes session objects to the higher level application running on top of the stack. The connection manager communicates directly with the user-level application of the stack.


SIP stack also exposes a rich set of utility SIP API. This API includes functions for parsing of SIP messages, creation of new SIP messages, retrieving and setting values in different SIP headers, their fields, attributes and parameters. This API is exposed to the user-application as a set of API, and to the internal layers of the SIP stack as a set of utility functions. It and can be used to manipulate SIP messages in any way desired by  the application or internal stack layers.


SIP Connector implements primitive opertions exposed to application scripts as the SIP API exposed by the stack. The SIP API enables SDSE applications to fully harness the power of SIP stack to create applications and services based on SIP.


Like all other SDSE sub-systems, modules and the run-time system, the SIP stack is built on Media Routes core application development framework called AMPS (Asynchronous Middelware for Parallel Systems). This gives the SIP stack full benefits of AMPS in terms of scalability and high performance.


Copyright All Rights Reserved 2006 to 2013 @ Media Routes Inc