Abstract: The Element Management System (EMS) is one that is involved in the development of the functionalities of efficient management of network elements like the DSLAMs that handles high speed digital data streams from numerous subscribers, end users and the network service providers. DSLAM is a broadband access network element that supports multiple DSL transmission types (xDSL) and finds advantageous as it provides an efficient way of broadcasting with reliability and scalability and its support to triple play delivery (audio, video and voice supporting). The essence of EMS is to research with network management system (EMS GUI) that provides configuration, maintenance and the FCAPS (Fault management, Configuration management, Accounting management, Security management) management of the network element. This flexibility ensures the enhanced deployment of novel Network Element (NE) releases, enabling high penetration in market for new services. EMS manages the Session Initiation Protocol (SIP) configuration of DSLAMs as being supported by the integration of multiple types of media. There are SIP versions for the hardware of DSLAMs which evolve in parallel, most of the times independently. Generally, the design of the application will have core component and on top of the plugins that are defined for each version of the hardware release. SIP application is like having SIP core and SIP plugins for each DSLAM version which results in making frequent releases of all of these components on every introduction of a new SIP version. This results in lot of cost involvement, every time developing and making releases of the SIP core and plugins. So, the current design of SIP core application and plugins need to be revisited to reduce the redelivery of all of them for each new SIP version thus providing an optimal design of SIP application. The optimal design of SIP application is obtained by moving the SIP components to the SIP core and making a deviant from the plugins that is dependent of each SIP plugins for the new SIP versions that is being introduced. The former is removed from its content thus breaking the link between the plugins and the core for the updation of the new SIP versions. As a result on introduction of every new SIP version the SIP core to be redelivered to the customer instead of redelivering the entire former SIP core and the SIP plugins as both has a dependency for the new SIP version thus resulting in higher performance and cost effective.