Advanced Dial Plan Design for Unified Communications Networks Johannes Krohn BRKUCC-3000
|
|
- Ella Walters
- 6 years ago
- Views:
Transcription
1
2 Advanced Dial Plan Design for Unified Communications Networks Johannes Krohn BRKUCC-3000
3 Agenda Introduction Numbering vs Dialing Reference Dial Plan Call Routing Reference Dial Plan Number Presentation Special Considerations Deterministic Inter-Cluster Routing (Global Dial Plan Replication) SIP Routing URI Routing on SIP Trunks
4 Introduction
5 Remember Best and most important tools for dial plan design: Pencil Paper Whiteboard Dial plans are not a new concept IP did not really change the fundamentals of dial plan design Dial Plan recommendations are not a monolith Take what you need Keep it simple!
6 What Is a Dial Plan About? Mapping from dialed destinations to connected endpoints Concepts that are part of dial plans user input mapping of user input to routable format (transformations) routing / routing restrictions (class of service) call presentation numbering plans (addressing) routing
7 User Input / Dialing Habits Users dial using common habits: Dialing Habits Different formats for types of destinations colleague next door example: 4XXX (four digit dialing) PSTN: local, national, international example: 9-7D, 91-10D, 9011-E.164, +E.164 Inter-office (abbreviated on-net, forced on-net) 8-7D, or any supported dialing habit for PSTN destinations mapped to on-net address Voic example: 4000 (special intra-site) Emergenc example: 911, 112, 110, 000 other services Especially external dialing habits are country-specific 9 or 0 for outside line Format of national numbering plan (fixed/variable length etc.)
8 Example Dialing Habits in Europe 0 (or 9 ) to get an outside line (trunk access) Any number starting with 1-8 is generally internal But please stay clear of 112 standardised emergency number National numbers need a 0 in front of the area code: 0 Trunk access 0 Escape for area code (Italy: 0 is part of the area code) 69 Area code of Frankfurt Dial From inside the enterprise to Frankfurt international numbers are typically prefixed by 00 : 0 Trunk access 00 Escape for country code 39 Country code of Italy Dial From inside the enterprise to Italy
9 Enterprise Specific Dialing Habits Typically dialing habits for local, national, international calls are given/agreed based on a given domain/country In addition need to agree on how to dial: Private numbers (on-net) Intra-Site Services (voic , meet-me, call park, pick-up...); non-dids + -dialing also needs to be supported! application support number portability
10 Dialing Domain Enterprise call controls need to be able to support different national dialing behaviours (different dialing habits) Groups of users sharing common dialing habits need to be treated identical Definition: Dialing Domain = Group of users/devices sharing common dialing habits to reach identical destinations US UC PSTN DE PSTN
11 Numbering vs. Dialing
12 Dial Plan vs. Numbering Plan Dial Plan: from dialed digits (dialing habits) to destinations Numbering Plan: scheme to identify entities (phones) unique number per entity e.g. (+)E.164 or private numbering allows for single numbering domain overlapping numbering e.g. unique per site requires partitioned numbering domains Recommended: unique addresses Benefits: maintain correct caller ID (think overlaps in forwarded inter-site calls) Simplified VM integration (unique subscriber IDs)...
13 Dial Plan vs. Numbering Plan Dial plan might support various dialing habits local call: 9+7D or 9+10D national call: 91+10D international call: 9011+<E.164> abbreviated on-net: 8+7D +E.164: +E.164 string Enterprise Numbering Plan might follow one of the above dialing habits (e.g. abbreviated on-net or +E.164)... but does not necessarily have to!
14 The Case for +E.164 Addresses (DN) PSTN addresses (E.164) are unique by definition No need to manage the addressing domain Prefix + allows to differentiate E.164 dialing from any other dialing habit Benefits if +E.164 DNs: +E.164 dialing habit for free Unique addresses (by definition) Correct globalized caller ID for calls orginiating from internal endpoints
15 +E.164 DNs and Non-DIDs (1) Non-DIDs for Lobby phones Features (call park, call pick-up, conferences,...) +E.164 DNs for regular phones provide Unique address (by definition) One on-net dialing habit for free (+E.164 dialing) Correct globalized caller ID for all call-flows originating from internal endpoints pseudo +E.164 DNs (e.g ) don t have any of the above
16 +E.164 DNs and Non-DIDs (2) Better: start with the question how do I want my users dial these destinations?... And add the appropriate patterns as addresses directly Local Significance site specific partition with site-unique patterns caution with exposing non-did inter-site Global Significance global partition with unique patterns need to come up with enterprise specific numbering scheme On egress (specifically gateways) make sure to filter non-did caller IDs
17 Enterprise Numbering Plan (abbreviated on-net inter-site dialing) Why Overlay addressing for non-dids including conference rooms and other features Can be re-used for VM subscriber IDs Possibly shorter inter-site on-net dialing (if mapped to addresses of endpoints) Fixed length instead of possibly variable length inter-site on-net dialing Enterprise Significant Numbers (ESN) must not overlap with any other dialing habit Steering digit for ESNs reduces the domain available for other dialing habits Planning and maintenance effort!
18 Guidelines for ESN Plan Typical format: <access code> - any digit or * <site id> - Might be a hierarchical scheme including regional attributes <extension> - Intra-site on-net extension Example: Access code 496 Site id (site 6 in Germany) 1234 Local extension Make sure to reserve space (what if we get more than 9 sites in Germany?) Make it extensible (think Shannon coding ) Changing an established private numbering is VERY hard
19 Example Dialing Habits/Numbering Non-DID Addressing Based on Dialing Habits Site +E.164 Abbr. Intra-Site * Call Park ** CMR conferencing *** SFO XXX 9XXX 4XXX 88XXXXX NYC XXX 1XXX 4XXX 88XXXXX RTP XXX 1XXX 4XXX 88XXXXX * site specific translation patterns in site specific partition mapping to +E.164 ** single call park range in global partition or site specific call park ranges in site specific partitions *** single dialing habit (single route pattern) in global partition
20 Reference Dial Plan Call Routing
21 Requirements Dialing Habits 4-digit intra-site + dialing for dialing from directories US sites digit for local calls digit for national calls 9011 for international calls German sites 0 for local calls 00 for national calls 000 for international calls Number presentation on phones in shortest possible format
22 Requirements Routing Forced on-net Local gateways in every site TEHO for international calls Classes of Service Internal: Allowed to call all on-net destinations National: Only national off-net destinations International: No restrictions
23 Requirements Sites ESC: XXX STU: XXX SJC: XXX DFW: XXX
24 CoS International +E.164 Destinations CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) USPSTNNational \+1XXX \+1XXX XXXX, XXXX Urgent PSTNInternational Problem with calls to national +E.164 destinations? Partial overlap with \+! Solution: Make \+1XXX XXX XXXX urgent LOC RL Other problems? DNs are non-urgent patterns \+! has partial overlap with all DNs Solution: We need urgent patterns for all on-net destinations to avoid overlap with \+! \+! \+!#, Discard Trailing # Local Route Group XYZ RG
25 CoS International +E.164 Destinations Avoiding Partial Overlap CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) DN E164OnNet \ XXX, Urgent \ XXX, Urgent \ XXX, Urgent \ XXX, Urgent USPSTNNational \+1XXX XXX XXXX, Urgent PSTNInternational \+! \+!#, Discard Trailing # LOC RL Local Route Group XYZ RG
26 CoS International +E.164 Destinations Avoiding Partial Overlap CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) DN E164OnNet \ XXX, Urgent \ XXX, Urgent \ XXX, Urgent \ XXX, Urgent USPSTNNational \+1XXX XXX XXXX, Urgent PSTNInternational \+! \+!#, Discard Trailing # Still need to support other dialing habits 4-digit intra-site US PSTN dialing LOC RL Local Route Group XYZ RG
27 CoS International Adding 4-Digit Intra-Site CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) DN E164OnNet SJCIntra 1XXX, Prefix SJCIntra Is Site-Specific XYZ RG PSTNInternational USPSTNNational LOC RL Local Route Group
28 CoS International Adding International Dialing CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) DN USE164International E164OnNet SJCIntra 1XXX, Prefix UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + Partition for Dialing Normalisation Is CoS Specific, Because Translation Patterns Can Only Have a Single Specific Resulting CSS Which Implements a Single CoS XYZ RG PSTNInternational USPSTNNational LOC RL Local Route Group
29 CoS International Adding 9+7 (Local) Dialing; Full Picture (pre 10.0) CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) DN SJCE164Local USE164International E164OnNet SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + Partition for 9+7 Dialing Is Location Specific, Because the Translation Pattern Needs Site Specific Called Party Transformation XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
30 CoS International Adding 9+7 (Local) Dialing; Full Picture (pre 10.0) CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) DN SJCE164Local USE164International E164OnNet SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + Partition for 9+7 Dialing Is Location Specific, Because the Translation Pattern Needs Site Specific Called Party Transformation XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
31 CoS International 10.0 Simplification (urgent DNs) CSSs Partitions Route Lists Route Groups SJCInternational DN IP Phone DNs (+E.164, urgent) DN SJCE164Local E164OnNet SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix Full match on urgent DN terminates digit collection. No T302 caused by overlap with \+! route pattern USE164International UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
32 CoS International 10.0 Simplification (urgent DNs) CSSs Partitions Route Lists Route Groups SJCInternational DN IP Phone DNs (+E.164, urgent) DN SJCE164Local SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix Full match on urgent DN terminates digit collection. No T302 caused by overlap with \+! route pattern USE164International UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
33 TP CSS Inheritance split personality Translation Patterns CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) UStoE !, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + XYZ RG SJCNational PSTNInternational USPSTNNational LOC RL Normalisation translation patterns use the activating CSS for secondary lookup Local Route Group A secondary lookup CSS following the activating CSS allows for re-use of normalisation
34 TP CSS Inheritance New in release 10.0 CSSs Partitions Route Lists Route Groups SJCInternational DN All IP Phone DNs (+E.164) UStoE !, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + Translation Pattern using CSS inheritance: secondary lookup uses activating CSS Translation Patterns can be re-used XYZ RG SJCNational PSTNInternational USPSTNNational LOC RL CSS Inheritance forces digit analysis to go back to the activating CSS after performing the calling/called party transformations defined on the translation pattern Ideal use case: dialing normalisation Local Route Group
35 CoS International 10.0 Simplification (TP Inheritance) CSSs Partitions Route Lists Route Groups SJCInternational DN IP Phone DNs (+E.164, urgent) DN SJCE164Local SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix Don t need CoS specific secondary lookup CSS any more USE164International UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
36 CoS International 10.0 Simplification (TP Inheritance) CSSs Partitions Route Lists Route Groups SJCInternational DN IP Phone DNs (+E.164, urgent) DN SJCE164Local SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix Don t need CoS specific secondary lookup CSS any more USE164International UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
37 CoS International 10.0 Simplification (TP Inheritance) CSSs Partitions Route Lists Route Groups SJCInternational DN DN IP Phone DNs (+E.164, urgent) SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + Might be a good idea to keep the DN CSS as secondary lookup for intra-site dialing to avoid abbreviated intra-site dialing of unassigned extensions to flow over to the PSTN XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
38 Effect of CSS Inheritance W/ CSS Inheritance: dialing normalisation re-used W/o CSS Inheritance: dialing normalisation patterns per CoS (and site)
39 CSS Inheritance Configuration New translation pattern attribute ( Use Originator's Calling Search Space ) CSS is empty!
40 Other classes of service Other classes of service built based on CoS International by removing route patterns Re-use of all dialing normalisation patterns TP CSS inheritance allows to remove all redundancies
41 Enterprise alternate dialing Adding abbreviated on-net inter-site dialing CSSs Partitions Route Lists Route Groups SJCInternational DN IP Phone DNs (+E.164, urgent) DN SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix OnNet XXX, Pre-Dot, Prefix for all other sites Dialing normalisation for abbreviated inter-site dialing UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
42 Alternate Numbers for DNs (10.0) Can define up to two alternate numbers on DN page Enterprise and +E.164 Alternate number defined using mask If mask is empty then DN is taken as configured Alternate Numbers can(!) be added to local route partition Alternate Numbers can(!) be advertised via ILS (Global Dial Plan Replication, GDPR)
43 Enterprise alternate dialing Adding abbreviated on-net inter-site dialing CSSs Partitions Route Lists Route Groups SJCInternational DN IP Phone DNs (+E.164, urgent) DN SJCIntra 1XXX, Prefix SJCtoE164local 9.[2-9]XXXXXX, Pre-Dot, Prefix OnNet Enterprise alternate numbers Partition holding all enterprise alternate numbers defined for DNs UStoE164International 9011.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 9.1[2-9]XX[2-9]XXXXXX, Pre-Dot, Prefix + XYZ RG PSTNInternational USPSTNNational SJCPSTNLocal \+1408[2-9]XXXXXX, Urgent LOC RL Local Route Group
44 Alternate Numbers Alternate numbers can be put into local partitions (added to local dial plan) Alternate numbers allow to implement up to two overlay dialing habits Even abbreviated intra-site dialing could be implemented using the alternate numbers Abbreviated intra-site dialing is site-specific Make sure to have alternate numbers in site specific partitions Caution: abbreviated intra-site dialing should not be advertised to other clusters! In general alternate numbers should be globally significant
45 Remember Workarounds required pre-10.0: Translation patterns used to normalise dialing to +E.164 Because TPs resulting CSS implements new CoS (does not inherit the initial CoS), we need normalisation per CoS Non urgent DNs: Need to create urgent translation patterns to avoid T302 based on overlap between DNs and variable length PSTN route patterns 10.0 dial plan enhancements simplify the design: Urgent priority for DNs Translation pattern CSS inheritance
46 Inbound Routing on Gateways Internal DNs are +E.164 Format of received called party number is provider and technology depending Route after globalizing to +E.164 on ingress Options Incoming Called Party Settings: Prefixes and CSSes per number type (pre 10.0: not on MGCP gateways and SIP trunks) Inbound calls CSS; Translation Patterns to get to +E.164
47 Inbound Routing on Gateways Incoming Called Party Settings H.323 Gateway, H.323 trunk Prefix or transformation CSS per type Transformation CSS not used for call routing only for number transformations! Example: PSTN gateway in site ESC
48 Emergency Calls Emergency Calls need to be enabled for ALL classes of service Emergency Calls need to be routed through an egress gateway local to the caller Different Emergency Numbers: US: 911 Europe: 112 Other... Options: Put emergency pattern in device CSS EM users use visited site s emergency calling format (recommended, but consider overlaps!) Add emergency partition to all CoS CSSes EM uses use home site s emergency calling format
49 Tail-End-Hop-Off Business case for national TEHO difficult Caller ID preservation? CLIP No Screening National restrictions for international TEHO? TEHO implemented through specific route pattern overlays
50 International TEHO Full Picture CSSs Partitions Route Lists Route Groups ESCInternational DN All IP Phone DNs (+E.164) DN E164OnNet ESCIntra 9XXX, Prefix ESCE164Local GERE164International ESCtoE164local 0.[^0]!, Pre-Dot, Prefix [^0]!#, Pre-Dot, Prefix GERtoE164International 000.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 00.[^0]!, Pre-Dot, Prefix [^0]!#, Pre-Dot, Prefix +49 PSTNInternational GERPSTNNational \+49! \+49!#, Strip Trailing # ESCPSTNLocal \ ! \ !#, Strip Trailing # LOC RL Local Route Group XYZ RG
51 International TEHO Full Picture CSSs Partitions Route Lists Route Groups ESCInternational DN All IP Phone DNs (+E.164) DN E164OnNet ESCIntra 9XXX, Prefix ESCE164Local GERE164International ESCtoE164local 0.[^0]!, Pre-Dot, Prefix [^0]!#, Pre-Dot, Prefix GERtoE164International 000.!, Urgent, Pre-Dot, Prefix !#, Urgent, Pre-Dot, Prefix + 00.[^0]!, Pre-Dot, Prefix [^0]!#, Pre-Dot, Prefix +49 PSTNInternational GERPSTNNational \+49! \+49!#, Strip Trailing # ESCPSTNLocal \ ! \ !#, Strip Trailing # LOC RL Local Route Group XYZ RG
52 International TEHO Full Picture CSSs Partitions Route Lists Route Groups DFW GW US TEHO SJC GW PSTNInternational \+1XXX XXX XXXX \+49! UStoE164International \+49!# GER TEHO Local Route Group ESC GW STU GW Local Route Group
53 Reference Dial Plan Number Presentation
54 Calling/Called Number Transformations What It Is: Concept Calls presented to a phone or a gateway typically require the calling and the called party numbers be adapted to the local preferences/requirements of: The user receiving the call The gateway the call is routed through The network the call is routed to Calls received from an external network (e.g., the PSTN) typically present calls in a localised flavor. We can now adapt the received call based on: The numbering plan presented by the network for a specific call The called/calling number delivered into the UC system by the gateway Combining the two elements above, we can globalise the number upon entry
55 Globalise on Ingress Goal is to get to +E.164 Service Parameter: Prefixes per type for H.323, MGCP and SIP (unknown only) Not recommended Device Pool Prefixes or CSSes per number type Gateway/Trunk Prefixes or CSSes per number type (only unknown on SIP trunks); Example: Gateway for ESC
56 Localise on Phones Transform Calling Party Number to shortest possible format or respective outbound dialing habit Example for SJC phones ( XXX): Calls from Display as XXX 1XXX +1 XXX XXX XXXX 91 XXX XXX XXXX or XXX XXX XXXX +XX XX... or +XX... Callback from missed calls directory goes to pre-transformation number! (globalised number) * Displayed number does not need to be dialable * * depending on phone model
57 Number Transformations Similar to translation pattern, but matches on calling (not CALLED) party number Only allow calling party transformations No impact on call routing Addressed by partitions and CSSes (like regular patterns)
58 Calling Party Normalisation From +E.164 to Shortest Presentation CSSs SJCphonesFromE164 Partitions SJCphonesFromE164 \ !, Strip Pre-Dot \+1408.!, Strip Pre-Dot, Prefix 9 For Your Reference DFWphonesFromE164 ESCphonesFromE164 STUphonesFromE164 DFWphonesFromE164 \ !, Strip Pre-Dot \+1972.!, Strip Pre-Dot, Prefix 9 ESCtoE164local USphonesFromE164 \+.1!, Strip Pre-Dot, Prefix 9 \+.!, Strip Pre-Dot, Prefix 9011 ESCphonesFromE164 \ !, Strip Pre-Dot \ !, Strip Pre-Dot, Prefix 0 STUphonesFromE164 \ !, Strip Pre-Dot \ !, Strip Pre-Dot, Prefix 0 ESCtoE164local GERphonesFromE164 \+49.!, Strip Pre-Dot, Prefix 00 \+.!, Strip Pre-Dot, Prefix 000
59 Number Transformations on Endpoints Phones have Inbound and Outbound Calls Calling Party Transformation CSS Inbound: calls originating from endpoint; typically used to map from DN to +E.164 Outbound: calls terminating on endpoint; typically used to map from globalised calling party to display format Can also be configured on device pool Use Device Pool... Device Pool New in 9.0 Endpoint
60 End-to-End Calling Party Transformations Inbound / Outbound calls Outbound calling party transformation Inbound calling party transformation /national Inbound calling party transformation Outbound calling party transformation Version 9.0 V /national Caller ID for Calls From This Phone Calling party transformation Remote Number calling party transformation Version 9.1
61 Phone Directories Calling Party Numbers are transformed using phone s (or device pool s) outbound calling party transformation CSS But: pre-transformation number is stored in missed calls directory and used for callback * Concept: Pre-transformation calling party numbers should be globalised globalise on ingress, localise on egress Globalised numbers (pre-transformation) have to be routable! (supported dialing habit) * 7940/60 store post transformation number in missed/received calls directory (9.1 and later)
62 Egress Called Party Normalisation Gateways / Trunks required format for calling party numbers typically defined by the provider use Calling Party Transformation CSS for outbound calls Caveat: device level transformations have no effect on Q.SIG APDUs
63 Egress Called Party Normalisation Example: German PSTN Gateway
64 Egress Calling Party Normalisation Gateways / Trunks Like called party normalisation, but use CALLING party transformation patterns and CSS! When using the device pool calling party CSS make sure that device pool is not shared by phones and gateways (typically require different transformations) Optional: Filter non-dids and send dummy instead Implement screening, if number does not match the number range assigned to the trunk by the provider
65 Deterministic Inter-Cluster Routing (Global Dial Plan Replication)
66 Multicluster URI routing sfo.cisco.com nyc.cisco.com Host part of URIs might identify home cluster Reachability established through SIP route patterns for host parts Requires hierarchical URI scheme
67 Multicluster URI routing sfo.cisco.com nyc.cisco.com Host part of URIs might identify home cluster Reachability established through SIP route patterns for host parts Requires hierarchical URI scheme What if URI scheme is flat?
68 Multicluster URI routing Host part of URIs might identify home cluster Reachability established through SIP route patterns for host parts Requires hierarchical URI scheme What if URI scheme is flat??
69 Intercluster Lookup Service (ILS) Fundamental idea Need mechanism that allows propagation of individual alpha URIs between call controls binds alpha URI with attribute that allows routing to URI s home cluster ILS each call control replicates it s alpha URIs to it s neighbours each call control also announces SIP route string together with the alpha URIs SIP route string can be routed based on SIP route patterns intercluster routing of alpha URIs not based on URIs host part, but on SIP route string
70 ILS Learning Learned from ILS nyc.route fra.route sfo.route nyc.route Learned from ILS sfo.route fra.route routestring: sfo.route Call controls establish ILS Exchange ILS Exchange routestring: nyc.route URI information flooded Each call control creates table with URIs and associated SIP route string SIP route strings routed by SIP route patterns Learned from ILS sfo.route nyc.route routestring: fra.route
71 Routing Alpha URI Using ILS Information Learned from ILS nyc.route fra.route 3) ILS Lookup leads to routestring fra.route 1) Alice calls 2) not routeable using Alice s CSS (not a local URI) routestring: sfo.route ILS Exchange 4) call gets routed using SIP route pattern fra.route SIP route pattern can point to route lists starting with CUCM 9.0 5) jkrohn@cisco.com is routeable using the trunk s CSS (is a local URI) jkrohn@cisco.com routestring: fra.route
72 Inter-cluster URI routing recap URIs (especially flat URIs) can not be used as addresses ; they only are identifiers Introduce a location attribute (SIP route string) Bind set of identifiers (URIs) to a common location attribute (SIP route string) Indirect routing: route identifiers (URIs) according to learned location attribute (SIP route string)
73 GDPR Motivation On-Net/Off-Net decision w/ multiple call controls Maintained manually XXX XXX XXX XXX XXX XXX PSTN XXX XXX Each call control has to take independent on-net/off-net decisions Requires knowledge about remote on-net addresses Explicit configuration of remote address ranges or automatic learning? Complexity depending on number of prefixes!
74 GDPR Motivation Local On-Net/Off-Net w/ Centralized Dial Plan? Maintained manually Really? PSTN XXX XXX SME to centralize dial plan, apps, PBX interconnect etc Default routing on leaf vs. local on/off-net descision XXX XXX
75 GDPR Concept New in release 10.0 Split identity of (E.164) numbers Identifier: non-wildcarded number identifies a callable endpoint Address: number/pattern used to identify the location (typically prefix based) Global Dial Plan Replicaton (GDPR) allows to route numeric destinations based on locaton attribute (SIP route string) Reachability information associated with SIP route string (location information) Arbitrary topology of SIP trunks, arbitrary SIP route string address space structure Think of splitting location from identity for +E.164 numbers Location of +E.164 identifier now determined based on SIP route strings (locators) LISP for +E.164 DN is the key identity (address) in Communications Manager
76 GDPR Concept New per DN attributes: +E.164 alternate number and/or Enterprise alternate number (one can be assigned as PSTN fallback number) Defined using a mask Can be put into local partition (to implement alternate dialing habit) Can be advertised via ILS Advertized patterns +E.164 or enterprise number pattern PSTN failover: use pattern directly (+E.164) or strip/prefix instruction Differentiated partitions for learned numbers and patterns
77 GDPR learning and routing Global Learned E.164 Numbers nyc.route fra.route sfo.route nyc.route Global Learned E.164 Numbers sfo.route fra.route routestring: sfo.route Call controls establish ILS Exchange ILS Exchange routestring: nyc.route GDPR information flooded Each call control puts learned patterns/numbers in respective partitions and associated them with learned SIP route string Global Learned E.164 Numbers sfo.route nyc.route routestring: fra.route SIP route strings routed by SIP route patterns
78 Routing Call to remote Number using ILS Information Global Leaned +E.164numbers nyc.route fra.route 2) Match on learned numeric +E.164 pattern in digit analysis leads to SIP route string fra.route 1) Alice calls routestring: sfo.route ILS Exchange 3) call gets routed using SIP route pattern fra.route routestring: fra.route 4) is routeable using the trunk s CSS (is a local DN)
79 ILS Networking, GDPR Learning and Routing Components of end-to-end dialing/routing ILS networking GDPR propagation SIP trunk SIP route pattern 84969XXX route: fra.route route string: nyc.route ILS networking GDPR propagation 84953XXX (fra.route) 84969XXX (nyc.route) SIP Trunk route string: fra.route 84953XXX route: nyc.route SIP connectivity is foundation for call routing based on SIP route patterns ILS networking is foundation for exchange or GDPR reachability information GDPR propagation/exchange is enabled independent of ILS networking
80 GDPR Number Types Enterprise Alternate Number : Enterprise specific dialing habit (abbreviated on-net dialing, e.g ) +E.164 Alternate Number : +E.164 number (e.g ) Enterprise Pattern : Wildcarded Enterprise specific dialing habit (e.g XXX) +E.164 Patterns : Wildcarded +E.164 (e.g XXX) Example: DN 9764 (not recommended, but ) +E.164 Alternate Enterprise Alternate: Enterprise Pattern: 84969XXX +E.164 Pattern: XXX Site ESC: +E.164 range XXX Enterprise range: 84969XXX
81 GDPR Information Exchange Single Catalog per ILS cluster can contain: Per DN GDPR information Up to 5 URI aliases Enterprise alternate number (abbreviated inter-site dialing) +E.164 alternate number PSTN failover number (for numeric and URI dialing) DN independent GDPR information Enterprise pattern (abbreviated inter-site dialing): summary per DID range +E.164 pattern: summary per DID range Additional catalogs: imported GDPR catalogs Individual SIP route string per imported catalog Advertised into GDPR by cluster the catalog is imported on Use case: proxy for systems not supporting GDPR/ILS
82 Advertising Patterns vs. individual Alternate Numbers All advertised numbers and patterns are added to digit analysis on the receiving cluster Only advertising summaries (patterns) reduces the numbers of entries to be considered on the receiving side Individual numbers need to be advertised if numbers can t be summarized (e.g. one DN from range moved to different cluster) or local on/off-net decision is absolutely required! Otherwise call to unassigned DN in +E.164 range might be sent to remote cluster only to be blocked there (Shouldn t really be a problem)
83 GDPR in an Enterprise Dial Plan Dialing learned numbers Up to three intercluster dialing habits to reach remote DN: Enterprise (8+7) based on enterprise alternate/pattern +E.164 based on +E.164 alternate/pattern URI Assuming that CoS does not depend on dialing habit all remote patterns can be put into single partition onnetremote CSSs SJCInternational ILS learned URIs are reachable from any device (, but the SIP route patterns potentially are not) DN Partitions DN All IP Phone DNs (+E.164) SJCtoE164 1XXX, Prefix [2-9]XXXXXX, Pre-Dot, Prefix onnetremote All patterns/numbers learned via GDPR + SIP route patterns for SIP route strings onnetremote added to all CSSes with CoS On-net Also make sure to add SIP route pattern matching on SIP route strings to onnetremote partitions
84 PSTN failover for URI dialed calls with GDPR GDPR learned: (east.route) Alternate: east.route west.route CAC or SIP trunk failure Alternate (+E.164) PSTN GDPR provides PSTN alternate number for learned URIs If primary call fails (CAC failure or SIP trunk failure) reroute to PSTN using PSTN failover number and AAR CSS of calling device
85 SIP Routing
86 SIP Request Routing Flowchart Is LHS numeric? no Does whole URI match one in the CSS and URI table? no Does whole URI match one in ILS? no Does RHS match a SIP Route Pattern? no Block call yes yes yes No match yes Route/block based on existing numeric rules (see next slide) Offer call Note: Assume only alice@cisco.com is in URI table, 1) alice@cucm IP address will not route. 2) alice@cfqdn will not route Route using SIP route patterns based on routing string provided by ILS example.org Route based on RHS Fallback for alpha-uris not local and not found in ILS! e.g. default routing left-hand-side (LHS) right-hand-side (RHS)
87 Numeric SIP Request Routing Flowchart Is RHS the IP address of a cluster member? no Does RHS match CFQDN? no Does RHS match OTLD? no Match RHS against SIP Route Pattern Route or block yes yes yes Analyze LHS Route or block Does LHS find a match? yes Offer call no numeric pattern actually routed based on RHS and not based on numeric dial plan
88 Clusterwide Domain Configuration OTLD: single domain CFQDN: one or more names separated by spaces Max 255 chars Allows wildcards; e.g. *.eu-cluster.home.org
89 Always set CFQDN and OTLD Set OTLD to match single(!) corporate domain name Make sure to set the CFQDN to match host names of all cluster nodes DNS naming structure might help e.g.: *.cucmeu.home.org for pub.cucmeu.home.org, sub1.cucmeu.home.org, Keep in mind that fallback routing based on RHS is implemented for: Alpha URIs not found locally Numeric URIs with RHS = OTLD not found in numeric lookup
90 Fully Qualified Domain Name in SIP Requests Always set Use Fully Qualified Domain Name in SIP Requests in SIP profile of all SIP trunks and endpoints involved: CUCM will relay an alphanumeric hostname of a caller to the called endpoint as a part of the SIP header information. This enables the called endpoint to return the call using the received or missed call list Mainly important for numeric IDs, but in mixed environments where numeric and alpha URIs exist, it s important to always have FQDNs in SIP requests for all calls For endpoints registered with CUCM the FQDN in SIP requests will be set to the OTLD configured in the enterprise parameters
91 Use Fully Qualified Domain Name in SIP Requests Example Route call cross-cluster INVITE RPID: INVITE RPID: ( Fully Qualified turned on) -or- INVITE RPID: ( Fully Qualified turned off) 180 Ringing RPID: ( Fully Qualified turned on) -or- 180 Ringing RPID: ( Fully Qualified turned off) 180 Ringing RPID: sip:bob@cisco.com
92 URI Handling on SIP Trunks
93 RHS of numeric URIs on SIP trunks Numeric dialing 1234 OTLD:home.org Route Pattern: 1234, matched *.org INVITE To: CUCM builds RHS of request and To: URI for numeric destinations based on configured SIP trunk destination Constructing RHS of To: and request URI makes perfect sense in pure numeric dialing environment where no concept of a URI host portion exists on the user side
94 RHS of numeric URIs on SIP trunks RHS of numeric URI matches OTLD, numeric match OTLD:home.org Route Pattern: 1234, matched *.org INVITE To: CUCM still builds RHS of request and To: URI for numeric destinations based on configured SIP trunk destination Numeric destination matched against numeric dial plan (OTLD match) and matches against configured route pattern When routed through a numeric route pattern RHS of To: and request URI are rewritten use FQDN in SIP requests setting on SIP trunk has no impact; only applied to calling/connected ID
95 RHS of numeric URIs on SIP trunks RHS of numeric URI matches OTLD, no numeric match OTLD:home.org Route Pattern: 1234 *.org, matched INVITE To: CUCM maintains original request URI but still rewrites RHS of To: URI based on configured SIP trunk destination Numeric destination matched against numeric dial plan (OTLD match), but no numeric match found Fallback to routing based on SIP route patterns RHS of To: URI not critical for routing (routing based on request URI), but possibly problematic if remote entities evaluate the To: URI for some reason
96 RHS of numeric URIs on SIP trunks RHS of numeric URI does not match OTLD OTLD:home.org Route Pattern: 1234 *.org, matched INVITE To: CUCM maintains original request URI but still rewrites RHS of To: URI based on configured SIP trunk destination RHS of request URI does not match OTLD; hence only routed based on SIP route patterns RHS of To: URI not critical for routing (routing based on request URI), but possibly problematic if remote entities evaluate the To: URI for some reason
97 RHS of numeric URIs on SIP trunks Summary For numeric destinations the RHS of the To: URI is always(!) rewritten RHS of request URI is only rewritten, if session is routed by match on numeric pattern Keep in mind that some numeric URIs are actually not routed numerically For these cases CSCtr30922 changes the behavior so that the To: URI is identical to request URI (check defect for integrated release, currently only 10.x)
98 Remember Best and most important tools for dial plan design: Pencil Paper Whiteboard Dial plans are not a new concept IP did not really change the fundamentals of dial plan design Dial Plan recommendations are not a monolith Take what you need Keep it simple!
99 Continue the Conversation using Cisco Spark Sign up free for Cisco Spark at Download the application from ios App Store, Google Play Store, or from Visit the World of Solutions Cisco Spark area for demos Use Cisco Spark to continue the conversation or ask any additional questions with the speaker for this session. The room name is BRKUCC-3000 How to get added to the Cisco Spark room for this session To opt in, send an to with the message Please add me to the BRKUCC-3000
100 Complete Your Online Session Evaluation Give us your feedback to be entered into a Daily Survey Drawing. A daily winner will receive a $750 Amazon gift card. Complete your session surveys though the Cisco Live mobile app or your computer on Cisco Live Connect. Don t forget: Cisco Live sessions will be available for viewing on-demand after the event at CiscoLive.com/Online
101 Continue Your Education Demos in the Cisco campus Walk-in Self-Paced Labs Table Topics Meet the Engineer 1:1 meetings Related sessions
102 Thank you
103
Advanced Dial Plan Design for Unified Communications Networks
Advanced Dial Plan Design for Unified Communications Networks Johannes Krohn Technical Marketing Engineer Abstract This advanced session provides detailed dial-plan design guidelines for each of the Cisco
More informationGlobalized Dial Plan Design. Danny Wong Session ID 20PT
Globalized Dial Plan Design Danny Wong Session ID 20PT Abstract This advanced session provides detailed dial-plan design guidelines for each of the Cisco IP telephony deployment models based on Cisco Unified
More informationEnabling Seamless Collaboration with Advanced Session Routing Architectures and Cisco Spark
BRKUCC-3001 Enabling Seamless Collaboration with Advanced Session Routing Architectures and Cisco Spark Johannes Krohn, Technical Marketing Engineer Cisco Spark How Questions? Use Cisco Spark to communicate
More informationEnterprise Dial Plan Fundamentals
BRKUCC-2800 Enterprise Dial Plan Fundamentals Johannes Krohn Abstract This session explains the various fundamental dial plan elements of Cisco Unified Communications Manager with a focus on Enterprise
More informationCisco Unified CM SIP Trunking, Session Management, and Global Dial Plan Replication
LTRUCC-2150 Cisco Unified CM SIP Trunking, Session Management, and Global Dial Plan Replication Paul Giralt - @PaulGiralt Markus Schneider - @Markus73 Agenda Objectives Technology Overview Unified CM Session
More informationNávrh číslovacího plánu, URI dialing
Cisco Expo 2012 Návrh číslovacího plánu, URI dialing T-COL2 /L2 Ivan Sýkora Cisco Cisco Expo 2012 Cisco and/or its affiliates. All rights reserved. 1 Twitter www.twitter.com/ciscocz Talk2cisco www.talk2cisco.cz/dotazy
More informationConfigure Global Dial Plan Replication
Global Dial Plan Replication Overview, page 1 Global Dial Plan Replication Prerequisites, page 3 Global Dial Plan Replication Task Flow, page 3 Global Dial Plan Replication Overview Use global dial plan
More informationCisco Unified Communications Manager Trunk Types
Cisco Unified Communications Manager Trunk Types This chapter provides information about trunk types. In a distributed call-processing environment, Cisco Unified Communications Manager communicates with
More informationCalling Party Transformation Pattern Configuration
CHAPTER 47 Calling Party Transformation Pattern Configuration Use the following topics to find, add, update, copy, or delete a calling party transformation pattern: Settings, page 47-1 Related Topics,
More informationImplementing Cisco Unified Communications Manager Part 2, Volume 1
Implementing Cisco Unified Communications Manager Part 2, Volume 1 Course Introduction Learner Skills and Knowledge Course Goal and Course Flow Additional Cisco Glossary of Terms Your Training Curriculum
More informationThis chapter provides information about Cisco Unified Communications Manager trunk configuration.
Trunk setup This chapter provides information about Cisco Unified Communications Manager trunk configuration. About trunk setup, page 1 Find trunk, page 57 Set up trunk, page 57 Delete trunk, page 59 Reset
More informationCalled Party Transformation Pattern Configuration
CHAPTER 48 Called Party Transformation Pattern Configuration Use the following topics to configure a called party transformation pattern: Settings, page 48-1 Related Topics, page 48-4 Settings In Cisco
More informationNumber: Passing Score: 800 Time Limit: 120 min File Version:
300-075 Number: 300-075 Passing Score: 800 Time Limit: 120 min File Version: 8.0 300-075 Implementing Cisco IP Telephony & Video, Part 2 v1.0 Version 8.0 Sections 1. VCS Control 2. Collaboration Edge (VCS
More informationITBraindumps. Latest IT Braindumps study guide
ITBraindumps http://www.itbraindumps.com Latest IT Braindumps study guide Exam : 300-075 Title : Implementing Cisco IP Telephony & Video, Part 2 v1.0 Vendor : Cisco Version : DEMO Get Latest & Valid 300-075
More informationUnified Communications Design
CHAPTER 7 Introduction While many school networks still use legacy PBX phone systems, many are migrating to the advantages of IP-based voice. Lower in cost, and more flexible and reliable, the Cisco Unified
More informationBRKCOC-2399 Inside Cisco IT: Integrating Spark with existing large deployments
Inside Cisco IT: Integrating Spark with existing large deployments Jan Seynaeve, Sr. Collaborations Engineer Luke Clifford, Sr. Collaborations Engineer Cisco Spark How Questions? Use Cisco Spark to communicate
More informationHunt Pilot Setup. About Hunt Pilot Setup
This chapter provides information to add, configure, or delete a hunt pilot. For additional information about understanding route plans, wildcards and special characters in route patterns and hunt pilots,
More informationCall Control Discovery
CHAPTER 3 The call control discovery feature leverages the Service Advertisement Framework (SAF) network service, a proprietary Cisco service, to facilitate dynamic provisioning of inter-call agent information.
More informationOn-Site 911 Notification Using Cisco Unified Communications BRKUCC-2012
On-Site 911 Notification Using Cisco Unified Communications Session Objective This session will illustrate different methods by which an enterprise can enhance the emergency call handling At the end of
More informationUnderstanding Route Plans
CHAPTER 16 The Route Plan drop-down list on the menu bar allows you to configure Cisco Unified Communications Manager route plans by using route patterns, route filters, route lists, and route groups,
More informationTranslation pattern setup
This chapter provides information to add, update, copy, or delete a translation pattern. For additional information, see topics related to understanding route plans in the Cisco Unified Communications
More informationThis chapter provides information about using Cisco Unified Communications Manager for working with and configuring Cisco gateways.
This chapter provides information about using Cisco Unified Communications Manager for working with and configuring Cisco gateways. About gateway setup, page 1 Gateway reset, page 2 Gateway deletion, page
More informationCalling Party Normalization
This chapter describes the feature. allows you to reformat the display of calling party numbers to a globalized version that includes prefixes such as international country codes or localize the calling
More informationUnderstanding Cisco Unified Communications Manager Voice Gateways
CHAPTER 38 Understanding Cisco Unified Communications Manager Voice Gateways Cisco Unified Communications gateways enable Cisco Unified Communications Manager to communicate with non-ip telecommunications
More informationCisco Exam Questions & Answers
Cisco 642-457 Exam Questions & Answers Number: 642-457 Passing Score: 800 Time Limit: 120 min File Version: 35.5 http://www.gratisexam.com/ Sections 1. 1-18 2. 19-36 3. 37-54 4. 55-72 Cisco 642-457 Exam
More informationCisco HCS Dial Plan Model with Enhanced Number Translation
Cisco HCS Dial Plan Model with Enhanced Number Translation Bulk-Loading Enhanced Number Translations, page 1 Extension Dialing Template, page 2 Extension Dialing with Prefix Template, page 3 Intrasite
More informationRoute Pattern Configuration
CHAPTER 33 Use the following topics to find, add, update, copy, or delete a route pattern: Settings, page 33-1 Related Topics, page 33-11 Settings In Cisco Unified Communications Manager Administration,
More informationRev CUCM Mobility. c cnac o okbook.com
Rev. 20170424.065954 12. CUCM Mobility c cnac o okbook.com C U C M M O B I L I T Y F E A T U R E S Mobile Connect (AKA Single Number Reach) All devices configured for mobile connect ring at the same time.
More informationDeploying B2B URI Dialing with Cisco UC Manager and VCS Expressway Solution
Deploying B2B URI Dialing with Cisco UC Manager and VCS Expressway Solution Kevin Roarty, Technical Marketing Engineer John Burnett, Technical Marketing Engineer Abstract With the 9.0 release of Cisco
More informationDirectory number setup
Directory number setup This chapter provides information about working with and configuring directory numbers (DNs) in Cisco Unified Communications Manager Administration. For additional information, see
More informationCISCO EXAM QUESTIONS & ANSWERS
CertifyMe Number: 642-427 Passing Score: 800 Time Limit: 120 min File Version: 29.0 http://www.gratisexam.com/ CISCO 642-427 EXAM QUESTIONS & ANSWERS Exam Name: TVOICE v8.0 Troubleshooting Cisco Unified
More informationCisco Exam Questions & Answers
Cisco 642-457 Exam Questions & Answers Number: 642-457 Passing Score: 800 Time Limit: 120 min File Version: 35.5 http://www.gratisexam.com/ Sections 1. 1-18 2. 19-36 3. 37-54 4. 55-72 Cisco 642-457 Exam
More informationHunt pilot setup. About hunt pilot setup
Hunt pilot setup This chapter provides information to add, configure, or delete a hunt pilot. For additional information about understanding route plans, wildcards and special characters in route patterns
More informationHunt Pilot Configuration
CHAPTER 36 Use the following topics to add, configure, or delete a hunt pilot: Settings, page 36-1 Related Topics, page 36-10 Settings In Cisco Unified Communications Manager Administration, use the Call
More informationConfigure Call Routing
Call Routing Overview, page 1 Call Routing Prerequisites, page 2 Call Routing Configuration Task Flow, page 2 Call Routing Overview The system uses route plans to determine how to route calls between clusters,
More informationConfigure Call Routing
Call Routing Overview Call Routing Overview, on page 1 Call Routing Prerequisites, on page 2 Call Routing Configuration Task Flow, on page 2 Call Routing Restrictions, on page 16 The system uses route
More informationCisco HCS Basic Call Flow Overview
Intrasite Call Between Cisco Unified IP Phones, page 1 Intersite Call Between Cisco Unified IP Phones, page 2 Intrasite and Intersite Call Between IP Phones (Flat Dial Plan), page 4 Incoming Call to and
More informationCisco Exam Questions & Answers
Cisco 642-457 Exam Questions & Answers Number: 642-457 Passing Score: 800 Time Limit: 120 min File Version: 35.5 http://www.gratisexam.com/ Sections 1. 1-18 2. 19-36 3. 37-54 4. 55-72 Cisco 642-457 Exam
More informationInfrastructure Configuration Product Fields
Infrastructure Configuration Product s Infrastructure Data Object s, page 1 Infrastructure Data Object s To create Configuration Templates, you must add infrastructure Configuration Products to the Configuration
More informationCall Display Restrictions
Overview, on page 1 Configuration Task Flow, on page 1 Interactions, on page 11 Feature Restrictions, on page 12 Overview Cisco Unified Communications Manager provides flexible configuration options that
More informationCall Forwarding. Call Forwarding Overview
Overview, page 1 Configuration Task Flow, page 3 Interactions and Restrictions, page 22 Overview As a user, you can configure a Cisco Unified IP Phone to forward calls to another phone. The following call
More informationPrepAwayExam. High-efficient Exam Materials are the best high pass-rate Exam Dumps
PrepAwayExam http://www.prepawayexam.com/ High-efficient Exam Materials are the best high pass-rate Exam Dumps Exam : 642-447 Title : Implementing Cisco Unified Communications Manager, Part 1 Vendor :
More informationTranslation Pattern Configuration
CHAPTER 42 Use the following topics to add, update, copy, or delete a translation pattern: Settings, page 42-1 Related Topics, page 42-10 Settings In Cisco Unified Communications Manager Administration,
More informationCisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration
CHAPTER 15 Cisco Unified Mobility Advantage and Cisco Unified Mobile Communicator Integration Cisco Unified Communications Manager provides certain functionality for Cisco Unified Mobile Communicator clients
More informationUnderstanding Cisco CallManager Trunk Types
42 CHAPTER In a distributed call-processing environment, Cisco CallManager communicates with other Cisco CallManager clusters, the public switched telephone network (PSTN), and other non-ip telecommunications
More informationCISCO UNIFIED COMMUNICATIONS MANAGER SIP INTEGRATION
CISCO UNIFIED COMMUNICATIONS MANAGER SIP INTEGRATION Validated Integrations: 6.1 with xic version 3.0 SU-3 and greater 7.1 with xic version 3.0 SU-6 and greater INTEGRATION DOCUMENT Version 1.19 7601 Interactive
More informationDirectory Number Configuration
CHAPTER 43 The following sections provide information about working with and configuring directory numbers (DNs) in Cisco Unified Communications Manager Administration: Settings, page 43-1 Synchronizing
More informationCCVP CIPT2 Quick Reference
Introduction...3...4 Centralized Call Processing Redundancy...11 CCVP CIPT2 Quick Reference Bandwidth Management and Call Admission Control...17 Applications for Multisite Deployments...21 Security...31
More informationCisco. Exam Questions CIPTV2 Implementing Cisco IP Telephony and Video, Part 2. Version:Demo
Cisco Exam Questions 300-075 CIPTV2 Implementing Cisco IP Telephony and Video, Part 2 Version:Demo 1. The network administrator at Enterprise X is creating the guidelines for a new IPT deployment consisting
More informationDial Plan CHAPTER. Last revised on: September 27, Cisco Unified Communications SRND (Based on Cisco Unified Communications Manager 5.
CHAPTER 10 Last revised on: September 27, 2007 The dial plan is one of the key elements of an Telephony system, and an integral part of all call processing agents. Generally, the dial plan is responsible
More informationAcano solution. Third Party Call Control Guide. 07 June G
Acano solution Third Party Call Control Guide 07 June 2016 76-1055-01-G Contents 1 Introduction 3 1.1 How to Use this Guide 3 1.1.1 Commands 5 2 Example of Configuring a SIP Trunk to CUCM 6 2.1 Prerequisites
More informationAcano solution. Third Party Call Control Guide. December F
Acano solution Third Party Call Control Guide December 2015 76-1055-01-F Contents Contents 1 Introduction... 3 1.1 How to Use this Guide... 3 1.1.1 Commands... 4 2 Example of Configuring a SIP Trunk to
More informationA New Approach to Call Routing and Dial Plans Based on the Service Advertisement Framework (SAF) BRKUCC-2003
A New Approach to Call Routing and Dial Plans Based on the Service Advertisement Framework (SAF) BRKUCC-2003 Introduction Prerequisites This Session Assumes Basic Knowledge of: Routing Protocols Dial Plans
More informationDial Plan Architecture
CHAPTER 6 Last revised on: October 30, 2009 This chapter defines and explains the key elements in designing a dial plan for an H.323 network. An H.323 video dial plan is a numbering scheme that allows
More informationHands-On CIPT1 - Telephony v8.0-v9.0 Part 1 Implementing Cisco Unified Communications IP Telephony
Hands-On Implementing Cisco Unified Communications IP Telephony Course Description This Hands-On Implementing Cisco Unified Communications Manager, Part 1 (CIPT1) v9.0 course prepares you for implementing
More informationCisco Emergency Responder Integration with Cisco Unified Communications Manager
Cisco Emergency Responder Integration with Cisco Unified Communications Manager Contents Introduction Prerequisites Requirements Components Used Basics of CER Call Flows Configuration Configuring the Cisco
More informationDesigning and deploying UC networks with Cisco Unified Session Management Edition
Designing and deploying UC networks with Cisco Unified Session Management Edition Tony Mulchrone Technical Marketing Engineer Cisco Collaboration Technology Group Housekeeping We value your feedback- don't
More informationHotline. Configuration Checklist for Hotline CHAPTER
CHAPTER 26 The hotline feature extends the Private Line Automatic Ringdown (PLAR) feature, which allows you to configure a phone so that when the user goes off hook (or the NewCall softkey or line key
More informationConfigure Gateways. Gateway Overview. Gateway Overview, page 1 Gateway Setup Prerequisites, page 3 Gateway Configuration Task Flow, page 4
Gateway Overview, page 1 Gateway Setup Prerequisites, page 3 Gateway Configuration Task Flow, page 4 Gateway Overview Cisco offers a wide variety of voice and video gateways. A gateway provides interfaces
More informationCISCO CCNP COLLABORATION Cisco Certified Network Professional Collaboration Part 1 (CIPTv1 and CIPTv2)
Our Learning Exclusive Custom exam prep software and materials Exam delivery in classroom with 98% success Course specific thinqtank Learning publications to promote a fun exciting learning Extended hours
More informationIntercluster directory URI
This chapter describes how to enable the ILS URI Replication feature in order to support intercluster dialing with directory URIs. When this feature is configured, Cisco Unified Communications Manager
More informationDesigning & Deploying UC networks with Cisco Session Management Edition
Designing & Deploying UC networks with Cisco Session Management Edition BRKUCC-2931 Follow us on Twitter for real time updates of the event: @ciscoliveeurope, #CLEUR Housekeeping We value your feedback-
More informationCisco Unified Mobility
CHAPTER 14 extends the rich call control capabilities of Cisco Unified Communications Manager from the primary workplace desk phone of a mobile worker to any location or device of their choosing. For example,
More informationAVANTUS TRAINING PTE PTE LTD LTD
[MS20337]: Enterprise Voice and Online Services with Microsoft Lync Server 2013 Length : 5 Days Audience(s) : IT Professionals Level : 300 Technology : Microsoft Lync Server Delivery Method : Instructor-led
More informationCisco Meeting Server. Load Balancing Calls Across Cisco Meeting Servers. White Paper. 22 January Cisco Systems, Inc.
Cisco Meeting Server Load Balancing Calls Across Cisco Meeting Servers White Paper 22 January 2018 Cisco Systems, Inc. www.cisco.com Contents Change History 4 Introduction 5 Load balancing across Cisco
More informationCisco Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2)
Cisco 300-075 Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) https://killexams.com/pass4sure/exam-detail/300-075 QUESTION: 90 An engineer is configuring a new DX-80 in Cisco Unified Communications
More informationCisco Communication Manager Administration v11.0 (CMA)
Course Overview This course will introduce students to the CUCM 11.0 system, the basic procedures for administering IP Phones and Users, understanding the Dial Plan and implementing Features. Who Should
More informationCisco EXAM Implementing Cisco IP Telephony and Video, Part 1 (CIPTV1) Buy Full Product.
Cisco EXAM - 300-070 Implementing Cisco IP Telephony and Video, Part 1 (CIPTV1) Buy Full Product http://www.examskey.com/300-070.html Examskey Cisco 300-070 exam demo product is here for you to test the
More informationCall Park and Directed Call Park
Call Park Overview Call Park Overview, on page 1 Call Park Prerequisites, on page 2 Call Park Configuration Task Flow, on page 2 Call Park Interactions and Restrictions, on page 17 Troubleshooting Call
More informationCall Forwarding. Call Forwarding Overview
Overview, page 1 Configuration Task Flow, page 3 Interactions and Restrictions, page 12 Overview As a user, you can configure a Cisco Unified IP Phone to forward calls to another phone. The following call
More informationConfiguration Example for CUCM Non-Secure SIP Integration with CUC
Configuration Example for CUCM Non-Secure SIP Integration with CUC Contents Introduction Prerequisites Requirements Components Used Configure Configuration on CUCM Configuration on Unity Connection Verify
More informationEnterprise Voice and Online Services with Microsoft Lync Server 2013
Enterprise Voice and Online Services with Microsoft Lync Server 2013 Course # Exam: Prerequisites Technology: Delivery Method: Length: 20337 70-337 20336 Microsoft Lync Server Instructor-led (classroom)
More informationLocal Route Groups. Configuration Checklist for Local Route Groups CHAPTER
CHAPTER 31 This chapter provides the following information about local route groups: Configuration Checklist for, page 31-1 Introducing, page 31-3 Routing with, page 31-5 Simple Local Routing, page 31-6
More informationImplementing Enterprise TelePresence and Video Communication Solution
Implementing Enterprise TelePresence and Video Communication Solution 2 Winchester Mystery House The Vision Every visual communications device, able to talk to any visual communications device, in any
More informationCisco.Actualtests v by.Edge.188q. Exam Code:
Cisco.Actualtests.642-457.v2014-02-08.by.Edge.188q Number: 642-457 Passing Score: 800 Time Limit: 120 min File Version: 16.5 http://www.gratisexam.com/ Exam Code: 642-457 Exam Name: CIPT2 v8.0 Implementing
More informationTelephony Design and Dial Plan Overview
Cisco HCS Architecture Primer, page 1 umbering Plan Design, page 5 Cisco HCS umbering Considerations, page 8 umbering at the Cisco Unified Communications Manager Interface, page 20 Cisco PGW Model and
More informationNATO Communications and Information Systems School
1.Course Title Version dated 28/Jan/2016 NATO Voice over IP Foundation Course Version 2.0 2.Identification Number (ID) 095 3. Purpose of the Course There are a number of new technologies (to NATO) that
More informationCisco Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) For More Information - Visit:
CertsChief Guaranteed Success with Accurate & Updated Questions. Cisco 300-075 Implementing Cisco IP Telephony and Video, Part 2 (CIPTV2) Questions & Answers PDF For More Information - Visit: https://www.certschief.com/
More informationCUCM XO SIP Trunk Configuration Guide
QUANTiX QFlex Session Border Controller CUCM 10.0 - XO SIP Trunk Configuration Guide Release 5.6.2-9 Document revision: 01.01 www.genband.com 2 630-02102-01 QUANTiX QFlex Session Border Controller Publication:
More informationCisco.Certkiller v by.Luger.57q. Exam Code:
Cisco.Certkiller.642-447.v2013-12-24.by.Luger.57q Number: 642-447 Passing Score: 825 Time Limit: 120 min File Version: 16.5 http://www.gratisexam.com/ Exam Code: 642-447 Exam Name: Cisco CIPT1 v8.0 Implementing
More informationReal4Test. Real IT Certification Exam Study materials/braindumps
Real4Test http://www.real4test.com Real IT Certification Exam Study materials/braindumps Exam : 300-075 Title : Implementing Cisco IP Telephony & Video, Part 2 v1.0 Vendor : Cisco Version : DEMO Get Latest
More informationCisco Unified Communications Manager Trunks
CHAPTER 2 A trunk is a communications channel on Cisco Unified Communications Manager (Cisco Unified CM) that enables Cisco Unified CM to connect to other servers. Using one or more trunks, Cisco Unified
More informationCommon Components. Cisco Unified Border Element (SP Edition) Configuration Profile Examples 5 OL
The following components of the Cisco Unified Border Element are common to all of the configuration profile examples in this document. Secure Media Adjacencies Call Policies CAC Policies SIP Profiles 5
More informationIT Exam Training online / Bootcamp
DumpCollection IT Exam Training online / Bootcamp http://www.dumpcollection.com PDF and Testing Engine, study and practice Exam : 642-445 Title : Cisco IP Telephony for Release 5.x Vendors : Cisco Version
More informationConfigure Multilevel Precedence and Preemption
Multilevel Precedence and Preemption Overview, on page 1 Multilevel Precedence and Preemption Prerequisites, on page 1 Multilevel Precendence and Preemption Task Flow, on page 1 Multilevel Precedence and
More informationExtend and Connect. Extend and Connect Overview
Overview, page 1 Prerequisites, page 2 Configuration Task Flow, page 2 Interactions and Restrictions, page 8 Overview The feature allows administrators to deploy Unified Communications (UC) Computer Telephony
More informationExam Name: Implementing Cisco Unified Communications Manager, Part 1 v8.0 (CIPT1 v8.0)
Vendor: Cisco Exam Code: 642-447 Exam Name: Implementing Cisco Unified Communications Manager, Part 1 v8.0 (CIPT1 v8.0) Version: Demo QUESTION 1 Which three options correctly describe the role of a subsequent
More informationCall Display Restrictions
This chapter provides information about the feature which allows you to choose the information that will display for calling and/or connected lines, depending on the parties who are involved in the call.
More informationImplementing Cisco Unified Communications Manager, Part 2 v8.0 (CIPT2 v8.0)
Implementing Cisco Unified Communications Manager, Part 2 v8.0 (CIPT2 v8.0) Number: 642-457 Passing Score: 720 Time Limit: 120 min File Version: 12.0 http://www.gratisexam.com/ Exam A QUESTION 1 Which
More informationCourse 20337B: Enterprise Voice and Online Services with Microsoft Lync Server 2013 Exam Code: Duration:40 Hrs
Course 20337B: Enterprise Voice and Online Services with Microsoft Lync Server 2013 Exam Code: 70-337 Duration:40 Hrs Course Outline Module 1: Voice Architecture This module introduce Enterprise Voice
More informationSpectrum Enterprise SIP Trunking Service Cisco Unified Communication Mgr Firmware 6.01 IP PBX Configuration Guide
Spectrum Enterprise SIP Trunking Service Cisco Unified Communication Mgr Firmware 6.01 IP PBX Configuration Guide About Spectrum Enterprise: Spectrum Enterprise is a division of Charter Communications
More informationConfigure Intercluster Lookup Service
Intercluster Lookup Service Overview, page 1 ILS Prerequisites, page 2 ILS Configuration Task Flow, page 2 ILS Interactions and Restrictions, page 9 Intercluster Lookup Service Overview The Intercluster
More informationVoice Topology: Lync 2010
Voice Topology: Lync 2010 PIC XMPP MSN AOL Yahoo DMZ UC Endpoints Archiving Monitoring Remote Users UC Pool AD DNS Front End (incl. Mediation) Back End AV Conf. Federated Businesses Edge Services SIP Trunking
More informationSIP Devices Configuration
Set Up Ingress Gateway to Use Redundant Proxy Servers, page 1 Set Up Call Server with Redundant Proxy Servers, page 1 Local SRV File Configuration Example for SIP Messaging Redundancy, page 2 Load-Balancing
More informationAdministering Cisco Unified Communication Manager and Unity Connection (ACUCM+AUC)
Administering Cisco Unified Communication Manager and Unity Connection (ACUCM+AUC) COURSE OVERVIEW: Administering Cisco Unified Communications Manager (ACUCM) provides system administrators and networking
More informationSIP Devices Configuration
Set Up Ingress Gateway to Use Redundant Proxy Servers, on page 1 Set Up Call Server with Redundant Proxy Servers, on page 1 Local SRV File Configuration Example for SIP Messaging Redundancy, on page 2
More informationConfigure Cisco Unified Communications Manager
Configure Cisco Unified Communications Manager Overview, on page 1 Set Up Phone Route Plans, on page 2 Set Up Cisco Unified Communications Manager for Emergency Responder, on page 3 Create Emergency Responder
More informationImplementing Cisco IP Telephony & Video, Part 1 (CIPTV1) 1.0
Implementing Cisco IP Telephony & Video, Part 1 (CIPTV1) 1.0 COURSE OVERVIEW: Implementing Cisco IP Telephony & Video, Part 1 (CIPTV1) v1.0 is a five-day course that prepares the learner for implementing
More informationIC 4.0 SIP INTEGRATION TO CISCO UNIFIED COMMUNICATIONS MANAGER 9.X INTEGRATION DOCUMENT. Version 4.07
IC 4.0 SIP INTEGRATION TO CISCO UNIFIED COMMUNICATIONS MANAGER 9.X Validated Integrations: CUCM 9.x with xic version 4.0 SU-2 (support included for all 4.0 SU s) CUCM 9.x with xic version 3.0 SU-15 (support
More informationEnhanced Location Call Admission Control
The following sections provide information about the feature. Configure, page 1 Feature, page 2 Architecture, page 4 Location Bandwidth Service Parameters, page 8 Shadow System Location, page 8 Devices
More information