C-Bridge CC-CC Link interface is internal interface of c-Bridge system to implement backbone connections between two server instances.
cBridge System User’s Guide and Reference Manual, page 6
The inbound and outbound connections on a Control Center describe the mechanism of joining two Control Centers together. The diagrams of Figure 2 and Figure 3 gives the impression that two Control Centers are joined together. The actuality is that two Bridge Groups (one from each Control Center) are joined together. When a member of one Bridge Group sends audio, everyone else in the local Bridge Group will hear audio. The members in the Bridge Group on the remote Control Center will hear the same audio. Placing the inbound and outbound connection types together will form one link. At one end (on one Control Center) there is an outbound connection. At the other end of the link (on a different Control Center) there is an inbound connection. The Control Center Outbound describes an entity that goes outside and attempts to connect with something out there. Hence, it is described as an Outbound link. In the specification of the Control Center Outbound, the IP address of the remote Control Center (and the emergency/backup Control Center) is specified. Note the similarity with the operation of the Gateway. On the Gateway, one has to specify the Primary and Secondary Control Center. The Control Center Inbound describes a listening and waiting entity. It waits for the time when the Outbound attempts to build the connection. At this point in time, the Inbound establishes the reception of the link. When defining a Control Center Inbound, one has to specify the sitename and link id of the far end. Note the similarity to defining an incoming Gateway entry for a Bridge Group. The Inbound and Outbound entities allow the site maintainer (at each Control Center) to keep track of who talks where. Conse- quently, users at the remote Control Center are limited to speak into just one Bridge Group. Further, it means that multiple links (between two Control Centers) can be maintained at the same time while maintaining tight control over who talks where. It maybe helpful to think of the Control Center Inbound and Control Center Outbound as an audio circuit. The audio circuit is established in a particular order. The Outbound goes out and builds it - the Inbound waits for the creation event to happen. Once built, audio can be handled in either direction across the link.
BrandMeister can do c-Bridge CC-CC Outbound Link connections for Group Voice Calls and Private Voice + Data. Each link is a separate data pipe that can transmit single call per once. Usually c-Bridge has several links for each talking group and single link for Private Voice + Data.
c-Bridge CC-CC Link uses TCP and UDP ports in range of 42420-42422.
C-Bridge CC-CC Link interface is internal interface of c-Bridge system to implement backbone connections between two server instances.
cBridge System User’s Guide and Reference Manual, page 6
The inbound and outbound connections on a Control Center describe the mechanism of joining two Control Centers together. The diagrams of Figure 2 and Figure 3 gives the impression that two Control Centers are joined together. The actuality is that two Bridge Groups (one from each Control Center) are joined together. When a member of one Bridge Group sends audio, everyone else in the local Bridge Group will hear audio. The members in the Bridge Group on the remote Control Center will hear the same audio. Placing the inbound and outbound connection types together will form one link. At one end (on one Control Center) there is an outbound connection. At the other end of the link (on a different Control Center) there is an inbound connection. The Control Center Outbound describes an entity that goes outside and attempts to connect with something out there. Hence, it is described as an Outbound link. In the specification of the Control Center Outbound, the IP address of the remote Control Center (and the emergency/backup Control Center) is specified. Note the similarity with the operation of the Gateway. On the Gateway, one has to specify the Primary and Secondary Control Center. The Control Center Inbound describes a listening and waiting entity. It waits for the time when the Outbound attempts to build the connection. At this point in time, the Inbound establishes the reception of the link. When defining a Control Center Inbound, one has to specify the sitename and link id of the far end. Note the similarity to defining an incoming Gateway entry for a Bridge Group. The Inbound and Outbound entities allow the site maintainer (at each Control Center) to keep track of who talks where. Conse- quently, users at the remote Control Center are limited to speak into just one Bridge Group. Further, it means that multiple links (between two Control Centers) can be maintained at the same time while maintaining tight control over who talks where. It maybe helpful to think of the Control Center Inbound and Control Center Outbound as an audio circuit. The audio circuit is established in a particular order. The Outbound goes out and builds it - the Inbound waits for the creation event to happen. Once built, audio can be handled in either direction across the link.
BrandMeister can do c-Bridge CC-CC Outbound Link connections for Group Voice Calls and Private Voice + Data. Each link is a separate data pipe that can transmit single call per once. Usually c-Bridge has several links for each talking group and single link for Private Voice + Data.
c-Bridge CC-CC Link uses TCP and UDP ports in range of 42420-42422.
BrandMeister