/mcpCall info Events Actions .getLastRedirectedAddress() = 4XXX, .getCurrentCallingTerminal() = Terminal of A. .getCurrentCalledTerminal() = null .getModifiedCallingAddress() = A, .getCurrentCallingAddress() = A, .getCallingAddress() = A, .getModifiedCalledAddress() = B, .getCalledAddress() = 4XXX, .getLastRedirectedAddress() = 4XXX, .getCurrentCallingTerminal() = terminal of A. .getCurrentCalledTerminal() = terminal of B GC1-TermConnRingingEvent GC1-CallCtlTermConnRingingEv GC1-TermConnDroppedEv GC1-CallCtlTermConnDroppedEv GC1-ConnDisconnectedEvent-4XXX GC1-CallCtlConnDisconnectedEv-4XXX GC1-ConnConnectedEvent-B GC1-CallCtlConnEstablishedEv-B GC1-TermConnActiveEvent GC1-CallCtlTermConnTalkingEv 4XXX gets dropped B Answers WildCard Routepoint Interaction (Original Behavior) WildCard RoutePoint Redirects a Basic Incoming Call to IPPhone Notes / Caveats This configuration is not supported. This use case is only intended to show the call flow or events for the above use case with the Use WildCard pattern in CTI Call Info service parameter turned off. Applications should not count on this information to be correct, and to properly support Wildcard Routepoint scenarios, should look to adapting their applications so that they can support the new service parameter being enabled. An important thing to note is that a connection is created for the dialed DN, 4000. This connection, as well as the connection of 4XXX is not dropped from the call until the redirect happens. This means that if a Wildcard DN is configured on a phone or device, you will see connections for the calling party, 4000, and 4XXX. This basic call will have three connections, which may confuse applications, which might believe it to be a conference call. CiscoCall.isConference() would still return false in this scenario. As stated in previous sections, this extra connection is created in error, and applications should not rely on this connection being there. Configuration Phone A, B are in cluster devices. 4XXX is a wildcard routepoint Service parameter “Use WildCard pattern in CTI Call Info” is set to false / OFF. Procedure: Application invokes connect() at A to call 4000. 4XXX redirects the call to B. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 954 Message Sequence Charts WildCard Routepoint Interaction (Original Behavior)