McDewey

Redirect TAPI application monitors party B and party C Party A represents an IP phone A calls B IP Address of A is available to TAPI application that is monitoring party B Party A redirects B to party C Calling IP address is not available to TAPI application that is monitoring party B (not a supported scenario) Calling IP address B is available to TAPI application that is monitoring party C Calling Party Normalization Incoming Call From PSTN to End Point TAPI structures TAPI messages CTI messages Action LINECALLINFO Displayed Calling Party = 5551212, Displayed Called Party = 2000, Displayed Redirection Party = , Displayed Redirected Party = , Globalized Calling Party = +14085551212, Calling Party Number Type = SUBSCRIBER, Called Party Number Type = UNKNOWN, Redirection Party Number Type = , Redirecting Party Number Type = LINE_CALLSTATE = CONNECTED CallStateChangedEvent, UnModified Calling Party = 5551212, UnModified Called Party = 2000, UnModified Original Called Party = 2000, Modified Calling Party = 5551212, Modified Called Party = 2000, Modified Original Called Party = 2000, Globalized Calling party = +14085551212, Calling Party Number Type = SUBSCRIBER, Called Party Number Type = UNKNOWN, Original Called Party Number Type, = UNKNOWN State = Connected, Origin = OutBound, Reason = Direct A Call gets offered from a PSTN number 5551212/<SUBSCRIBER> through a San Jose gateway to a CCM end point 2000 Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 500 Message Sequence Charts Redirect