Call processor system and methods

A system for implementing a high-availability architecture comprising:

• a first compact Peripheral Component Interconnect shelf;
• a second compact Peripheral Component Interconnect shelf;
• and
• a network;
• wherein the first and second compact peripheral component interconnect shelf are redundant systems;
• wherein the network comprises a three-port extender, XNET, XPEC, and a line card.

A method for a graceful switchover in a system for implementing a high-availability architecture comprising a first computer system and a second computer system wherein the first and second computer systems are redundant systems, the method comprising:

• taking a semaphore for Pdata and file access for the first computer system;
• shutting down a core to network interface of the first computer system and shutting down interfaces to a network;
• locking interrupts of the first computer system and stopping an operating system from running;
• saving state information of a processor of the first computer system;
• suspending a heartbeat task in the second computer system;
• closing files in the second computer system;
• closing an interface in the second computer system;
• locking interrupts in the second computer system;
• transferring state information of the processor via a high speed pipe to the second computer system;
• restoring a processor of the second computer system to the state of the first computer system using the state information;
• unlocking interrupts of the second computer system;
• setting IP active of the second computer system;
• enabling a core to network interface of the second computer system;
• giving a semaphore for the second computer system;
• and
• unlocking interrupts of the first computer system, killing regular tasks of the first computer system, changing a logical call server state to inactive, testing the operating system of the first computer system, and setting IP to inactive.

A software module structure for implementing redundancy control in a system for implementing a high-availability architecture comprising a first computer system and a second computer system wherein the first and second computer systems are redundant systems, the software module structure comprising:

• an applications layer;
• an application adaptors layer;
• an operating system extensions layer, comprising
• a logical call server module for managing the first computer system and the second computer system redundant state, controlling state transitions, coordinating redundancy-related operations, and controlling inter-CPU tasks, voting, heartbeat and protected data synchronization, and protected data updating, and
• a disk redundancy module;
• a real-time operating system kernel layer;
• a TCP/IP stack layer;
• a lightweight protocol stack layer;
• a hardware abstraction layer;
• a board support package layer;
• and
• wherein the logical call server module comprises:
• a vote state;
• a redundant/active and down state which occurs from the vote state or from the redundant/active, redundant/inactive state;
• a switch state which occurs from the vote state;
• a split/inactive, split/active state which occurs from the switch state or from the split/active, split/inactive state or from the redundant/inactive, redundant/active synch state;
• a split/active, split/inactive state which occurs from the switch state or from the split/inactive, split/active state or from the redundant/active, redundant/inactive synch state;
• a redundant/inactive, redundant/active state comprising a redundant/inactive, redundant/active synch state, a redundant/inactive, redundant/active update state, and a redundant/inactive, redundant/active highspeed pipe down state;
• a redundant/active, redundant/inactive state comprising a redundant/active, redundant/inactive synch state, a redundant/active, redundant/inactive update state, and a redundant/active, redundant/inactive highspeed pipe down state;
• wherein,
• the redundant/inactive, redundant/active synch state occurs from the switch state or from the split/inactive, split/active state or from the redundant/inactive, redundant/active high speed pipe down state;
• the redundant/inactive, redundant/active update state occurs from the redundant/inactive, redundant/active synch state or from the redundant/active, redundant/inactive update state;
• the redundant/inactive, redundant/active high speed pipe down state which occurs from the redundant/inactive, redundant/active synch update state;
• the redundant/active, redundant/inactive synch state occurs from the switch state or from the split/active, split/inactive state or from the redundant/active, redundant/inactive high speed pipe down state or from the redundant/active, done state or from the redundant/inactive, redundant/active state;
• the redundant/active, redundant/inactive update state occurs from the redundant/active, redundant/inactive synch state or from the redundant/inactive, redundant/active update state;
• and
• the redundant/active, redundant/inactive high speed pipe down state occurs from the redundant/active, redundant/inactive synch update state.