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 🙂
In order to your DHCP to give the TFTP address to your phones , the common configuration is to use the option 150 which is the main and the more expanded concept used for providing your TFTP. It can provide an IP Address as well an array of IP Address.
This is also the code which you are using under IOS configurations.
But in some old implementation , you can find also the option 66 to give the TFTP to the phones . Option 66 is different in the meaning that you must provide a server name so you need to have DNS enabled . Also you can only pass one parameter!!!
So don’t be too disturbed if you see this option 🙂