|
Once you have your
c-Bridge peer on the Bridge CPM you will need to take a few
steps to put the data and the voice onto your other
managers. Remember, no repeaters go onto a CPM.
There are 6 key pieces of information
that you as a c-Bridge admin need from the upstream
c-Bridge:
-
c-Bridge IP
(provided by Email to interested
c-Bridge Admins)
-
CPM's UDP port
(provided by Email to interested c-Bridge
Admins)
-
Authorization key
(provided by Email to interested c-Bridge
Admins)
-
Data is on timeslot 1
(List of
other CPMs)
-
Bridge TG on timeslot
2 and it uses TG ID 3100 (List
of other CPMs)
Timeslot 1 and 2 can be reversed at your
end. You can change Data to timeslot 2 and the Bridge
talkgroup to timeslot 1 if you wish if it fits in better
with your talkgroup layout.
First, lets get the Bridge TG voice
working.
-
Using manager 47 as
an example (DCI uses managers 50 and down
for CPM's), Data is on Link ID 93 (manager 47,
TS1) and the Bridge talkgroup is on Link ID 94 (manager
47, TS 2).
-
Go into Bridge Groups
(Configuration/Audio Connections/Group Calling) and
create an entry that looks like the this example below.
Change the site name to match your Control Center name.
-
Go into your Super
Groups for the Bridge TG if you already have a CC and
idle your CC by turning it off but don't delete it yet.
This needed so you don't create a loop between the 2
c-Bridges.
-
If you have never
carried the bridge TG, then you need to create a Super
Group to manage this talkgroup. (This can be done with
Bridge Group bindings only if you prefer)
-
Add the new Bridge
Group above (example: Bridge 94 CPM) into your
Bridge Super Group.
-
If your Bridge
Talkgroup Super Group is new then you need to bind your
other managers into this Super Group if you wish to
enable this Talkgroup.
-
You will now have TG
3100 going out on your Manager on timeslot 2. If
you wish to carry the Bridge on Timeslot 1, then
substitute 93 for the 94 shown above to swap timeslots.
Second, lets get Data
linked up.
-
PVD means Private
Voice / Data and it is on timeslot 1. Leave both
Private Voice and Data Checkmark enabled for now.
You can uncheck Private Voice here if you do not wish to
supply Private Voice ANY manager on your c-Bridge but
wait for now.
-
In the example below
you see that binding 93 matches the editor sample above.
91 shows that Private Voice is disabled while 29 and 31
are enabled for Private Voice. 29, 31 and 91 are
the better place to enable or disable Private Voice
rather than at the CPM 93 if you wish to provide PV to
some managers but not others.
-
Data does not have
Super Groups capabilities but you can create other
Destination Names for Data to handle internally if you
do not wish to have outside data mixed with your
internal data.
-
Data may also be
bound to both timeslots of any or all of your managers
if you wish to have slot neutrality. This is
currently experimental as we have not yet done that
across c-Bridges. We also have not tested fully
for adverse loading nor how active voice may adversely
affect the opposite slot when bound to both timeslots.
Additional thoughts
-
Never bind any
other talkgroups (only Bridge onto TS 2) to either
timeslot of this CPM.
-
Once your CPM
connected Bridge talkgroup is up and working
satisfactorily, you may delete your Conference
Connection if you have one idling. You may wish to
let it idle as it can be a diagnostic tool between
c-Bridges if needed. DCI will leave our CC to you
in place...at least until we run out of CC's (100 max)
unless you tell us you have deleted it at your end.
We would then delete ours.
-
If you wish to test
data, we have some 7/24 radios that you can use.
Radio Checks are handy for end to end testing.
Participating
Test Radios
-
We will be testing
more and provide update in the
Forum dealing with
CPM's.
-
Hopefully the main
USA talkgroups will get this CPM treatment once the
Bridge CPM gets more c-Bridges peering in and we all get
some time onboard to insure that it works well.
-
Your feedback is
welcome in the forum so that everyone can benefit from
your ideas.
|
