Learning IOS and JUNOS

Juniper CLI learning is a little challenge for junior network engineers or Cisco IOS engineers, because the JUNOS modular and hierarchical structure design. Some features may need several command line which were configured under different hierarchical levels, then combined all of them together in another hierarchical level. Such kind of CLI design especially not easy to learn when apply CoS on juniper device.(I believe many Cisco IOS engineers don't want to switch to JUNOS because of this...) As above figure is my understanding about the related JUNOS command which is using in our production network.

Call-Signaling Traffic The following are key QoS requirements and recommendations for Call-Signaling traffic: • Call-Signaling  traffic should be marked as  DSCP CS3  per the QoS Baseline (during migration, it may also be marked the legacy value of DSCP AF31). • 150 bps  (plus Layer 2 overhead) per phone of  guaranteed bandwidth  is required for voice control traffic; more may be required, depending on the call signaling protocol(s) in use. Call-Signaling traffic was originally marked by Cisco IP Telephony equipment to DSCP AF31. However, the Assured Forwarding classes, as defined in RFC 2597, were intended for flows that could be subject to markdown and - subsequently - the aggressive dropping of marked-down values. Marking down and aggressively dropping Call-Signaling could result in noticeable delay-to-dial-tone (DDT) and lengthy call setup times, both of which generally translate to poor user experiences. The QoS Baseline changed the ma...