Video Transcript
Core to Core Paging
7m 17s
00:06
Okay, welcome back.
00:07
This is the final section.
00:09
We are going to talk about core-to-core paging.
00:13
What happens when you’ve got multiple paging systems
00:15
and multiple cores in a larger campus, maybe a theme park,
00:21
maybe higher education, something like that?
00:23
You want to be able to send a page from one system to another system.
00:28
When you do that, you don’t want to do it just via channels.
00:34
You don’t want to send an audio channel from Core 1 to Core 2.
00:38
We have components for that. The QAN transmitter and
00:41
receiver are perfect for sending audio channels from one core,
00:44
leaving that core’s environment,
00:46
going across the network, and being picked up by
00:47
another core that has a QAN receiver on it.
00:50
The same thing with the system link transmitter and receivers.
00:52
There are lots of ways that we can send audio channels
00:54
from one system to another system.
00:58
The problem is that when they arrive in the other system,
01:00
it’s just audio; it’s just noise.
01:06
The whole point,
01:07
like we said at the very beginning of this about a PA system,
01:09
is that a page and a message have other intrinsic abilities integrated into them,
01:15
such as their priority settings, their queuing options,
01:19
their retry options,
01:20
and whether they want to be splits or things like that.
01:23
We need all of that metadata that comes with the
01:26
announcements to go with that audio.
01:29
So, we don’t want to rely on audio transmitters and receivers.
01:32
We’re actually going to link the two PA routers together,
01:35
and here’s how you do it.
01:37
Let’s take a look at our PA router.
01:39
In its properties, it’s got some that we haven’t played with yet:
01:42
the remote sources count and the remote destination counts.
01:46
Now, I’ve seen some people, when they first start playing with the PA router,
01:49
if they don’t know what they’re doing,
01:50
they think that remote destinations are zones.
01:53
That’s not what these are for.
01:54
The remote sources and remote destinations are different
01:57
PA routers on a different core that’s all on the same network somewhere.
02:02
So, we’re going to use this PA router as our source,
02:05
and we’re going to send it to another one.
02:07
I’m going to add one remote destination to this PA router.
02:12
When I do that,
02:13
I get a whole bunch more properties here that I need to configure.
02:17
Remote destination one needs a name,
02:21
a type of transmission across the network.
02:23
Generally speaking, you won’t need to deal with most of these,
02:25
but you do need to make sure the name is one that you have selected properly.
02:29
I have named mine A to B.
02:32
A to B is just telling me I’m sending something from Core A to Core B.
02:36
You can name it whatever you want,
02:37
but the name of this link has to be the exact same on
02:40
this system as it is on the other system as well.
02:44
Also, when I open up my PA router,
02:47
I now have a new tab in the control panel
02:50
that is for my remote destination.
02:52
If I look on here,
02:53
I’ve got another channel strip of my destination
02:57
with all the same stuff we get for our local zones,
03:00
and I’ve got some information on the connection status
03:02
between this system and that one.
03:04
So, the first thing I’m going to do is save this design to the core and run it.
03:08
Then, I’m going to go access another core.
03:11
I happen to have another core already.
03:13
Look at this!
03:13
It’s like on those baking shows when they have the
03:16
finished pie already ready in the oven,
03:18
and they’re like, “Look, here it is!”
03:20
And, you know that everything you saw was a lie.
03:22
Everything you saw has been a lie.
03:24
I’ve got another system up and running already on another core.
03:27
I put this mode in dark mode so that you can tell that it’s a different system.
03:32
All it’s got is a real simple PA router in here,
03:35
and this one is running on a Core Nano.
03:37
I’m going to change this PA router to have a remote source of one.
03:44
Once again, I’m going to make sure that it is named A2B,
03:47
so it is the exact same connection with the other PA router.
03:51
You can have your PA routers connect to multiple
03:54
PA routers all over a network as long as there’s a
03:57
unique identifying name that connects each one of them.
04:00
I’ve got that going here.
04:02
In this page station, I’ve got a tab called remote source,
04:06
which gives me the connection status to my original one.
04:09
So, I’m going to save the core and run for my second core as well.
04:13
I’m going to split the screen between these two so that one of them
04:17
is on the left side of my screen and the other one is on the right side of my screen.
04:24
That way, I can see them both simultaneously.
04:28
As it comes up, you can see that indeed both sides show an “okay”
04:33
connected status for that stream connection.
04:36
That means the two PA routers are handshaking;
04:38
they are talking to each other even though they’re on different cores.
04:41
This is perfect.
04:42
Now, before I can send anything from my first core to my second core,
04:46
I’ve got to configure those new zones.
04:49
The way you do that is once again by matching some names.
04:52
I’m going to go to the administrator on my receiving side and
04:56
look at the PA zones I’ve created.
04:57
This one only has a single zone.
04:59
Again, we made it simple. I named it “output.”
05:02
The name of the zone is called “output.”
05:04
On our sending side, we must also go to the administrator, also go to PA zones.
05:10
There’s a new area here called remote tags.
05:14
I’m going to add a new remote tag.
05:18
This must be named the exact same name as you have the zone labeled on the receiving side.
05:24
I’m going to call this “output.” Not the most realistic name,
05:28
but that’s what I’ve got. I’m going to update this side. This side’s good.
05:32
Now, I’ll just go back to my page station.
05:36
Actually, I’m going to go back to my commands,
05:37
and I’m going to adjust that command that we created.
05:40
You can see that we have the remote destinations as
05:43
options for our commands as well.
05:45
I’m going to enable that as part of the destinations we
05:49
get whenever we launch this command.
05:50
I’ll hit “okay” and update that as well.
05:54
So now, let’s go take a look and see if it works.
05:56
I’m going to keep an eye on this PA router’s zone.
06:02
We’ll keep an eye on this here specifically to see if anything is coming in on my sending side.
06:07
I’m going to look right here to see if anything is being sent from the original one.
06:13
I’m going to hit “go” on my physical page station,
06:15
and let’s see if it works.
06:17
There it is.
06:18
Both sides are receiving the game over, man, priority.
06:22
This one is coming in and going out.
06:25
When the first announcement is done,
06:27
it will be the same thing on both sides.
06:29
There it is.
06:31
Easy as that. Line up the names; the zones will connect to each other.
06:37
Now, as they transmit across the cores,
06:39
they retain their priority, their queuing information,
06:42
their splitting, their retry, all the things we need.
06:46
We made it to the end.
06:47
Like I said, paging is wide, right?
06:50
It’s really wide.
06:51
It covers a lot of different places in the design.
06:54
You’ve got to go a lot of different places;
06:55
you’ve got to configure a lot of things.
06:57
In the end, it’s not that complicated.
06:59
You’re still just hitting “go,” sending an announcement, sending a page.
07:03
You just got to know what they are and fine-tune the way that it gets integrated into both sides.
07:09
You’re all done. Thanks for sticking around.
07:12
That was public address. You did it.