Mapping Connections between c-Bridges |
Mapping is the
term used when connecting c-Bridges via Server Inbound
and Server Outbound connections. The process
creates the pipe or trunk line that carries that "long
distance call" between 2 c-Bridges. Each end of the
pipe is free to bind that trunk to any talkgroup or
timeslot on any of their IPSC Managers. This is a
major advantage of the c-Bridge over peering in on an
existing IPSC network when only 1 c-Bridge is available. |
NOTE: "T6-DCI"
is the name of our c-Bridge and this must be entered
exactly including the hyphen and all upper case or the mapping will
fail. Your c-Bridge
IP and exact name needs to be provided to us if we
do not
already have it.
T6-DCI will initiate a Server Outbound connection and you will initiate a Server Inbound
connection. We will provide you our c-Bridge
Name and a Link ID number. That is all that is
needed to enable the "Mapping" on your side of the
connection. You must provide us with your
c-Bridge IP, that's all. |
Here's how to map connections
between c-Bridges. The example used will create
a "Server Inbound" connection on your end make use
of the "Bridge"
talkgroup (3100). Simply substitute in
your TG name and TG ID if you do not wish to use
3100 and/or change the timeslot on which it appears
on your IPSC Manager. It consists of 2 steps,
the "Mapping" entry itself and then then binding the to the Talkgroup(s) and the timeslot(s) on your IPSC
Manager(s). |
TIP:
We
highly recommend that you use a
defined or reserved series of
numbers for all the Link ID's as there are 3
groups that have the same name, mean something
different and increase the confusion level. |
|
|