1 / 61

Enabling Single-Site On-Net Calling

Implementing Calling Privileges in Cisco Unified Communications Manager. Enabling Single-Site On-Net Calling. Outline. Calling Privileges Overview Partitions and Calling Search Spaces Time Schedules and Time Periods Client Matter Codes and Forced Authorization Codes

bess
Download Presentation

Enabling Single-Site On-Net Calling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Implementing Calling Privileges in Cisco Unified Communications Manager Enabling Single-Site On-Net Calling

  2. Outline Calling Privileges Overview Partitions and Calling Search Spaces Time Schedules and Time Periods Client Matter Codes and Forced Authorization Codes Calling Privileges Applications Overview Implementing Class of Service Implementing 911 and Vanity Numbers Implementing Time of Day-Based Carrier Selection Implementing Private Line, Automatic Ringdown

  3. Calling Privileges Overview

  4. Calling Privileges Calling privileges (also called class of service) define the entries of a call routing table that can be accessed by an endpoint performing a call routing request. Used to control telephony charges Block costly service numbers Restrict international calls Used for special applications including: Route calls with the same number differently per user(different gateway per site for PSTN calls) Route calls to the same number differently per time of day

  5. Call Privileges Requirement Example

  6. Call Privileges Configuration Elements

  7. Partitions and Calling Search Spaces

  8. Partitions and Calling Search Spaces A partition is a group of numbers with same reachability. Any dialable patterns can be part of a partition (directory numbers, route patterns, translation patterns, voice-mail ports, Meet-Me conference numbers, etc.). Calling search space is a list of partitions and includes the partitions that are accessible by this CSS. A device can call only those numbers located in the partitions that are part of its calling search space. Assigned to any entity that can generate a call routing request, including phones, phone lines, gateways, and applications.

  9. Partition <None> and CSS <None> Before partitions and CSS are configured, all entities that can have a partition (i.e., called entities such as directory numbers, route patterns, etc.) reside in partition <None>, and all entities that can have a CSS (calling entities such as phones or trunks) are assigned with CSS <None>. Entities that are in partition <None> are always accessible (regardless whether the calling entity has a CSS or not). Entities that have CSS <None> assigned can only access entities that are in partition <None>.

  10. Analogy: Locks and Key Rings No Partition Assigned Partitions: Phones Phone1 Phone2 Phone3 Phone4 Phone5 No CSS Assigned CSSs: Phone1: Phone2, Phone3, Phone4, Phone5 Phone2: Phone1, Phone3, Phone4, Phone5 Phone3: Phone2, Phone4 Phone4: Phone1, (Phone4) Phone5: Phone4 Effective Permissions:

  11. Basic Partitions and CSS Example Partition Chicago Partition San Jose Partition Atlanta 3001 Phone 2-1 2001 4001 Phone 3-1 Phone 1-1 Phone CSS contains two partitions. 2 1 User dials 3001. CSS Phone 2-1 DN 3001 lies in partition Chicago. 3 Phone 2-1 will ring. Phone 3-1 DN 4001 lies in partition Atlanta. Not included in routing decision.

  12. CSS Partition Order Relevance A CSS is an ordered list of partitions. All accessible entities of the call routing table are considered by best-match logic. Entities which are in a partition that is listed in the CSS of the calling entity Entities which do not have a partition assigned Multiple identical entities can exist in the call routing table but must be in different partitions. If no single best match, the entry of the call rouitng table is used whose partition is listed first in the CSS of the calling device. Resulting route selection priorities: Best match If multiple, equally qualified matches, order of partition is tie breaker

  13. Partitions and CSS Example with Multiple Best Matches Partition Chicago Partition San Jose Partition Atlanta 3001 Phone 2-1 3001 3001 Phone 3-1 Phone 1-1 Phone CSS contains two partitions. 1 User dials 3001. CSS Phone 2-1 DN 3001 lies in partition Chicago. 2 Phone 1-1 DN 3001 lies in partition San Jose. Phone2-1 and Phone1-1 match equally well. Phone2-1 is used because its partition is listed first. Phone 2-1 and Phone 1-1 match equally well. Phone 2-1 is used because its partition is listed first in calling phone’s CSS. Phone 3-1 DN 3001 lies in partition Atlanta. Not included in routing decision.

  14. Phones Have a Device CSS andLine CSS IP phones can have a CSS configured at each line and at the device. CSS of the line from which the call is placed is considered first Device CSS is then added Effective CSS consists of: Line CSS Device CSS Line CSS Partition L1 Partition L2 Resulting CSS Partition L1 Partition L3 Line Partition L2 Partition L3 Partition D1 Device CSS Partition D2 Partition D1 Partition D3 Partition D2 Device Partition D3

  15. Example with IP Phone Line CSS andDevice CSS A phone with both line anddevice CSS configured dials extension “3001”. Line CSS and device CSS are concatenated with line CSS ontop of device CSS. Route pattern 300X is eliminated because other entries are better matches. Two entries in different partitions (Chicago and Atlanta) found by best-match algorithm. Best match of first listed partition (Chicago) is used. Partition Chicago Partition Atlanta Partition San Jose 3001 Phone 2-1 3001 300X Phone 3-1 Route Pattern Line CSS Device CSS

  16. Class of Service Sample Scenario Assigned CSS determines calling privilege CSS Internal CSS Local CSS LD CSS International Partition Phones (all Phone DNs) Internal Calls X Partition Local-PSTN 9[2-9]XXXXXX Local Calls X X Partition LD-PSTN 91[2-9]XX[2-9]XXXXXX Long-Distance Calls X X X Partition Intl-PSTN 9011!# International Calls

  17. Configuring Partitions and CallingSearch Spaces There are two steps of configuration: Partition configuration in Cisco Unified CM: Create new partitions. Assign partitions to directory numbers, route patterns, translation patterns. Calling search spaces configuration in Cisco Unified CM: Create new calling search space. Select list of partitions for eachcalling search space. Assign calling search space to lines, devices,and translation patterns.

  18. Creating Partitions Enter list of partitions and descriptions (separated by comma)

  19. Assigning Partitions Note: Assign partitions to directory numbers, route patterns, translation patterns, etc.

  20. Creating a Calling Search Space Add or remove highlighted partition to or from CSS Change order of partitions in CSS by moving highlighted partition up or down

  21. Assigning CSS to IP Phone Assign CSS to Phone Note: Assign CSSs to devices (phones/lines), gateways, translation patterns, etc.

  22. Time Schedules and Time Periods

  23. Time-of-Day Routing Overview • Time and date information can be applied to partitions. • CSSs that include such a partition only have access to the partition if the current date and time match the time and date information applied to the partition. • Allows different routing based on time • Identical route pattern is put into multiple partitions. • At least one partition has time information applied. • If this partition is listed first in CSSs, it will take precedence over other partition during the time applied to the partition. • If time does not match, second partition of CSS is used(first one is ignored due to invalid time).

  24. Time-of-Day Routing Applications Allow international calls only during office hours (based on the time zone of the caller) Block international calls on holidays Other applications in which you want to control the calling search space based on the time of day: Least cost routing: Multiple providers for international calls Different prices per hours of the day Time-of-day routing allows dialing different providers for same destination (country) based on time

  25. Time Periods and Time Schedules Time period Time range defined by start and end time Repetition interval—Days of the week or specified calendar date Associated with time schedules Time schedule Group of time periods Assigned to partitions Determines the partitions that calling devices search when they are attempting to complete a call during a particular time of day Repetition Time Periods Start–End weekdayhrs_TP 0800–1700 M – F weekendhrs_TP 0800–1700 Sat –Sun newyears_TP 0000–2400 January 1 noofficehours_TP Sat – Sun Time Periods Time Schedule weekdayhrs_TP RegEmployees_TS Partition Time Schedule RegEmployees_TS CiscoAustin_PT

  26. Example: Block International Calls During Weekends and on January 1 First Partition (Weekend) is ignored because no time match. Pattern not blocked. Dials 9.0114369918900009 Current Time: 10:00Current Day: Wed 1 First Partition (Weekend) is active, matched, and listed first. Pattern blocked. CSS: Weekend Standard Dials 9.0114369918900009 Current Time: 20:00Current Day: Sat 2 Route Pattern: 9.011! Partition: Weekend Block This Pattern! Partition Weekend: Time Schedule: TS1 Time Schedule TS1: Time Period: TP1, TP2 TP1: 00:00–24:00 Sat-Sun TP2: 00:00–24:00 Jan 1 Route Pattern: 9.011! Partition: Standard Route to PSTN Partition Standard: (no time schedule)

  27. Time-of-Day Routing Configuration Procedure • Create time periods. • Create time schedules. • Assign time schedules to partitions.

  28. Creating Time Periods TP1 is active Saturday and Sunday from 00:00 to 24:00 TP2 is active Jan 1 from 0:00 to 24:00 TP2 is active Jan 1 from 00:00 to 24:00

  29. Creating Time Schedules Add or remove highlighted time period to or from time schedule

  30. Assigning Time Schedules to Partition Assign time schedule to partition Set fixed time zone or use time zone of call originating device Partition is only active in CSS if call is placed during time specified in time schedule.

  31. Client Matter Codes and Forced Authorization Codes

  32. Client Matter Codes and Forced Authorization Codes CMC: Forces the user to enter any configured CMC Allows for billing and tracking of calls made per client FAC: Forces the user to enter aconfigured authorization code with ahigh-enough authorization level Prevents unauthorized user from making toll calls Can be combined with time-of-day routing (e.g., international calls outside business hours require FAC) Both generate Call Detail Records

  33. CMC Call: Successful Call Play Tone 912125551212 Extend Call to Gateway 1234# (Code) • Dial number that goes to CMC-enabled route pattern • Unified CM tells phone to play tone to prompt for CMC • User enters valid code number • Call extended • Generate CDR for billing CMC: 123412443489 User A Voice GW

  34. CMC Call: Call Failure Play Tone Play Reorder Tone 912125551212 5555# (Code) • Dial number that goes to a CMC-enabled route pattern • Unified CM tells phone to play tone to prompt for CMC • User enters invalid CMC number • User receives reorder tone • Generate CDR to log attempt CMC: 123412443489 User A Voice GW

  35. FAC Call: Successful Call Play Tone 912125551212 Extend Call to Gateway 1888# (FAC Code) • Dial number that goes to an FAC-enabled route pattern • Unified CM tells phone to play tone • User enters authorization code • Code is known and authorization level is not lower than required level configured at route pattern • Call extended • Generate CDR FAC: 1234: Level 11244: Level 21888: Level 7 User A Voice

  36. FAC Call: Call Failure Play Tone Play Reorder Tone 912125551212 1234# (FAC Code) • Dial number that goes to an FAC-enabled route pattern • Unified CM tells phone to play tone • User enters authorization code • Code is not known or its authorization level is lower than the one configured at the route pattern • User receives reorder tone • Generate CDR to log attempt FAC: 1234: Level 11244: Level 21888: Level 7 User A Voice

  37. Calling Privileges Applications Overview

  38. Different Ways Of Using Calling Privileges Configuration Tools • Partitions and CSS are primarily used to implement class of service. • Primariliy used to implement class of service when you must to permit or deny access to a certain number • International versus long distance versus local • Direct access to managers versus going through assistant • Can include time of day or require an authorization code • Configuration tools can also be used for applications such as these. • Vanity numbers: depending on who is calling a number, the call is routed differently • Time of day-based path selection: depending on time a number is called, call is routed differently • Private line, automatic ringdown (PLAR): automatically dial one specific number when phone goes off-hook

  39. Calling Privileges Application Examples

  40. Implementing Class of Service

  41. Class of Service Collection of calling permissions assigned to individual users. Class of Service 1 Class of Service 2 Lobby Employee Executive Emergency Local PSTN Long Distance International Employee

  42. Implementing CoS: Traditional Approach Place external route patterns in partitions associated with the destinations that they can call Configure each calling search space to be able to reach only the partitions associated with its call restriction policy Assign these calling search spaces to the phones by configuring them on the Unified CM device pages (all lines on the device automatically receive the same CoS)

  43. Traditional Approach – Example: Single Site Calling Search Spaces RouteLists RouteGroups Partitions Devices Calling Search Space assigned to device based on class of service Internal_pt All IP Phones Internal_css 911 Route Patterns 9.911 Local_pt Local_css 9.[2-9]XXXXXX PSTN PSTN RL PSTN RG LD_pt LD_css 9.1[2-9]XX [2-9]XX XXX Intl.pt 9.011! Intl_css 9.011#

  44. Traditional Approach – Example: Multiple Sites Calling Search Spaces Route Lists/Route Groups Partitions On Cluster IP Phones Site1Internal Shared VM ports, MeetMe… Site1Local Site1Emergency Device Calling Search Spaces (4 for site 1) 9.11 Site1National 9.911 1RL 1RG Site Local Local_pt 9.1[2-9]XXXXXX Site1International Site1National Local_pt 9.1 [2-9]XX [2-9]XX XXXX Site1International 9.011! SiteNInternal 9.011!# Site 1 Gateways SiteNEmergency SiteNLocal 9.11 Device Calling Search Spaces (4 for site N) 9.911 NRL NRG SiteNLocal SiteNNational Local_pt 9.[2-9]XXXXXX SiteNNational SiteNInternational 9.1 [2-9]XX [2-9]XX XXXX Local_pt SiteNInternational 9.011! Site N Gateways 9.011!#

  45. Line Device Approach: Improves Scalability Significantly decreases the total number of partitions and CSS required. Use the device calling search space to provide call routing information (for example, which gateway to select for all PSTN calls). Use the line calling search space to provide class of service information (for example, which of the PSTN calls to block).

  46. Line Device Approach – Concept Device CSS contains only one partition with route patterns to all PSTN numbers using a specific PSTN gateway. For each PSTN gateway, route patterns exist once in a different partition. Line CSS contains a partition with a single route pattern that matches international numbers and has been configured as a blocked pattern. Regardless of the used gateway, this same partition can be used to block international calls. “Blocked” Route/Translation Patterns Line CSS Line CSSselectively blocksundesired routes(according toclass of service) Block Int’l Partition Resulting CSS 9.011! Block Int’l Partition Line 9.011! PSTN Partition Device CSS 9.[2-9]XXXXXX PSTN Partition 9.1 [2-9]XX [2-9]XX XXXX Device CSSallows access toall external routes 9.011! 9.[2-9]XXXXXX 9.1 [2-9]XX [2-9]XX XXXX “Routed” Route Patterns Device 9.011!

  47. Line Device Approach – Example: Multiple Sites Calling SearchSpaces RouteGroups RouteLists Partitions BlockLocalPSTN Internal OnCluster 9.[2-9]XXXXXX IP Phones Local BlockNationalPSTN Shared 9.1 [2-9]XX [2-9]XX XXXX VM Ports, MeetMe… Line CSS (4 Global) BlockIntlPSTN 9.011! PSTN Partition National Site1Devices Device CSS (1 for site 1) 9.11 9.011!# 9.911 International NoBlock 1 RL 9.[2-9]XXXXXX 1 RG 9.1 [2-9]XX [2-9]XX XXXX 9.911! Empty 9.011!# Site 1Gateways SiteNPSTN 9.11 SiteNDevices Device CSS (1 for site N) 9.911 N RL 9.[2-9]XXXXXX N RG 9.1 [2-9]XX [2-9]XX XXXX 9.911! 9.011!# Site NGateways

  48. Implementing 911 and Vanity Numbers

  49. 911 Emergency Number 911 is a single number to call for medical, fire, and police emergencies, legislated in Canada and United States: Calls to 911 are routed to a PSAP. The PSAP is the first-tier triage call center for emergency calls. 911 calls must always be sent to the local PSAP . Calls to the same number must be routed differently per phone (location).

  50. Vanity Numbers Vanity numbers provide a certain local service Same number regardless of your physical location Examples: Dial 7999 at any site to get local IT support (on-net) Dial 7998 at any site to get local travel agency (off-net) Number can be a route pattern, directory number, or hunt pilot 911 emergency dialing has the same basic concept Dial 911 at any site to get to local emergency services (off-net, emergency call)

More Related