In the Homisco Intelligent Network Platform (INP), the logic for controlling telecommunications services migrates from traditional switching points to computer-based, service-independent platforms. This provides network operators an open platform provisioned with generic service components that can interoperate with elements from different vendors, based on published, open-interface standards. This platform can be used to develop new and different services. The Homisco IN platform is a prime example of this, an open-standards investment that can migrate services from legacy or our VANX Circuit Based equipment onto a converged IP-based broadband network. It operates equally well with narrowband and broadband switches and provides the perfect stepping stone for operators looking to evolve their networks. The Homisco, Inc. INP architecture is composed of several components (processes), which reside on multiple CPUs. In particular, the IP7server, which provides the SS7-Edge interface can be co-located with the SS7 network edge, and the other INP components are located in a common data-center using TCP/IP as the access method to IP7Server. The INP components include: IP7server: Provides TCAP/SCCP/MTP support utilizing NMS SS7 boards CAPgateway: Acts as a proxy between the actual SCF application and the IP7server’s TCAP-API. CAPgateway provides the following: Performs the CAMEL/CAP BER ASE operation transcoding functions for TCAP component parameters. Refer to the list of Voice Call Control CAP operations. Exports a TCP/IP based API to the SCF application. Performs the Dialogue Section transcoding functions. Interfaces to the IP7server via the TCP/IP based TCAP-API. Performs TCAP transaction management functions. Performs linked dialogue management functions. Handles TC-BEGIN, TC-END, TC-CONTINUE, TC-UABORT, TC-PABORT handling. Handles INVOKE, RESULT, CANCEL, ERROR, REJECT components. Performs dialogue timer services. Provides managed object alarms to OAMPserver for forwarding to the network’s alarm management interfaces via the development of an OAMPproxy adaptor. In a subsequent Phase/Release, TCAP Dialogue Section version negotiation will be supported. CAPgateway may require support of GSM/MAP HLR operations such as the SendRoutingInfoForSM and will be addressed as required using MAPgateway.