CME to CME Call forward loop

-
Sample call flow of such scenario-
IP Phone CME A >> IP Phone CME B >> Call forward to another extension of CME B.
In call forward loop scenario, Call will reroute by CME A instead of CME B.
This scenario gets complicated when we call forward the calls to a PSTN number, in such scenarios, call routes via CME A, still doesn't looked complicated, let me give you an example-

India IP phone calling directly to US IP phone which is CFA to local mobile number which could be 9.1234567890
When India IP phone hits the US CME, it will send the call forward information to India CME which is 9.1234567890, India CME won;t able to complete this call because it is not its local number rather international.

To avoid this call forward looping, you'd need to disable H450.3 service in the forwarding CME.
It is activated by default on a CME with 3.1 or later versions, this service loops the call. The idea of this service is to minimize the resources being used at remote CME, choice of codecs for the new call leg as well as minimizing the WAN bandwidth. Here is what I got on my asn1 debugs on India CME-

value H4501SupplementaryService ::=
    {
      networkFacilityExtension
      {
        sourceEntity endpoint : NULL
        destinationEntity endpoint : NULL
      }
      interpretationApdu discardAnyUnrecognizedInvokePdu : NULL
      serviceApdu rosApdus :
      {
        invoke :
        {
          invokeId 5480
          opcode local : 19
          argument {"4824010180CB38000000010180CB530001018044..."}
        }
      }
    }

155673: May  9 15:45:11 SING: H450 INCOMING PDU ::=
  {
      reroutingReason 1
      originalReroutingReason 1
      calledAddress
      {
        destinationAddress
        {
          dialedDigits : "9805"
        }
      }
      diversionCounter 1
      h225InfoElement {}
      lastReroutingNr
      {
        destinationAddress
        {
          dialedDigits : "9820"
        }
      }
      subscriptionOption 0
      callingNumber
      {
        destinationAddress
        {
          dialedDigits : "1134"
        }
      }
      originalCalledNr
      {
        destinationAddress
        {
          dialedDigits : "9820"
        }
      }
    }

1134 dialed 9820 which was CFA to 9805 another local extension.

In order to disable h450.3 service, do the following. You'd need to disable it on CME B, in this case US CME-
Config t
Voice service voip
no supplementary-service h450.3


Good link for further information.

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more