Preyarn Report
- Mats Age
- Zane England
This document provide infomation as to why data is collected and to help analyse the results
Quick View Report Item | Quick View | Quick View Detailed | Excel Tab | Excel Report Content |
|---|---|---|---|---|
Server Info | This contains the following CUCM Version | N/A | Summary | List of: CUCM Version Recommended number of VM’s/ OVA for cluster, current and with +20% growth This is not Any configured syslog and CDR feeds Roadmap: we are going to also add SNMP information here and highlight that SNMP is not supported with WxC-DI Current Licenses consumed PSTN Break Out Codes CBO/ LBO Number of Country Dial Plans Loaded and used (Countries with lines) Summary Counters of objects analysed Users |
Services By Host | This shows all services/ CUCM hosts, status and how long they have been running. These are useful to know what node is what and how many nodes there are Status 1 - Active Status 2 - Inactive
| N/A | CUCM | This shows all services/ CUCM hosts, status and how long they have been running. These are useful to know what node is what and how many nodes there are Status 1 - Active Status 2 - Inactive |
Cluster Architecture Recommendations | Recommended number of VM’s/ OVA for cluster current and +20% growth  Note that this is not relevant for migration to WxC-DI | N/A | Summary | See Above |
Licenses | Licenses, this section is what CUCM reports as the licenses – NOTE that this may be different to PLM in HCS as the output is from CUCM  | N/A | Summary | See Above |
Output Destinations | These are any configured syslog and CDR feeds Roadmap: we are going to also add SNMP information here and highlight that SNMP is not supported with WxC-DI | N/A | Summary | See Above |
Dial Plan | This information includes any country dial plans loaded, noting that NANP is loaded by default, DN’s by country and summary counters of dial plan objects in the system. Intent of this is to get a view of dial plan complexity
| N/A | Dial Plan | This information includes any country dial plans loaded, noting that NANP is loaded by default, DN’s by country and summary counters of dial plan objects in the system. Intent of this is to get a view of dial plan complexity |
|
|
| Number Ranges | List of Number ranges These are auto generated from the DN and e164 per site (Device Pool). The ranges are created in 10/100/1000 blocks when there are contiguous numbers or there are no numbers in the block in another sites. If the external number mask is in FNN format, pre_yarn will try to convert and validate to e164 - this is why the country must be selected when starting – you can specify multiple countries by device pool |
Telephony Summary | This is an interpretation for how the source system would be represented in flex (licensing) Roadmap: update terminology to match current flex3.0 | N/A | Telephony Summary | This is an interpretation for how the source system would be represented in flex (licensing) Roadmap: update terminology to match current flex3.0 |
External Directory Usage | Summary counters for: | Show All Phone Services Phone Services, used for services such as EM and may indicate presence of 3rd party apps like paging etc Show All LDAP Directories Displays all LDAP sync agreements for user synchronization with external directory such as AD Show All UC Services UC Services as used by Jabber Show All UC Service Profiles UC Service Profiles as used by Jabber
| External Directory Usage | Summary counters for:
|
Configured CMC | Client Matter Codes. These are digits entered during or after a call, recorded in CDR and used for accounting purposes or such - supported in WxC DI but not WxC MT
| N/A | Configured CMC | List of configured CMC, Client Matter Codes. These are digits entered during or after a call by the users, recorded in CDR and used for accounting purposes or such - supported in WxC DI but not WxC MT |
Configured FAC | Forced Access Codes. These are Authority Codes generally used to grant user access to dial number that otherwise their Class Of Service would prevent. This feature is supported in WxC DI and WxC MT
| N/A | Configured FAC | Forced Access Codes. These are Authority Codes generally used to grant user access to dial number that otherwise their Class Of Service would prevent. This feature is supported in WxC DI and WxC MT |
CAC Complexity | Counter for Location BW and RSVP settings. For more details on this, look in Quick View Detail or Excel Report
| Show CAC Complexity This is the location matrix info defining any Bandwidth limitations and RSVP settings between the configured locations. Maybe not being used that much anymore due to BW not being constrained
| CAC Complexity | This is the location matrix info defining any Bandwidth limitations between the configured locations. Maybe not being used that much anymore due to BW not being constrained Roadmap: We are looking having a way to simplify and/or overlay video easily when doing wrangler_ migrations |
Users | Counter of users and User by site
| Show All Users Overview of users including if LDAP synced or Local Number of Users by Site Users listed with Username, mailid, site, Home Cluster, Local or LDAP, Number of Lines associated with user
| Users | Overview of users including if LDAP synced or Local Number of Users by Site Users listed with Username, mailid, site, Home Cluster, Local or LDAP, Number of Lines associated with user Roadmap: add device and EM profile count to this |
Application Users | Counter of Application Users | Show all Application users List of all application users with associated ACG’s and Roles Useful to identify if there are any obviously named accounts for 3rd parties as there may be no way of detecting other than the account
| Application Users | List of Application Users with associated Access Control Groups and Roles These are here to check if there are any obviously named accounts for 3rd parties as there may be no way of detecting other than the account |
Devices | Counters of Total number of devices configured Active (Registered) devices Inactive (Unregistered/ Unknown status) devices | Show All Devices Detailed device break downs inc;uding Device Name, Description, Type of Device, Status, Location, Site (Device Pool), User owner, Firmware defined, Active (Registered), Lines
| Devices | Device break downs – this is to know what models are in use and grouping by DP/LOC which can be useful depending on what the source configuration is. It also provides an overview of the phones resistration and IP address Roadmap: we are going to add the EM enabled field |
Devices by Type | Displays the type of devices with counters for each
| As per 'Show All Devices' | Phones* | This is an overview with additional information to the devices using information from the phone web browser provided this is enabled for the device in CUCM. Information collected includes Serial Number and UDI HW rev to work out MPP compatibility of the device – it will also give details for any phone it couldn’t reach |
Devices by Location | Displays view of device count/ location
| As per 'Show All Devices' |
|
|
Devices by Site | Displays view of device count/ site (Device Pool)
| As per 'Show All Devices' |
|
|
Devices by Status | Displays device count by status - Unknown, Registered, Unknown | As per 'Show All Devices' |
|
|
Phones with non-default Firmwares | Lists phones that do NOT have default firmware loaded and the firmware loaded on phone/s in question
| As per 'Show All Devices' | Phone Firmwares
| Lists phones that do NOT have default firmware loaded. This is important to know as there may be a special reason for this that needs to be taken in to account for migrations |
Product Alerts | Lists EOS/EOL per phone device type
| N/A | Product Alerts | List of End of Sale/ SW Maintenance/ Support for existing phone devices. This is important to understand if all models supported in target system or if there is a requirement to replace some |
Lines | Displays Couter for number of Lines (DN’s) and Multi Lines Expands to show all multi lines | Shows Quick View detailed of all lines (DN’s) in CUCM and associated Devices
| Lines | Lines gives an overview of MLA and then lines by device pool where possible (not EM) and the devices associated with the lines |
Line Groups
| Summary Counter for line Groups and number of lines in Groups
| Lists all Line Groups with Counters of member Lines
| Line Groups | List of line groups in the system and number of associated lines |
Pickup Groups
| Counter of Pickup Groups
| View of Pickup Groups configuration with counter of lines included in each
| Pickup Groups | List of Pickup groups configured together with |
Gateways | View of Gateways - counter for total number of GW’s and Expanded view of Gateways by Type and Protocol
| Detailed Quick View of Gateways gives an overview of what is out there, information includes types of gateways and protocol used for each, Modules and Subunits configured and devices configured in the gateways
| Gateways | List of Gateways gives an overview of what is out there> information includes types of gateways and protocol used for each, Modules and Subunits configured and devices configured in the gateways Descriptions may get an idea of any 3rd party integrations for the GW devices Roadmap: again we are planning on adding in more details about IOS version and maybe some config extracts |
Time Schedules | Counter for number of Time Schedules in CUCM
| Time Schedules are there to see if there is any special time based routing - can be complex
| Time Schedules | Time Schedules are there to see if there is any special time base routing - can be very complex |
Media Services | Counter for number of Media Services
| List of Media Services configured in the CUCM source. This includes Conference Bridges, MTP’s, Transcoders, Annunciator and Music On Hold Servers
| Media Services | List of Media Services configured in the CUCM source. This includes Conference Bridges, MTP’s, Transcoders, Annunciator and Music On Hold Servers |
EM Profiles | Counter for Number of EM profiles
Expand for number of EM profiles/ Phone Device Type
| Displays EM Profiles log in status
| EM Profiles | EM profiles give a count of what profiles are in use and which ones are logged in
Roadmap: we are planning on adding more to this to detect EM profiles that are logged into other sites than where the associated user/ device belongs |
Remote Destination Profiles | Counter for Remote Destination Profiles configured in CUCM
| N/A | N/A |
|
MOH Audio Sources | Number of MOH Audio Sources configured
| Shows all MOH Audio Sources including audio file name, Source ID for stream and if Multicast or Unicast
| MOH Audio Sources | List of MOH Audio Sources gives an overview of these and respective Source ID’s |
SIP Tunks | Counters for SIP Trunks, Active SIP Trunks and Inactive SIP Trunks
| View of all SIP Trunks in CUCM, including Site, Status
| SIP Trunks | List of SIP Trunks/ site which gives an overview of what is being used including registration status and the name can be useful to help work out if these are used for some 3rd parties |
SIP Trunks by Site | Number of SIP Trunks by Site
| As Above |
|
|
SIP Route Patterns | Counter for SIP Route Patterns
| CDR Site Traffic** | SIP Route Patterns | List of SIP Route Patterns giving an indication of any B2B dialling or other URI dialling settings |
Hunt Pilots | Number Of Hunt Pilots configured in CUCM
| All configured Hunt Pilots shown including if Queuing is used
| Hunt Pilots | List of Hunt Pilots with DN, Description and if Queuing is configured / pilot which may increase complexity
|
CTI Route Points | Number of CTI Route Poiints configured in CUCM
| List of CTI Route Points configured. This is to detect any third party CTI applications integrated or perhaps call forwarding settings as CTIRP is the only device in CUCM that doesn’t count to license total
| CTI Route Points | List of CTI Route Points configured. This is to detect any third party CTI applications integrated or perhaps call forwarding settings as CTIRP is the only device in CUCM that doesn’t count to license total |
|
|
| CDR Trunk Traffic** | This give the call counts, duration and erlang calc for each trunk for each hour when there was traffic – This data can be used for trend analysis graphs and network NNI requirement/SIP channels |
|
|
| CDR line traffic** | lists the number of calls for each line – we plan on adding the linked device to this |
|
|
| CDR Lines Without Traffic** | Lines without traffic report identifies any lines that didn’t have any calls during the analysis period – again want to add linked devices to this as these lines/devices may not be in use and can be pruned from migration |
|
|
| CDR Sites and Trunks Traffic** | This report give the call counts and erlang for each trunk from each site – can be useful for working out network NNI requirement/SIP channels |
|
|
| CDR Site Traffic** | Gives the call counts and erlang for inter-site traffic. Not so much used anymore due to BW not being restrained |
*Requires Phone device to have Web interface enabled in CUCM.
** Require that CDR is downloaded to location that can be accessed by the PC/Server where the pre_yarn application is run from. Max period for report is 90 days