QoS Application Classes: Signalling

This blog continues our coverage of the 11 Cisco QoS application classes. The classes are as follows: Routing Voice Interactive Video Streaming Video Mission-Critical Data Call Signalling Transactional Data Network Management Bulk Data Best Effort Scavenger The next application class in our coverage is the call signaling class. The call signaling class will include the protocols used in IP telephony to setup and teardown telephone and video conversations. These protocols include, but are not limited to H.323, MGCP, SIP, and SCCP. The port numbers for these protocols can be find by issuing the “show ip nbar port-map” command on a Cisco router. This application class should also include CTI-QBE (Computer Telephony Integration – Quick Buffer Encoding) if any TAPI (Telephony Application Programming Interface) or JTAPI (Java TAPI) integrations exist. CTIQBE uses TCP 2748 and is not included in Auto QoS Voip or Auto QoS Enterprise. CUCM deployments using the clustering over the WAN model, must identify additional protocols in the call signaling class. Most CUCM ICCS (inter-cluster communications signaling) is marked as CS3 by default, but I prefer to not rely on defaults. The ports used in CUCM can be very large, but I have included a link in the references section of this blog. The main protocol used for ICCS between CUCM servers is SDL (signal distribution layer) which uses TCP port 8002 and 8003. We will continue this conversation in the next blog with the transactional data class. REFERENCES CUCM 7.0 TCP and UDP Port Usage: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/port/7_0/CCM_7.0PortList.pdf