re the conference server assigns nte (rfc2388) to use payload 96. This is needed for the media servers at Company Q. Example 12-6 shows the RTP pay-load configuration. dial-peer voice 3 voip dial-peer voice 88532929 voip Company P Company Q Conference Server dial-peer voice 4 voip dial-peer voice 2 voip Figure 12-5 Dial-Peer Configuration Example Example 12-6 RTP Payload Configuration dial-peer voice 2 voip description **Incoming SIP Dial - Peer ** rtp payload-type cisco-codec-fax-ack - - 114 rtp payload- type cisco - codec-fax-inc - 112 rtp payload type nte 96 session protocol sipv2 session transport udp incoming called-number - dtmf-relay rtp-nte codec g711ul ip qos dscp cs5 media no vad Example 12-7 shows another configuration of an H.323 dial-peer that connects to Company P's CUCM and handles all the international calls initiated by the prefix 9011. Example 12-7 Dial-Peer Toward Company P's CUCM dial-peer voice 4 voip description ial-back CUBE to ccm-sjc destination-patterr 9011. session target ipv4:xx.xx.xx.xx dtmf-relay h245-alphanumeric codec g711ulaw ip qos dscp cs5 media no vad 274 SIP Trunking Call Admission Control When we took the snapshot of the solution, Company P was running 4700 active calls during peak hours and close to 34,000 users, all G.711 traffic. It forecasted that call vol- ume for the combined sites would never exceed 6000 calls, but during the economic downturn, the company instituted travel restrictions. Therefore, employees would not need to fly to have face-to-face meetings, and they were asked to use web-based confer- encing to save money. It increased the maximum hit at 6641 calls. To manage the call admission control (CAC) in many CUBE boxes, Company P tried fol- lowing CAC options in CUBE, including: Total calls Memory IP call capacity Max-connections Resource ReSerVation Protocol (RSVP) Company P used the total calls control mechanism for CAC. Example 12-8 shows the configuration from the router. Example 12-8 Call Admission Control call threshold global total-calls low 280 high 