Shaping can be applied only in the outbound direction and doesn’t discard the traffic exceeding the rate limit automatically. Shaping will bufferize the queue until the bandwidth become available or in last action will drop exceeding packets.
Compared to Policing , shaping preserves the bandwidth and is recommended on lower bandwidth links.
Qos Shaping is also considered as an Traffic Conditioner
Policing can be used in either the inbound or outbound direction and it discards packets which are exceeding a configured rate limit.
Pay attention to the fact that policing is dropping packets , it can result in retransmissions (TCP acknowledge), so it is better to use policing on higher bandwidth links !!!
Qos Policing is also considered as an Traffic Conditioner
Endpoints which are using multicast discovery will use the multicast adress 224.0.1.41 for GRQ
In H.323 , you can play with the caller id (not the case with MGCP , see previous post).
By default,Caller ID is disabled on all FXS ports.
So in order to enable it , you must go under the voice-port and activate it as it is shown in the below config
!
voice-port 2/0
caller-id enable
!
Caller ID is not supported on MGCP Controlled FXS ports.
So remind this if you need it 🙂
Regarding security endpoints, you have 2 opportunities :
- Newer phones are using more an existing Mafufacturing Installed Certificate , this is the MIC
- Meanwhile , old phones will use a Locally Significant Certificate ( LSC) which will be installed by the Certificate Authority Proxy Function (CAPF)
As LSC must be a transaction between the Ip phone and the CAPF , here is the process as it is issued :
- IP Phone generates a public/private key pair
- A TLS Session is established with the CAPF Service and the keys and identity are sent from the phone to CAPF
- The CAPF Service creates and sends an LSC to the phone
- The IP Phone installs the LSC
Also for info, the CAPF Service must be in the phone CTL file , which is downloaded from the TFTP when the phone boots .
Recent Comments