HowTo: Support FMU Private and Corporate modes on the SOP.
Introduction
This document contains the preferred method of implementation for the Private and Corporate modes of FMU within the SOP. It works with any versions of UC.
How to implement ?
Import the callflow
Navigate to: Communication Flow Studio > Callflows
Import the following callflow:
Create variables
Navigate to: Communication Flow Studio > Global Parameters
Select parameters of type "STRING"
Add the new parameter:
- FMU Logger Service Number
- Parameter Name: FMULoggerServiceNumber
- Friendly Name: FMULoggerServiceNumber
- Value: < empty >
Select parameters of type "INTERFACE"
Add the new parameters:
- FMU Trunk 1 for the service
- Parameter Name: FMULoggerSIPTrunk1
- Friendly Name: FMULoggerSIPTrunk1
- Value: < empty >
- FMU Trunk 2 for the service
- Parameter Name: FMULoggerSIPTrunk2
- Friendly Name: FMULoggerSIPTrunk2
- Value: < empty >
Create a new Profile
Navigate to: Communication Flow Studio > Profiles
- Profile Name: FMULogger
- Type: STATIC
- Parameter 1: FMULoggerServiceNumber
- Parameter 2: FMULoggerSIPTrunk1
- Parameter 3: FMULoggerSIPTrunk2
Press save
Assign the callflow to the profile
Navigate to: Communication Flow Studio > Callflow assignment
click on add and fill in the following fields:
- Application Selector : STARTDYNAMICAPPLICATION
- Profile : FMULogger
- Status : Service
- CallFlow Root : *025
Press save
Create the extensions
Navigate to: Directory > Internal directory
Click on add and fill in the following fields:
- Extension : 5001
- First Name : FMU Private Mode
- Last Name : service
- Visibility: Hidden
- CallFlow : FMULogger.service
Press save
Click on add and fill in the following fields:
- Extension : 5002
- First Name : FMU Corporate Mode
- Last Name : service
- Visibility: Hidden
- CallFlow : FMULogger.service
Press save
Set the profile parameters with the following values:
- for Private Mode:
- Service Number : #5001
- SIP Trunk1 : >> must contain the FMU Trunk's SOA 1 <<
- SIP Trunk1 : >> must contain the FMU Trunk's SOA 2 <<
- for Corporate Mode:
- Service Number : #5002
- SIP Trunk1 : >> must contain the FMU Trunk's SOA 1 <<
- SIP Trunk1 : >> must contain the FMU Trunk's SOA 2 <<
Inbound number mapping
Navigate to: Communication Routing > Incoming Number Mapping
Add a mapping for your DDI and the Extensions.
- External Number: < DDI For the service on the PABX >
- Internal Extension : 5001
Add a mapping for your DDI and the Extensions.
- External Number: < DDI For the service on the PABX >
- Internal Extension : 5001
Push the configuration
Navigate to: Apply changes > Apply changes
Requirements
- The number format of the CLI for the Cell Phone must always come in +E.164 format (ie: +32477123456) - This can be changed on request or through edition of the callflow itself.
- This procedure only works with FMU Template v10+