This guide outlines how to create a word merge template, the use of tokens and the context each should be used in.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The system type is ‘{platformType}’ running on ‘{platformName}’
There are {total_mg}nodes in this configuration.
...
Category | Count | Information |
Cards full | {cardsfull} | Cards that are 100% utilised |
Cards almost full | {cardsnearlyfull} | Cards that are >90% utilised |
License status | (See licensing section) | {license_alert} |
{#migsumm}{title} | {count} | {detail} {/migsumm} |
...
| Analog | Digital | IP | Cisco | Broadsoft | Skype | ||||||||||||
Counts | Ana | Dig | IP | Ana | Dig | IP | Ana | Dig | IP | |||||||||
{#migrationbyloc} {Region_Name} | {Total_analog} | {Total_digital} | {Total_IP} | {ciscoAnalogIcon} | {ciscoDigitalIcon} | {ciscoIPIcon} | {broadsoftAnalogIcon} | {broadsoftDigitalIcon} | {broadsoftIPIcon} | {skypeAnalogIcon} | {skypeDigitalIcon} | {skypeIPIcon} {/migrationbyloc} | ||||||
...
Migration Features Graphs
{chartcccisco} -> CISCO
{chartccbroadsoft} - > RING CENTRAL
{chartccteams} - > TEAMS
{chartccbroadsoft%} - > BROADSOFT
{chartccrc} - > RINGCENTRAL
{chartcceight} - > 8x8
| Anchor | ||||
|---|---|---|---|---|
|
...
Digit | Digits to follow | Group # | COR | Route Type | Trunk Type | Description | Absorb | Insert | Final | Group type |
{#ars} {digit}{following} | {digitstofollow} | {trunkgroup} | {cor} | {routetype} | {type} | {description} | {abs} | {ins} | {ft} | {grouptype}{/ars} |
Or
Digit | Digits to follow | Route Termination Type | 1st | 2nd | 3rd | Absorb | Insert |
{#ars2} {digit}{following} | {digitstofollow} | {rid} | {c1} | {c2} | {c3} | {abs} | {ins}{/ars2} |
List all Routes (in use or not)
Digit | Route Type | Trunk Group Type | Absorb | Insert | Final Tone/Marker |
{#ars3} {rn} | {routetype} | {tt} | {abs} | {ins} | {ft}{/ars3} |
List all Plans
| Route Plan Number | Day and Time Zone # | Day Zone | Zone 1 Term Type | Zone 2 Term Type | Zone 3 Term Type | Zone 4 Term Type | ||||||
{#ars4} {rid} | {rpn} | {dtz} | {dz} | {z1type} {z1term} | {z2type} {z2term} | {z3type} {z3term} | {z4type} {z4term} {/ars4} |
...
Route Number | Routing Medium | Trunk group number | Description / SIP Peer Profile Label | Trunk Type | Route Type |
{#ars5} {rn} | {type} | {trunkgroup} | {description} | {grouptype} | {routetype} {/ars5} |
MiVB:
You can also add:-
{rt} to show the route number if required
...
Shows all feature codes (e.g. “Make Busy”, “DND” etc.) – Note the orange entries apply to some vendors only (e.g. MiVO 250)
Feature name | Code | Admins Only | Directory Entry | Engineering Only |
{#codes} {featurename} | {code} | {adminonly} | {direntry} | {engonly}{/codes} |
I
| Anchor | ||||
|---|---|---|---|---|
|
...
LIM | Type | Analog Extns | Digital Extns | Operator Extns | Total for LIM |
{#sapsec}{lim} | {type} | {analogextns} | {digitalextns} | {oprextns} | {total}{/sapsec} |
Totals: | {saptotalanalog} | {saptotaldigital} | {saptotaloperator} |
| Anchor | ||||
|---|---|---|---|---|
|
...
PLID | Name | Detail | Number | Part number | Revision | Firmware |
{#comparison} {plid} | {nameimg} {name} {oldName} | {detailimg} {detail} {oldDetail} | {circuitidimg} {circuitid} {oldCircuitid} | {partnumberimg} {partnumber} {oldPartnumber} | {revisionimg} {revision} {oldRevision} | {firmwareimg} {firmware} {oldFirmware} {/comparison} |
| Anchor | ||||
|---|---|---|---|---|
|
...
Name | Current IP | IPS IP |
{#serverinfo} {platform_name} | {current_ip}
| {ips_ip} {/serverinfo} |
...
Call Usage Tokens
The high-level insights for the usage of the telephone usage of users.
NOTE: This section of the report requires CDR data to allow population.
{total_phones} Total DN's (Directory Numbers) | {total_calls} DN's making calls |
{total_calls_in} DN's receiving incoming calls. | |
{total_calls_out} DN's making outgoing calls |
Zero / Low Usage | Medium Usage | High Usage |
{total_users_zero_calls} users with 0 calls {total_users_less20_calls} with under 20 calls | {total_users_less50_calls} users with under 50 call involvements {total_users_less100_calls} with under 100 call involvements | {total_users_over100_calls} users with over 100 call involvements {total_users_over250_calls} over 250 {total_users_over1000_calls} over 1000 |
Alternative Tokens:
Metric | Count |
Total Extension Directory Numbers (DN’s) | {extns_calls_totalextns} |
Total Calls out for ALL DN’s | {extns_calls_out} |
Total Calls out duration | {extns_durn_in} |
Total Calls in for ALL DN’s | {extns_calls_in} |
Total Calls in duration | {extns_durn_out} |
Total number of extensions with more than 10 calls out | {extns_calls_out_10} |
Total number of extensions with more than 10 calls in | {extns_calls_in_10} |
Total number of extensions with more than 10 calls in or out | {extns_calls_in_out_10} |
Cost of an E3 license for all devices {e3}
Cost of an E5 license for all devices {e5}
Cost of an E3 license for all devices making or receiving >10 calls {e3_over_10}
Cost of an E5 license for all devices making or receiving >10 calls {e5_over_10}
| Anchor | ||||
|---|---|---|---|---|
|
...
Total cost if using E3+Voice based on {extns_calls_in_out_10} extensions in use (based on CDR data):
{e3v}* - {e3insight}
*Based on costs of E3 = {e3cost}, E3+Voice = {e3vcost} and E5 = {e5cost}
| Anchor | ||||
|---|---|---|---|---|
|
This details features that have limited or no support in Teams
Facility | # in Use | Comment |
{#teamsinsights} {facility} | {count} | {info}{/teamsinsights} |
...