|
0:00:13
|
OK. So for our next Task 15.10
|
|
0:00:17
|
Endpoint Registration with an External SIP Proxy Server
|
|
0:00:21
|
We´re told to configure Branch2 Router3 to register all of it´s
|
|
0:00:24
|
skinny and SIP endpoints with an external SIP proxy server
|
|
0:00:29
|
that´s currently being hosted based on the start up configs
|
|
0:00:32
|
on Corporate Headquarter Router1 loop back interface.
|
|
0:00:35
|
We´re told to go ahead and register all E164 numbers
|
|
0:00:38
|
in the range of the 3000 series of DID numbers
|
|
0:00:42
|
to the SIP proxy server but ensure that they register
|
|
0:00:45
|
with their entire E164 number not including
|
|
0:00:48
|
plus, so for example contry code 31
|
|
0:00:52
|
geographic code 20 703 3001
|
|
0:00:58
|
then 31 20 703 3002 and of course
|
|
0:01:03
|
so on and so forth for the entire 3001 series range.
|
|
0:01:07
|
Now I´ll tell you to begin with, we don´t have a
|
|
0:01:09
|
proper SIP proxy server, we´re just using the router as one
|
|
0:01:13
|
and it´s really meant for CNE operations.
|
|
0:01:16
|
So our Corporate Headquarter router has very simply then configured
|
|
0:01:22
|
with show run type2 section voice service.
|
|
0:01:29
|
VOIP not voice service voice
|
|
0:01:35
|
and we just turned down register our server
|
|
0:01:37
|
OK, everything´s bound to the loop back or SIP.
|
|
0:01:41
|
So we got to SIP register our server
|
|
0:01:46
|
then clear off our previous configuration so
|
|
0:01:50
|
what we´re going to do to register is first,
|
|
0:01:54
|
we´re going to jump in to the Branch2 Router3 and issue the,
|
|
0:02:04
|
issue the SIP UA configuration area
|
|
0:02:10
|
SIP user agent which can be a UAS or UAC user agent
|
|
0:02:14
|
server or user agent client depending on whether it´s
|
|
0:02:17
|
initiating or actually receiving or initiating the
|
|
0:02:21
|
connection respectively, so SIP UA and under here we can say
|
|
0:02:27
|
a lot of things that set our user agent client or server parameters
|
|
0:02:32
|
but we can say registrar, now registrar should not be confuse here
|
|
0:02:40
|
I´m going to do a do show run type2 section voice
|
|
0:02:44
|
service VOIP
|
|
0:02:48
|
shouldn´t be confused with registrar server
|
|
0:02:50
|
here, if I just say registrar and expires.
|
|
0:02:55
|
I´m simply saying, I am a registrar server turn it on
|
|
0:02:59
|
under the SIP UA and I put in registrar
|
|
0:03:04
|
if asking me for a server address, this is the server that
|
|
0:03:08
|
I as a gateway, want to register too as a gateway
|
|
0:03:12
|
the entire gateway and all entities on it so
|
|
0:03:17
|
I´m going to say 177.1.254.1 which is the loop back of
|
|
0:03:22
|
Corporate Headquarter Router1 and I can do expires
|
|
0:03:26
|
and secondary and etcetera, but I´m just going to say
|
|
0:03:28
|
just that number before I do that, I want to be over here
|
|
0:03:32
|
and I want to say debug ccsip messages and again
|
|
0:03:41
|
we´re not going to see them succeed in registering
|
|
0:03:44
|
but we will see them trying to register. Alright, so soon as I say this
|
|
0:03:51
|
of course I have to put it in IPV for format
|
|
0:03:54
|
just like a session target
|
|
0:03:59
|
as soon as I see this I begin getting registrations over here
|
|
0:04:03
|
on my Corporate Headquarter router I get
|
|
0:04:06
|
DN 3001, now wait a minute that was a skinny phone.
|
|
0:04:09
|
Yes, unless I have no reg at the end of an ephone DN number
|
|
0:04:16
|
then it tries to register with anything the gateway is registering with
|
|
0:04:20
|
be at a H323 gate keeper which is what most folks are used to
|
|
0:04:24
|
or a SIP proxy server. OK? So it received a register message
|
|
0:04:31
|
I have a trying, it sent back a SIP 100 trying message
|
|
0:04:36
|
and then I´m receiving others for 3002, 3003 at this address
|
|
0:04:49
|
and we´re saying they´re not found, right. So
|
|
0:04:52
|
that´s understandable I said they weren´t going to register properly
|
|
0:04:56
|
the point was is that they are trying to register.
|
|
0:05:00
|
So 3001, 3002 and 3003.
|
|
0:05:08
|
Now we were also instructed, so that was very simple,
|
|
0:05:12
|
we were also instructed to register all E164 numbers.
|
|
0:05:16
|
This over on Branch2 is done under the voice register
|
|
0:05:23
|
global setting with something called bulk.
|
|
0:05:30
|
So bulk allows a bulk pattern registration.
|
|
0:05:35
|
So we can say bulk 31 20 703 3...
|
|
0:05:43
|
and watch happens now, I´m going to clear this off.
|
|
0:05:50
|
Now, we´re about to get 31 20 703 3... so all of those addresses
|
|
0:06:00
|
that entire range is going to attempt to register
|
|
0:06:03
|
with the SIP proxy server, again it´s not going to be found
|
|
0:06:06
|
that´s understandable, not a real SIP proxy server.
|
|
0:06:09
|
Well I mean it is a a real SIP proxy server, but it´s not really
|
|
0:06:12
|
fully set up to be taking all these registrations yet.
|
|
0:06:16
|
The point of the task was just that we wanted to
|
|
0:06:19
|
show the configuration that was necessary
|
|
0:06:22
|
and show that it´s actually working properly as we intended it to.
|
|
0:06:26
|
|
