Table Of Contents
Using Provisioning Flows and Templates
Using Provisioning Flows
Customizing Provisioning Flows
Creating Provisioning Flows
Using Templates
Creating EPOM Templates
Using Existing Templates to Create New Templates
Editing EPOM Templates
Setting Default EPOM Templates
Deleting EPOM Templates
Applying EPOM Templates
Using Provisioning Flows and Templates
Using Provisioning Flows
Provisioning Flows guide you through multistep tasks. Information is carried over from one step to the next. EPOM provides wizards for these common provisioning tasks:
•
Provisioning announcements
•
Provisioning call agents
•
Adding subscribers
•
Deleting subscribers
•
Deleting residential media gateways
•
Diagnosing media gateways
•
Provisioning Centrex groups
•
Provisioning Centrex subscribers
•
Provisioning multiline hunt groups
•
Provisioning multiline hunt group subscribers
•
Provisioning SS7 trunk groups
•
Provisioning H323 trunk groups
•
Provisioning basic SS7 routing
•
Provisioning advanced SS7 routing
•
Provisioning ISDN trunk groups
•
Provisioning softswitch trunk groups
•
Provisioning 911 (CAS) trunk groups
Step 1
From a Domain window, click domain.
Step 2
Click BTS10200s.
Step 3
Click EMS server.
Step 4
Click Config.
The BTS 10200 Component Status window opens.
Step 5
In the Configuration tree, click Provisioning Flows; then, click the appropriate provisioning wizard.
The BTS Configuration Wizard opens showing the list of provisioning tasks for this flow.
Step 6
Click the first task.
The form for the selected task opens.
Step 7
Fill in the form; then, click OK.
Alternatively, if this task is not required or you are not ready to complete it now, click Skip. The form for the next task opens.
Step 8
Repeat step 5 for the remaining tasks.
Customizing Provisioning Flows
EPOM allows you to define new provisioning flows (consisting of the tasks necessary to achieve them) and to add them. The following example shows the process of creating a new provisioning flow called MTA Diag.
Note
EPOM sees the media termination adapter (MTA) as a media gateway (MGW).
The tasks achieved by this provisioning flow are:
•
Placing the MGW into a maintenance state
•
Diagnosing the MGW
•
Restoring the MGW to service
Note
In this example, the filename that is used is mgw_diagnose.xml. It is located in this directory: /opt/CSCOepom/tomcat/webapps/ROOT/xml/bts/wizard/.
<step_name="Control MGW MAINT"
url="btscompcontrol.jsp?_noun=mgw"
help_mssg="Control the mgw into MAINT state"
<parameter name="mgwId" sourceName="id"/>
<parameter name="mode" sourceName="FIXED" value="FORCED"/>
<parameter name="target_state" sourceName="FIXED" value="MAINT"/>
<step_name="Diagnose MGW"
url="btscompdiag.jsp?_noun=mgw"
help_mssg="When done with diagnosis, click the skip button, I really should not
carry you away from this page"
<parameter name="mgwId" sourceName="id"/>
<parameter name="id" sourceName="mgwId/">
<parameter name="test" sourceName="FIXED" value="3"/>
<step_name="Control MGW INS"
url="btscompcontrol.jsp?_noun=mgw"
help_mssg="Control the mgw into INS state"
<parameter name="mgwId" sourceName="id"/>
<parameter name="mode" sourceName="mgwId/">
<parameter name="mode" sourceName="FIXED" value="INS"/>
<parameter name="mgwId" sourceName="id"/>
Where,
•
step_name—The name of the task displayed in the right pane when you click on the MTA Diag provisioning flow item in the left pane.
•
url—The jsp page name from the URL, followed by the component name.
•
help_mssg—Reserved for future use.
•
img—The example uses the default icon, but you can define your own icon for each step.
•
provideParameterList—Items within this tag record user input for this step after the page appears and the user clicks Ok. You can use the parameters that are used here in subsequent steps.
–
name—The parameter name used by the page.
–
sourceName—When this is FIXED, the value that follows is used. Otherwise, you can use parameter names that are defined under the provideParameterList tag in previous steps.
•
takeParameterList—Items within this tag accept parameters passed from previous steps.
–
name—The parameter name used by the page.
–
sourceName—When this is FIXED, the value that follows is used. Otherwise, you can use parameter names that are defined under the provideParameterList tag in previous steps.
Creating Provisioning Flows
In this task, the filename used is mgw_diagnose.
Step 1
Create the mgw_diagnose.xml file.
Step 2
Place the mgw_diagnose.xml file in /opt/CSCOepom/tomcat/webapps/ROOT/xml/bts/wizard.
Step 3
Make a backup copy of the defaulttree.xml file located at /opt/CSCOepom/tomcat/webapps/ROOT/xml/bts/navigation/defaulttree.xml.
Step 4
Modify the defaulttree.xml by adding these commands to the file:
<node name="MTA Diagnose">
<url base="btswizard">mgw_diagnose</url>
Note
The location of this code in the .xml file defines the structure of the navigation tree. Make sure that you add it to the correct "branch."
Step 5
Stop and start EPOM..
Step 6
Verify that MTA Diag is added to the Provisioning Flow list by choosing Domain > all > BTS10200 > Summary > Provisioning Flow.
Using Templates
Use EPOM templates to createand save templates for creating BTS objects.
Templates are stored on the EPOM server by BTS noun and template name.
Templates can be created, viewed, and applied by all levels of EPOM users. Administrators can edit and delete all existing templates, whereas Users can edit and delete only the templates that they created.
Creating EPOM Templates
Step 1
In a Domain view, select domain > BTS10200s > EMS server
Step 2
Click on Config.
The BTS Component Status view opens.
Step 3
In the Configuration tree, select Office Tables > Call_agent.
The BTS Component view opens showing a list of call agents.
Step 4
Select a call agent and click Details.
Step 5
Enter information in the fields. ID is unique to each device. You can either specify a value to be used as a prefix, or leave a blank field that forces the user to specify a valid, unique ID.
Step 6
Enter a name for the template and click on Save.
The created template contains field information from the Details Component window.
Using Existing Templates to Create New Templates
Step 1
In a Domain view, select domain > BTS10200s > EMS server.
Step 2
Click Config.
The BTS Component Status view opens.
Step 3
In the Configuration tree, select Template Manager > Templates.
A list of templates appears.
Step 4
Select a template and click Details.
Step 5
Enter information in the fields. ID is unique to each device. You can either specify a value to be used as a prefix, or leave a blank field that forces the user to specify a valid, unique ID.
Step 6
Enter a new template name.
Step 7
Click Save.
The new template is stored under the specified name.
Editing EPOM Templates
Step 1
In a Domain view, select domain > BTS10200s > EMS server.
Step 2
Click Config.
The BTS Component Status view opens.
Step 3
In the Configuration tree, select Template Manager > Templates.
A list of templates appears.
Step 4
Select a noun and template and click Edit.
The Edit Template window appears.
If necessary, make changes to the information in the fields and click OK to save changes.
Setting Default EPOM Templates
One template for each device type can be identified as the default template. When you add a device, the default template automatically loads. If necessary, you can select a different template for this device.
Step 1
In a Domain view, select domain > BTS10200s > EMS server.
Step 2
Click Config.
The BTS Component Status view opens.
Step 3
In the Configuration tree, select Template Manager > Templates.
A list of templates appears.
Step 4
Select a noun and template and click Edit.
The Edit Template window appears
Step 5
Select the Default template checkbox.
Step 6
Click OK to save changes.
Deleting EPOM Templates
When you delete an EPOM template you also delete all the data it contains.
Step 1
In a Domain view, select domain > BTS10200s > EMS server.
Step 2
Click Config.
The BTS Component Status view opens.
Step 3
In the Configuration tree, select Template Manager > Templates.
A list of templates appears.
Step 4
Select a noun and template and click Delete.
Applying EPOM Templates
Templates are applied only when creating an object (during an Add operation).
Step 1
In a Domain view, select domain > BTS10200s > EMS server.
Step 2
Click Config.
The BTS Component Status view opens
Step 3
In the Configuration tree, select Office Tables > dial_plan.
The BTS Component view opens showing a list of dial plans.If this is the first dial plan (or device of this type) that you are adding, the list is empty
Step 4
Click Add.
The BTS Component Add view opens.
Step 5
Select a template from the list.
Step 6
Click Load.
Click OK or Apply.
•
When you click OK, the component is added and the list of components in the Component name window appears.
•
When you click Apply, the component is added, but you remain in the Add component window for further operations