WEBVTT

00:00.070 --> 00:06.150
Key element for stable Wapnick book and this video I tried to show some of the network elements that

00:06.150 --> 00:13.080
really affect the quality and if you plan to deploy the white PBX or the IP PBX and your network you

00:13.080 --> 00:15.630
really need to take care of these elements.

00:15.660 --> 00:22.140
Wipe is a service doctrine on a network for example and this image the road is an example of the network

00:22.260 --> 00:30.040
and car that drive on top of this road is like an example of web service on this road.

00:30.130 --> 00:33.230
We face some obstacles or bumps.

00:33.480 --> 00:36.990
Definitely we will not be having a smooth drive.

00:37.050 --> 00:39.020
It will be uncomfortable for us.

00:39.030 --> 00:44.570
Similarly as the example of the web network the network is not optimize our way.

00:44.640 --> 00:53.090
Then you come across different issues like quality car drops and some ways that better meters.

00:53.190 --> 00:55.410
Here's one more example I tried to show you.

00:55.410 --> 00:57.590
Imagine your network is congested.

00:57.600 --> 01:02.670
Let's say you do not have a villain and all your voice and data is on same live network.

01:02.670 --> 01:06.880
This means you are putting all the traffic on a single network on a single line.

01:06.900 --> 01:13.290
So that can cause delays and the way there will be a jitter and the wife can I call in the audio's and

01:13.480 --> 01:15.590
will have a very bad experience.

01:15.630 --> 01:18.390
So what is actually a real time service.

01:18.570 --> 01:25.110
Imagine if I'm browsing a webpage and let's him to repeat takes 10 seconds then I don't can see that

01:25.110 --> 01:26.260
I don't have an issue.

01:26.280 --> 01:32.280
But imagine if I'm talking to somebody on the phone and there's a delays of five seconds and then I'll

01:32.280 --> 01:33.820
keep saying hello hello.

01:33.820 --> 01:36.260
So something like this I'll expedience.

01:36.360 --> 01:42.870
So then this video will try to explore some of the elements that will help us to achieve the VOIP quality

01:42.890 --> 01:44.650
or the white paramita.

01:44.820 --> 01:51.630
So first of all really great to see the Nano related elements the local area elements.

01:51.630 --> 01:58.110
The first thing and the land that we use are the switches so use the modern switches of white using

01:58.110 --> 02:04.500
hubs the ordinate button devices because the hubs are no longer in use but in some situation I have

02:04.500 --> 02:10.890
seen some students who are trying to use the hubs and then they come up with the Weiskopf energy issue.

02:10.890 --> 02:12.440
This is the way it is not clear.

02:12.460 --> 02:18.900
So the first thing tried to use the modren switches is the new switches even if they're using at home

02:18.930 --> 02:25.950
or small office or in the productions a while using hubs the Ord networking new ises network switch

02:25.950 --> 02:34.380
between IP PBX and are employing the IP phone should be at first Duplaix rather than half duplex more

02:34.410 --> 02:43.010
so you should configure all the ports at 4 Duplaix the next use segregated network.

02:43.200 --> 02:48.570
That means separate your wife's and data using the land approach.

02:48.810 --> 02:57.220
So if you use the land the what your land and your network then the wice will have its own network subnet

02:57.270 --> 03:00.020
and that data will have its own network and subnet.

03:00.060 --> 03:04.960
And this case will be able to have a better or worse quality on your network and you will not get the

03:04.960 --> 03:06.940
delays or conditions.

03:06.960 --> 03:11.940
This is one of the vilest standard 800 2.1 Kule relend standard.

03:11.940 --> 03:15.980
Those who are very much familiar and the networking site are the networking professional.

03:15.990 --> 03:22.140
They understand that going into this thing trying to if you dont have any idea on land can search some

03:22.410 --> 03:28.830
nickered expert or the network administrator or 100 applying the telephony to these requirements to

03:28.830 --> 03:35.790
your network administrator that you need to be lan it or 2.1 Kule relend standard and use the quality

03:35.790 --> 03:36.430
of service.

03:36.440 --> 03:43.890
The cause was on the networks which is where he will be able to prioritize the Weist traffic as compared

03:43.890 --> 03:53.120
to the data graphic settings priority setting you can use it or not what the automatic setting for default

03:53.120 --> 03:56.730
product the Fyffe is there for the Weisse.

03:56.730 --> 04:02.160
So you can share these details with your networks if you understand the networks when you deploy the

04:02.160 --> 04:05.120
line for the network for the wipe you can.

04:05.130 --> 04:11.210
You should consider these land bad ammeters quite related to the the land settings and standards.

04:11.220 --> 04:19.730
If you do not afford the villain in some cases it quite the manageable switch and disk management switches

04:19.740 --> 04:26.780
are relatively expensive as computer non-management switch then you should deploy all the hundred MBBS

04:27.090 --> 04:29.800
one 1 gig NBPA switches in your network.

04:30.270 --> 04:35.100
That will give you more local bandwidth to your wife's traffic.

04:35.130 --> 04:40.890
So in a situation I'll repeat again if you're not able to for chairs or there some scenario where you

04:40.890 --> 04:43.410
are facing issue with the cost.

04:43.410 --> 04:50.680
You can use the non-measurable suite but with the higher total What acceptance criteria.

04:50.760 --> 04:55.290
These are the next about ammeters for example the packet loss.

04:55.520 --> 05:02.610
If you have a pack that cost less than 1 percent the dream but you know you have a greater waste quality

05:03.420 --> 05:06.760
and something that will take the umber of the yellow one.

05:06.760 --> 05:14.000
The caution it should be less than 5 percent and then if it is something more than that last more than

05:14.000 --> 05:19.030
five percent then that is not recommendable for the boy.

05:19.190 --> 05:25.200
And similarly the gender and gender is the variation between when the delays.

05:25.220 --> 05:32.330
That is something you should have less than 30 milliseconds then that is acceptable if it's less than

05:32.330 --> 05:33.140
60.

05:33.140 --> 05:35.590
Somehow you take caution and try to fix it.

05:35.600 --> 05:41.870
And that is greater than 60 then definitely you will experience the bad Weisse quantity or breaks and

05:41.870 --> 05:44.210
the audio you will have.

05:44.310 --> 05:51.690
And similarly is the delay the one way DeLay should be less than 50 millisecond 80 and then 150 millisecond

05:51.690 --> 05:57.920
if it is something more than 150 you should stop using it and you should write to us your nickered arms

05:57.970 --> 05:58.860
Titor.

05:58.980 --> 06:06.100
The network consultants who are responsible for the network ask them to fix these things are you.

06:06.210 --> 06:09.390
And similarly being responsive the both ways.

06:09.400 --> 06:10.450
Values are there.

06:10.480 --> 06:17.570
It should be less than 100 milliseconds are the acceptable it's should be less than 160 milliseconds

06:17.590 --> 06:22.350
if it's something more than 300 millisecond then you should not use it.

06:22.350 --> 06:26.630
This should be between IP PBX server and the phone network.

06:26.880 --> 06:30.690
So wherever you are IP is IP PBX is based on.

06:30.750 --> 06:37.560
Imagine if you're using in the cloud audio using a different subject subject and different networks

06:38.200 --> 06:44.010
than the these paramita the packet flaws the jitters and the delays.

06:44.010 --> 06:49.720
You should take into the considerations the phone network we are deploying the IP phones.

06:49.920 --> 06:57.510
So these parameters are then checked based on the between the IP PBX and the phone network wide area

06:57.510 --> 06:58.420
network element.

06:58.410 --> 07:06.420
So one of the key element for the wide area network you should have a similar optimized network along

07:06.420 --> 07:13.710
with the optimized network if you are using the remore branch any more extensions then you should use

07:13.710 --> 07:17.250
the file for the branch office or the remote user.

07:17.280 --> 07:24.260
Use the best Benwood optimize audio cortex like oboes de 8:53 are recommended.

07:24.270 --> 07:33.240
Now these kind of codecs they use less bandwidth in a situation where you have a multiple offices branch

07:33.240 --> 07:39.510
offices and you're planning to connect the branch office with the headquarters to the head office and

07:39.510 --> 07:44.450
then you are trying to register the extension from branch to the head office.

07:44.490 --> 07:50.790
Then you're using a van band right now the van Banbridge totally depend on you know the provider who

07:50.790 --> 07:58.450
gives you the connectivity it might be E-1 or you know the T-1 are some VPN you know the connectivity.

07:58.470 --> 08:04.920
So you need to use if you're facing the delays and the issues then you should try to use because when

08:04.920 --> 08:10.200
we are on the land then we don't have any issue of the bandwidth because it's just by default is under

08:10.230 --> 08:11.040
MBBS.

08:11.070 --> 08:19.620
But when we move out from the land we have a van and then when we can see that the bandwidth issue cortex

08:19.650 --> 08:26.850
is something that can help you to utilize our guns you less bandwidth with better audio quality.

08:26.850 --> 08:31.340
Here's a chart bitrate for the as per channel.

08:31.770 --> 08:42.630
You can see the Opal's and 8:53 is on top and the other cortex speaks you 7:02 to decide when to 9.1

08:42.750 --> 08:44.340
and others etc..

08:44.370 --> 08:51.990
So in case of man I tried to use the G-7 2:9 of Opus Kordek for your IP PBX.
