WEBVTT

00:00.090 --> 00:03.160
NACRO services for web deployment.

00:03.430 --> 00:10.620
Now we do require when we deployed the IP PBX or the white phone system and a network for the production

00:10.740 --> 00:15.830
we do require our network services that help us to ease the deployment.

00:15.840 --> 00:21.630
Now in this video I'll try to show you the network service and are really required to make a smooth

00:21.660 --> 00:25.560
deployment of our white PBX and our production environment.

00:25.560 --> 00:33.260
Let's see a common network services that we require for IP telephony deployments are idiotcy server

00:33.840 --> 00:40.830
or a Dynamic Host control protocol where we deploy the phones and all those of the phones get the IP

00:40.830 --> 00:46.050
addresses from the server in order to communicate with the IP PBX.

00:46.050 --> 00:50.440
Then of course we do need the A.P. network time protocol.

00:50.460 --> 00:54.870
All the phones that we are deploying should have a correct timing on it.

00:54.870 --> 01:02.250
The FTB of the FTB is the Obst none are in case of we are doing the auto provisioning or the phones

01:02.250 --> 01:08.010
that say you have 100 hundred plus phones are 50 60 phones and you like to give them the zero touch

01:08.010 --> 01:08.770
provisioning.

01:08.820 --> 01:17.190
Then you do need the DFT or the FGP services of the server where you can upload all the example configurations

01:17.400 --> 01:23.280
the content directories logos images for all the phones that you like to deploy.

01:23.370 --> 01:26.880
And I mean sure you can do that in the later videos.

01:27.790 --> 01:35.770
And then of course the DNS DNS and case of are using for on disaster recovery are the higher reliability

01:35.830 --> 01:43.210
than the DNS also helps you to configure a DNS hostname instead of using the IP address.

01:43.210 --> 01:49.870
Now the DSP sort of is that we use is a dynamic host control protocol of course and you need to define

01:49.870 --> 01:54.100
the DSC pre-arrange for the pool of endpoint phones.

01:54.130 --> 02:02.800
So you should define Lets say you have our 254 hostname then you defined a range for our iPhones and

02:02.800 --> 02:08.970
you should have a static range as well so your IP PBX or the phone Sarber the gateways.

02:08.980 --> 02:15.810
And as we see the session Mahrer controller IP addresses should be and static range should not be the

02:15.810 --> 02:18.020
part of a DCP otherwise.

02:18.160 --> 02:25.300
You know the C-p each time when you board the device it tried to local try to did the DNC because it

02:25.300 --> 02:34.300
DeWyze is having the least time to adjust hands on will use the DCP for the phones that we are deploying

02:34.420 --> 02:42.040
and we'll keep the static IP addresses for IP PBX and gateways and as busy as Sacra or any web device

02:42.520 --> 02:49.750
the that we use in our network other than the phones the DHC option can be used to Arko assigned the

02:49.750 --> 02:51.880
following setting to the IP phones.

02:51.880 --> 02:58.210
Now one of the advantage of using the DSP and your phone network is that you can automate some of the

02:58.210 --> 02:59.040
features.

02:59.050 --> 03:06.850
For example the anti-peace server address that you can assign using the C.P options to your phones that

03:06.900 --> 03:09.920
Ifti be in the server address as well.

03:09.940 --> 03:18.550
So as soon as the phone booths and the IP address and the next using the DTP option like 121 fifty or

03:18.550 --> 03:25.800
sixty six it will get the DFT P or the FGP address where it can download it from where its config files

03:25.810 --> 03:26.630
etc..

03:26.680 --> 03:28.570
And similarly the DNS.

03:28.570 --> 03:33.920
So it will also get its domain name where it can resolve any IP address against any domain.
