/mcpFields Event Action State = ROUTE getCurrentRouteAddress () = RP getCallingAddress () = A getCallingTerminal () = SEPA (Terminal associated with A) RouteEvent Call arrives at RP State = ROUTE_USED getCallingAddress () = A getCallingTerminal () = SEPA (Terminal associated with A) getRouteUsed () = B RouteUsedEvent Application invokes selectRoute(routeselected[], callingsearchspace, modifiyingcallingnumber[], preferredOriginalCdNumber[], preferredOriginalCdOption[], facCode[], cmcCode[]) where routeSelected[] = BcallingSearchSpace = CiscoRouteSession.DEFAULT_SEARCH_SPACEmodifyingCgNumber = null, preferredOriginalCdNumber = null, preferredOriginalCdOption = CiscoRouteSession.DONOT_RESET_ORIGINALCALLED, facCode[] = “facCode for B”cmcCode[] = “cmcCode for B” State = ROUTE_ENDgetRouteAddress () = RP RouteEndEvent Application invokes endRoute (ERROR_NONE) Hairpin Support Result Expected Behavior Use Case Pre-Condition S.No. A and C are connected. At A: It is connected to B. A’s type is CiscoAddress.Internal B’s type is CiscoAddress.External At C: It is connected to B. C’s type is CiscoAddress.Internal B’s type is CiscoAddress.External A calls B via gateway. B transfers call to C via gateway. B completes the transfer and goes out of scenario. Now IP Phones A and C are connected IP Phones A and C are in same cluster, IP phone B is in another cluster. JTAPI observes A and C. Gateway does not pass new party information to each other. There will be no transfer start and end events as transfer controller is not a controlled device. 1 A and C are connected. At A: It is connected to C. A’s type is CiscoAddress.Internal C’s type is CiscoAddress.External At C: It is connected to A. C’s type is CiscoAddress.Internal A’s type is CiscoAddress.External A calls B via gateway. B transfers call to C via gateway. B completes the transfer and goes out of scenario. Now IP Phones A and C are connected. IP Phones A and C are in same cluster, IP phone B is in another cluster. JTAPI observes A and C. Gateway is able to pass new party information to each other. 2 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 998 Message Sequence Charts Hairpin Support