During WAN failure , we can observe that H323 will not preserve absolutely the call when the failover occurs as there is no more any signal from the CUCM.
An unofficial workaround is to use the command h225 timeout to suppress the keepalive between the Call Manager and the gateway.
!
no h225 timeout keepalive
!
MGCP is Master/Slave protocol and MGCP endpoints are controlled by the Control Agent ( Most of the case , it will be the CUCM)
MGCP uses the UDP/2427 for its communication between the CUCM and the GW. It is also a text-based master/slave protocol used by a media gateway controller (MGC) and Call Agent to control media gateways. However , TCP/2428 is used to exchange keepalives between endpoints and Call Agent, as well for MGCP PRI/BRI backhaul.
MGCP MGCs and MGs can be described as follows:
- MGC/Call Agent: this element possesses call control intelligence and controls MGs (example : Call Manager)
- MG: This device provides translation between data packet and audio signals reveived over VoIP networks and other networks such as the PSTN ( example: IOS gateway)
As defined for SIP , here are the transport layers used by Skinny/SCCP Protocol:
- TCP Connection with CUCM
- UDP Connection between the endpoints
SCCP is a Cisco proprietary protocol master/slave protocol that Call Manager and other call agents can use to communicate with devices and endpoints as Cisco IP Phones.
SCCP uses port TCP/2000 and TCP/2443 for SCCPS
Video Call Bandwidth is dealing the bandwidth of video and voice for a call in one field .
So in the CAC for a video call , you can remove the video bandwith + the audio bandwidth from the the field Video Call Bandwidth .
Location is the total amount of bandwidth that you have
CUCM 8 0 0 99141-4 – (Bootable) CallManager 8 Beta @ http://www.bitspyder.net/details.php?id=42532
I have worked during all the week-end to install images in VmWare Virtual machines .
And here is the result :
(more…)