This document explains the various Unified Communications call flow scenario in an Enterprise Network. Idea of creating this document is to help the beginners to understand the various Call flows and protocol messages.
Basic knowledge about Cisco Unified Communications Manager (CUCM) and the protocols SIP, H.323 and ISDN.
Call Flow Examples
1. IP Phone to IP Phone - Successful Intracluster Call
In this scenario, Phone A is registered to Cisco Unified Communication Manager X denoted by CUCM X. Phone B is registered to the same CUCMX.
A call is placed from Phone A (1000) to Phone B (1006). Basic setup for a call between two IP phones registered to the same CUCM.
Below call flow illustrates the sequence of Skinny Call Control Protocol (SCCP) messages exchanged between the Unified CM (CUCM X) and the two IP phones described in the setup.
2. Call flow: IP Phone to Voice Gateway using MGCP
In this scenario, Phone A is registered to the Unified CM (CUCM). Phone B is connected to a carrier’s central office (CO) Switch. CUCM will access Phone B through the voice gateway. Below diagram illustrates this basic setup for a call set up between an IP phone registered to the CUCM and another phone connected to a CO switch in the public switched telephone network (PSTN) through a voice gateway. This voice gateway is registered with the CUCM using Media Gateway Control Protocol (MGCP).
A call is placed from Phone A (1000) to Phone B (555-1212). Phone A will hang up first. MGCP is used to relay ISDN messages that go between the CUCM and the actual CO switch.
Below figure, include call flows that show ISDN messages going to the gateway (GW); they are really being sent to the CO switch through the gateway. Detailed call flow is shown here,
3. Call flow: IP Phone to H.323 Voice Gateway with Gatekeeper
In this scenario, Phone A is registered to the CUCM. Phone B is connected to a carrier’s CO switch. Below diagram illustrates this call setup between two IP phones registered to the same CUCM. A call is placed from Phone A (555-2001) to Phone B (555-2001). Phone B hangs up first. The CUCM must register with the gatekeeper prior to placing any calls, and the gatekeeper will police the bandwidth by implementing Call Admission Control (CAC).
Because the initial call setup phases between the IP phone and the CUCM have been covered earlier, they are not repeated in this call flow. Below figure includes all the steps involving CUCM registration with the gatekeeper, skips the initial IP Phone A interaction with the CUCM when it goes off-hook to call Phone B in the PSTN, and then illustrates the CUCM and H.323 gateway interaction, including the ISDN Q.931 messaging exchange with the CO in the PSTN to set up the call with Phone B. The communication beyond the CO, which would include SS7 messages, with the CO serving Phone B is not part of this overall example.
Simple script : Prompt caller to enter a PIN using the Get Digit Step.In the Success branch I created an IF step > If (Pin_Entered == "1234") ; then the TRUE branch is a '= SET' step to identify the Extension ...
I am having an issue where any consult transfer to a UCCE PQ never updates the Call.CallingLineID variable in Finesse....even after the transfer completes. The variable remains stuck on the extension doing the initial transfer and never displays the...
Good morning and a very happy Friday Cisco community. Have a weird one here, doing an upgrade for the client UC system(CUCM, CUC, CER and IM&P) from 10.5.1 TO 12.5. But I had to upgrade the CUCM to 10.5.1 to 10.5.2 first so It can be upgra...