McDewey

Use Cases for NuRD (Number Matching for Remote Destination) Prerequisites Pre-conditions to nurd use cases, unless specified otherwise: • Provider is in IN_SERVICE state • All addresses and terminals are already in service. • Enable "Route calls to all remote destinations" checkbox for CTIRD1 and CTIRD2. • Clusterwide service parameter "Reroute Remote Destination Calls to Enterprise Number" is set to true. • ICT Trunk configured with Route pattern is 408XXXXX with no discard digits. • SIP Trunk configured with Route pattern is 409XXXXX with no discard digits. • ICT Trunk configured with Route pattern is 33.XXXX with discard digits pre-dot. • CTIRD1 associated to user "Mobility1", dn = 2303 • Remote destination 1 (Name: "RDD1", Number: "40822077") • Remote destination 2 (Name: "RDD2", Number: "40922078") • CTIRD2 associated to user "Mobility2", dn = 9200 • Remote destination 1 (Name: "RDD3", Number: "40812115") • Remote destination 2 (Name: "RDD4", Number: "40912116") • CTIRD2 has a shared ip phone D • RDP2 associated to user "Mobility2", dn = 9200 with display and Unicode name configured to be "RDP2". • Remote destination 1 (Name: "RDD3", Number: "40812115"). This is shared with CTIRD2. • Remote destination 2 (Name: "RDDP1", Number: "40922095") • Device A (IP Phone - Name: "SEP2401C7824EA3", Line A1 (dn: 9000)). • Device B (IP Phone - Name: "SEP2401C7824EAE", Line B1 (dn: 9001)). • User1 has in its control list: Device A, B, CTIRD1 and CTIRD2. All devices and lines are observed. Basic Calls Initiated From Remote Destination Table 286: Remote Destination Initiates Call with No Active RDD Call Info Events Action ProvInServiceEv User1 opens Provider and adds a provider observer. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1307 Message Sequence Charts Use Cases for NuRD (Number Matching for Remote Destination)