5 Get support for your project Executive sponsorship must be appropriate and accountable for the scale of deployment planned. The level and intensity of sponsorship will also change as projects progress from pilot to full deployment.Is the executive sponsorship appropriate and properly accountable for the scale of the next phase of the deployment?Is the anticipated return on investment clear and measurable?Is the sponsoring executive accountable to achieve the ROI and the overall value of the Lync deployment?
7 Voice Routing Dialing Behaviors Routing & Authorization User Initiates CallNormalization RuleDial PlanUser=phoneSIP URIGlobal?Emer. Call?NoNo404: No matching ruleCall Park Orbit RangeYesYesDialing BehaviorsReverse Number LookupRouting & AuthorizationNo matchMatch1. Vacant Number Range2. Call Park Orbit RangePSTN Usage3. Voice PolicyRoutesRoutePSTN UsageLocation PolicyMediation Server and Trunk Configuration403: No route foundAnnouncement or Call Park ApplicationGateway / IP-PBX / SIP TrunkInbound RoutingExternal Endpoint Receives CallUC Endpoint Receives Call7
8 Voice Routing User habits Gateway selection (or not) User Initiates CallNormalization RuleDial PlanUser=phoneSIP URIGlobal?Emer. Call?NoNoUser habits404: No matching ruleCall Park Orbit RangeYesYesDialing BehaviorsReverse Number LookupRouting & AuthorizationNo matchMatchGateway selection (or not)1. Vacant Number Range2. Call Park Orbit RangePSTN Usage3. Voice PolicyRoutesRoutePSTN UsageLocation PolicyMediation Server and Trunk Configuration403: No route foundAnnouncement or Call Park ApplicationGateway / IP-PBX / SIP TrunkInbound RoutingPSTN accommodationsExternal Endpoint Receives CallUC Endpoint Receives Call8
9 Overview with respect to numbering Dial plan converts the presented number to E.164Lync (reverse number lookup) determines if this number is assigned to any Lync user, contact, or applicationLync (outbound routing) selects the appropriate gateway, IP-PBX, or SIP trunk for the called numberThe number is manipulated to present something other than E.164 (if required) to the downstream component
11 Voice Routing User- focused Infrastructure- focused Dialing Behaviors User Initiates CallNormalization RuleDial PlanUser=phoneSIP URIGlobal?Emer. Call?NoNoUser-focused404: No matching ruleCall Park Orbit RangeYesYesDialing BehaviorsReverse Number LookupRouting & AuthorizationNo matchMatch1. Vacant Number Range2. Call Park Orbit RangePSTN Usage3. Voice PolicyRoutesRoutePSTN UsageLocation PolicyInfrastructure-focusedMediation Server and Trunk Configuration403: No route foundAnnouncement or Call Park ApplicationGateway / IP-PBX / SIP TrunkInbound RoutingExternal Endpoint Receives CallUC Endpoint Receives Call11
12 Routing and Authorization, the big picture Voice PoliciesPSTN UsagesRoutesUser authorizationClass of serviceVoice feature setPurpose (usage, caller’s intent)Calling locationPriorityCalled numberCost of call12
13 Voice Policies Can be assigned per user, site, or global Provides admins with flexibility to control user voice entitlementsCall ForwardingDelegationCall TransferCall ParkSimultaneous RingingTeam CallPSTN ReroutingBW Policy OverrideMalicious Call Tracing13
14 Call Forwarding & Simultaneous ringing An administrator can associate a set of PSTN usages to specify this call authorization in a voice policyCall authorization types:Voice policy PSTN usagesRestrict to Lync users onlyCustom set of PSTN usagesThe same call authorization applies to call forwarding and simultaneous ring“Call PSTN Usages”PSTN Usages‘”Local”, “International”Voice Policy“Redmond”Call Forwarding / Simulring Type“Internal Lync users only”“Custom PSTN Usages”“Custom usage”14
15 PSTN UsagesA Public Switched Telephone Network (PSTN) usage record specifies a class of call (such as internal, local, or long distance) that can be made by various users or groups of users in an organization.By themselves, PSTN usage records do not do anything. For them to work, they must be associated with the following:Voice policies, which are assigned to users.Routes, which are assigned to phone numbersVoice PoliciesPSTN UsagesRoutes
16 RoutesA voice route associates destination phone numbers with one or more public switched telephone network (PSTN) gateways or SIP trunks and one or more PSTN usage records.A route is selected based on a matching patternPSTN Usages control if a user is allowed to use the routeRoutes are associated to one or more trunks
17 Controlling gateway preference Multiple trunks in same routeGateway will be selected randomlyUseful when there is no gateway preference and multiple gateways are available for same path to PSTNMultiple routes in the same usageGateway selected based on matching pattern. If multiple routes match, do not rely on route ordering for enforcing preference.Used when difference gateways are used for different called numbers but all belong to the same class of service.Routes in different usagesGateway selected based on the order of the usages in the user’s voice policy.Useful for enforcing primary/secondary relationships between gateways.
24 Trunks, cont’dAllow for centrally managing number formatting prior to routing to PBX/PSTN for both calling and called numberAlice calls ; based on route translation pattern, called number is formatted to when using gateway in RedmondAlice’s number ; based on route translation pattern, calling number is formatted to 5667 when using gateway in Redmond
31 Response Group Administration by Roles Response Group AdministratorConfiguration for all RGS settings and all groups (including creation)Improves RG admin scalability by delegating workflow to managersResponse Group ManagerManages specific Workflow settings for designated groupsCannot manage resources not owned by that manager
34 Unassigned Number Service Call treatment for dialing numbers owned by the enterprise but unassigned to usersAvoid busy tones if callers misdialTransfer to predetermined destinationPhone numberSIP URIVoicAnnouncement Service
37 Call Park- Configuration Call Park Service installed when configured for Enterprise VoiceEnable in user policy (off by default)Configure orbit rangesNumber ranges per poolRange is globally unique, not DIDsDigits must be of uniform length
45 IP Phones Two levels of Qualification for IP phones Optimized- Runs Lync Phone Edition software built and maintained by MicrosoftIntegrated user experience, centralized management, and securityAdvanced incoming call controlsRich conferencing with click to join, roster viewing, and leader controlsProvision the phone with domain credentials to access calendar, Outlook contactsLet you join meetings even when the PC is offOffer Microsoft media platform with RT audioCompatible- Runs partner software tested and qualified by MicrosoftPartner controlled feature sets, form factors, and release schedulesCore capabilities level mandatory for any qualification. No required topology updates. No gateway needed.Extended scenarios qualified as determined by partnerIP PhonesOptimized for Lync or Compatible
46 As the program matures, critical features have been added ~2010-Basic telephony features, username/password sign-in2007 R2 and 2010 qualification2011-Extension/PIN, certificates, branch resiliency mandatoryCall Park, Lync based conferencing, Lync managed upgrade2012-Datacenter resiliencyPC tethering, exchange integrated scenarios (visual VM, one click join, etc)Remaining gaps-QoEQualification ScopeTimelines
47 Compatible IP Phones Form Factors Features Desk phoneProgrammable keysExpansion modulesWireless (WiFi and DECT)Features802.1x authenticationBoss-Admin / Shared line appearanceIntercom and pagingDual registrationMarket supportCustom solutions (Ex- MoH, provisioning)Compatible IP PhonesPartner controlled software == differentiated features
Your consent to our cookies if you continue to use this website.