This guide outlines how to create a word merge template, the use of tokens and the context each should be used in.
...
The location of the templates is typically c:\inetpub\UCentricNodeUCentricServer\merge_templates and an example _Default_Template.docx is provided to give you examples.
...
| 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 | ||||
|---|---|---|---|---|
|
...
| Anchor | ||||
|---|---|---|---|---|
|
Mitel Phones
This is used only when migrating to hosted Mitel solutions.
phones that are not supported
phones with revision numbers that will require an extra step when first connect to MiCloud Connect
phones with more buttons programmed than what is supported by MiCloud Connect
Location | Name | Model | DN | IP | MAC |
{#miccunsup} {rname} | {name} | {detail} | {circuitid} | {IP_Address} | {MAC} {/miccunsup} |
RingCentral
Location | Name | Model | DN | IP | MAC |
{#rcunsup} {rname} | {name} | {detail} | {circuitid} | {IP_Address} | {MAC} {/rcunsup} |
| 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 | ||||
|---|---|---|---|---|
|
...
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 |
| 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} |
...
| Anchor | ||||
|---|---|---|---|---|
|
{chartcabs}
Note: Scaling may be required after the document is generated.
...