Configure the VPS

The Virtual Phone Service (VPS) process is supported primarily by one main configuration file: the VPS_service.cfg file. This file has a minimum of five sections including [General], [HLR], [MSC], [CDR], and at least one VPS rule. There is also an optional strip and replace configuration file for the VPS. The sections are explained in more detail here.

VPS Service Configuration
VPS Strip and Replace

VPS Service Configuration

You must configure the VPS_service.cfg file and the VPS_resourcePolicy.cfg file in order for the Virtual Phone Service to function correctly. There are multiple prerequisite configuration steps that need to be taken first, but that is typically completed by Tango Support.

Prerequisites

You must have access and permissions to configure and update both the VPS_service.cfg file and the VPS_resourcePolicy.cfg file.
You must have a MAP.cfg file present on your system.

The VPS contains MAP layer functionality for receiving SRI-SM and MT-FSM requests.
You must have a route.cfg file with a routing definition for the VPS service.
You must have an RM.cfg file containing the configured resource name.

Procedure

Specify the Resource Policy file in the [General] section of the VPS_service.cfg file. The default is VPS_resourcePolicy.cfg.
```
[General]

    Resource Policy File                = /tango/config/VPS_resourcePolicy.cfg
```

Still in the VPS_service.cfg file, configure the remaining resource information in the [General] section:

[General]

    Resource Name                       = VPS           (1)
    Resource Algorithm Id               = 0             (2)
    Resource Scope                      = 0             (3)
    Resource Priority                   = 0             (4)

The name of the resource provided by the VPS.
Specifies the resource algorithm ID of the resource.
Specifies the resource scope (the host or cluster) of resource.
Specifies the resource priority of the resource.

Set the MSC address in the [HLR] section.

[HLR]

    MSC Address                         = +123456789

Configure the [MSC] section of the VPS_service.cfg file.
```
[MSC]

    Number of Instances                 = 50000                 (1)
    SMPP Router Policy                  = SMPP-ADAPTOR          (2)
    SMPP Response Timer                 = 5                     (3)
    Default SMPP Coding is Packed GSM   = yes                   (4)

    SMPP B Number SNR File              = (--- None ---)        (5)
```
1. Defines the number of VPS MSC instances
2. The name of the resource policy name used to identify the SMPP-Router.
3. The timer (seconds) used in awaiting response from the SMPP-Router.
4. Boolean indicating whether SMPP default data coding is 7-bit Packed GSM or ISOLATIN-15 character sets.
  
  yes = 7-bit Packed GSM; no = ISO-LATIN-15
5. Optional property that specifies the name of the configuration file containing strip and replace rules to be applied to the service MSISDN to form the B Number for the SMPP PDU.
Ensure Call Detail Records (CDRs) will be produced by enabling them (Enabled=yes) and specifying the Handler Policy.
```
[CDR]

    Enabled                             = yes
    Handler Policy                      = CDRH-0
```

Define at least one VPS rule.

[VPS Rule0]

    Name                                = Main Rule         (1)
    MSISDN                              = +353861234500     (2)
    IMSI                                = 272011234567890   (3)
    SMPP System ID                      = miep              (4)
    SMPP Command                        = SMPP-DELIVER      (5)
    prefixes                            = 1                 (6)
    prefix0                             = +44               (7)

Name the rule.

The MSISDN prefix that should match the incoming SRI-SM request.

(1) An MSISDN match is successful between the SRI-SM request and the rule if there is an exact match or the MSISDN of the SRI-SM request has more digits but matches what exists in the rule (works as prefix - see MSISDN as prefix for a detailed explanation) (2) The same MSISDN cannot be configured in two or more VPS rules. (3) The number of digits in the MSISDN field of all configured VPS rules must contain the same number of digits with no discrepancies.

The IMSI to be returned by the service in the SRI-SM response and will be present in the subsequent MT Forward Short Message (FSM).
The SMPP System ID to which the message is forwarded.

Indicates if the message should be encoded as SMPP-DELIVER or SMPP-SUBMIT.

This defaults to SMPP-DELIVER if not specified.

Optional property that defines how many allowed prefixes are specified.

Optional property (counters from 0) that defines the allowed prefix.

Only use these properties when a rule is to only be allowed when the SRI-SM is received from certain SMSCs. If you require no restrictions, it is best to not use these properties. Alternatively, you can set prefixes to 0.

Finally, configure your resource policies in the VPS_resourcePolicy.cfg file:

[policy_X]                                                  (1)

        policy_name      = VPS-MSC                          (2)
        num_alternatives = 1                                (3)
        1                = resource,VPS,MAP_fwdSMHandler/-  (4)

[policy_Y]

        policy_name      = VPS-HLR
        num_alternatives = 1
        1                = resource,VPS,MAP_sriSMHandler/-

The name of the policy section in which you will set properties for that policy.
The name of the policy.
Specifies the number of alternatives.

Whatever the <number> shown, there will be <N> list below the num_alternatives property. In this case, it is 1.
The alternative’s information.

MSISDN as prefix

If there are more digits when mapping MSISDN to IMSI, for example if the incoming MSISDN was +35386123450012, the MSISDN (1) in the rule is used as a matching prefix and the resultant mapped IMSI would be made by the rule IMSI (2) followed by the trailing digits from the incoming MSISDN 12 to make 27201123456789012.

When the resultant IMSI is used as input to the IMSI to MSISDN mapping, it would then match this rule and the resultant mapped MSISDN would be formed by the rule MSISDN (1) prefix +353861234500 with the trailing 12 from the IMSI being appended to it to form the MSISDN of +35386123450012 (to match that original incoming MSISDN).

[VPS Rule0]

    Name                                = Main Rule
    MSISDN                              = +353861234500     (1)
    IMSI                                = 272011234567890   (2)
    SMPP System ID                      = miep
    SMPP Command                        = SMPP-DELIVER

Sample file

The sample file here shows you a full VPS_service.cfg file containing a strip and replace function (SMPP B Number SNR File = VPS_smppBNumber.cfg) and one rule entitled [VPS Rule0].

[General]

    Resource Policy File                = /tango/config/VPS_resourcePolicy.cfg
    Resource Name                       = VPS
    Resource Algorithm Id               = 0
    Resource Scope                      = 0
    Resource Priority                   = 0

[HLR]
    MSC Address                         = +123456789

[MSC]
    Number of Instances                 = 50000
    SMPP Router Policy                  = SMPP-ADAPTOR
    SMPP Response Timer                 = 5
    Default SMPP Coding is Packed GSM   = yes

    SMPP B Number SNR File              = (--- None ---)

[CDR]
    Enabled                             = yes
    Handler Policy                      = CDRH-0

[VPS Rule0]

    Name                                = Main Rule
    MSISDN                              = +353861234500
    IMSI                                = 272011234567890
    SMPP System ID                      = miep
    SMPP Command                        = SMPP-DELIVER
    prefixes                            = 1
    prefix0                             = +44

VPS Strip and Replace

When configured, this rule is applied to the MSISDN defined when a rule match is found when processing an MT FSM request. The result (of the strip and replace rule) is used as the B number (destination number) in the SMPP DELIVER (or SUBMIT) sent over SMPP.

If used, name the configuration file VPS_smppBNumber.cfg.

If no strip-and-replace rules are defined or no match is found, the MSISDN in the matching VPS Rule is used as the SMPP B number.

Prerequisites

You must have completed the VPS Service Configuration.
You have defined the SMPP B Number SNR File property in the [MSC] section of the VPS_service.cfg file.

Each strip and replace rule must have the properties set. The rules counter from 0.

Procedure

Enable strip and replace by setting the property to yes.
Set the strict validation mode to no.
Enable the strip and replace rule.
Set the minimum digits.
Set the maximum digits.
Specify what digits are stripped.
Specify the replacement digits.

[General]

	Strip And Replace Enabled  		= 	yes                 (1)
    Strict Validation Mode     		=  	no                  (2)

 [stripAndReplace0]

  	enabled      				    = 	yes                 (3)
  	min digits   				    = 	12                  (4)
  	max digits   				    = 	20                  (5)
   	strip        				    = 	00041006020801      (6)
   	replace      				    = 	000010              (7)