Gate Synchronization Procedure

When the IPC connection between the PGCP process and the MultiServices PIC is being reestablished, a synchronization process restores the previous state of gates, so session and call continuity is achieved. That is, existing calls stay active and voice sessions are not disconnected.

The synchronization process can result in the mismatching of gates. Mismatched gates are handled as follows:

• If the PGCP process detects gates that exist in the Routing Engine, but are missing in the PIC, the PGCP process reinstalls the gates on the PIC. Existing calls receive service from the PIC when the synchronization is complete.
• If the PGCP process detects gates that exist on the PIC, but not on the Routing Engine, the PGCP process removes the gates from the PIC. This removal causes the associated sessions to be closed, and the session resources to be released.
• If the PGCP process detects gates that exist on the PIC and on the Routing Engine, but the versions of the gates do not match, the PGCP process forces the Routing Engine version. Doing so maintains call continuity by making sure that the databases are synchronized, while limiting the effect to existing calls and sessions.

You can control the number of mismatches by configuring the synchronization properties.

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.