Availbale with RCM license.

The gateway allows to change the passing call parameters using the RADIUS server commands sent in response to RADIUS-Authorization requests. Commands are transferred in the text format using Vendor-Specific attribute (see RADIUS replies to voice messages mapping) with vendor number assigned to Eltex and equal to 35265 and Eltex-AVPair attribute name with the number 1.

In general, Eltex-AVPair attribute format will be as follows:

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1):<$COMMAND-STRING>

By transferring various commands in $COMMAND-STRING, you may manage the following parameters:

CgPN and CdPN number modification:

Number modification may be performed at two stages during call processing:

For the incoming communication, before the call passes through the dial plan, i.e. before its routing. For that purpose, CgPNin and CdPNin values are used for Calling and Called numbers respectively.
For the outgoing communication, after the call passes through the dial plan and after its routing. For that purpose, CgPNout and CdPNout values are used for Calling and Called numbers respectively.

For CgPN numbers, you may modify the following parameters in addition to the number itself:

numtype – CgPN number type;
plantype – CgPN dial plan type;
presentation – CgPN 'presentation' field value.

For CdPN numbers, you may modify the following parameters in addition to the number itself:

numtype – CdPN number type;
plantype – CdPN dial plan type.

CgPN and CdPN number modification request syntax

The command consists of the required part and optional parts. Required part contains an initial text identifier of the command, modified number identifier and modification mask.

«CallManagement:» is a text identifier defining that this attribute contains the call management command.
«CgPNin=», «CdPNin=», «CgPNout=», «CdPNout=» – number identifiers, indicate the number that the modification should be applied to.
'Modifier mask' parameter — modification rule for number digits (may be empty).

Optional part may contain a single or multiple parameters delimited by semicolons. If an optional part of the command is present, required and optional parts are also should be delimited by the semicolon.

Possible optional part parameters:

numtype.
plantype.
presentation

In general, command format will be as follows:

CallManagement:CgPNin=<$modifymask>;numtype=<$numtype>;plantype=<$plantype>;presentation=<$presentation>
where:
«CallManagement:CgPNin=<$modify-mask>;» – required part.
«numtype=<$numtype>;plantype=<$plantype>;presentation=<$presentation>» – optional part.
CallManagement:CdPNin=;numtype=<$numtype>;plantype=<$plantype>
Где:
«CallManagement:CgPNin=;» – required part with an empty modification mask.
«numtype=<$numtype>;plantype=<$plantype>» – optional part.

CallManagement:CgPNin=<$modify-mask>;

where:

«CallManagement:CgPNin=<$modify-mask>;» – required part. Optional part is absent.

Values of parameters used in commands are as follows:

$modify-mask – number modification rule (for rule modification syntax, see Modification rule syntax);
$numtype – represents one of the values: international, national, network-specific, subscriber, unknown;
$plantype – represents one of the values: isdn, national, private, unknown;
$presentation – represents one of the values: allowed, restricted, not-available, spare.

The gateway allows to pass the number modification command parameters in multiple attributes. Thus, a set of commands:

«CallManagement:CgPNin=<$modify-mask>»
«CallManagement:CgPNin=;numtype=<$numtype>»
«CallManagement:CgPNin=;presentation=<$presentation>»

is equivalent to a single command:

«CallManagement:CgPNin=<$modify-mask>;numtype=<$numtype>;presentation=<$presentation>»

If one of the optional parameters (numtype, plantype, presentation) should remain unchanged, do not include it in the request, but you must specify the number type (CgPNin, CdPNin, CgPNout, CdPNout) that passed fields belong to in the beginning of the request.

Example:

For incoming communication, add prefix +7383 to CgPN, change its number type to national and define presentation restricted.

To do that, it is sufficient to pass the attribute with the following value in Access-Accept reply from the RADIUS server:

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1):
CallManagement:CgPNin=+7383;numtype=national;presentation=restricted

Что также это эквивалентно трем атрибутам со значениями:
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:CgPNin=+7383
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:CgPNin=;numtype=national
Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:CgPNin=;presentation=restricted

Call routing management

Using RADIUS server commands, you may manage the call routing process, i.e. to transfer it to another dial plan of the gateway and unconditionally forward it to a prefix created in the configuration (equivalent to the 'direct prefix' parameter described in section Trunk groups).

Routing management command consists of the required part only:

«CallManagement:» – text identifier defining that this attribute contains the call management command.
«NumberingPlan» – identifier that indicates the dial plan change command.
«DirectRoutePrefix» – identifier that indicates the direct routing prefix selection command.

In general, command format will be as follows:

CallManagement:NumberingPlan=<$numplan_idx>
CallManagement:DirectRoutePrefix=<$prefix_index>

where:

$numplan_idx – dial plan sequential number.

$prefix_index – ID of a prefix created in the dial plan.

Example

Change the call dial plan to the 3rd one.

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:NumberingPlan=3

Call category management

Using RADIUS server commands, you may modify access category and subscriber's Caller ID category (equivalent to the 'calling party category'). To do this, use the following fields:

Category changing command consists of the required part only:

«CallManagement:» – text identifier defining that this attribute contains the call management command.
«AccessCategory» – identifier that indicates the access category change command.
«AONCategory» – identifier that indicates the calling party category change command.

In general, command format will be as follows:

CallManagement:AccessCategory=<$category_idx> 
CallManagement:AONCategory=<$category_value>

where:

$category_idx – access category index.
$category_value – Caller ID category index.

The priority of changing the AON category depends on the type of subscriber.

The dynamic subscriber:

Modification via RADIUS;
Modification via modification tables on the incoming leg;
Modification via modification tables on the outgoing leg.

The other subscribers:

Modification via modification tables on the incoming leg;
Modification via RADIUS;
Modification via modification tables on the outgoing leg.

Example

Define subscriber category (calling party category) equal to 7.

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): CallManagement:AONCategory=7

Subscriber parameter management

Available with SMG-PBX and SMG-VAS licenses, SMG-RCM license is not required.

For dynamic subscribers, you may define the 'Line quantity' and line operation mode parameter at the subscriber registration phase.

Subscriber parameter management command consists of the required part only:

«UserManagement:» – text identifier defining that this attribute contains the subscriber record management command.
«MaxActiveLines» – identifier indicating the quantity of active lines that are available to the current subscriber in common mode. The line operation mode will be set as common (even if separate mode has been specified), if the parameter 'MaxActiveLines' is specified.
«MaxEgressLines» – identifier, which indicates the number of egress lines that are available for subscriber in separate mode. The parameter can be combined with the 'MaxIngressLines';
«MaxIngressLines» – identifier, which indicates the number of ingress lines that are available in separate mode. The parameter can be combined with the 'MaxEgressLines';

In general, command format will be as follows:

"UserManagement:MaxActiveLines=<$line_count>"
"UserManagement:MaxEgressLines=<$egress>;MaxIngressLines=<$ingress>;”
"UserManagement:MaxEgressLines=<$egress>”
"UserManagement:MaxIngressLines=<$ingress>”

where:

$line_count – number of active connections available to the subscriber simultaneously;

$egress – number of egress connections that are available to the subscriber;

$ingress – number of ingress connections that are available to the subscriber.

Examples:

Define common line mode and three active lines for a subscriber.

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): UserManagement:MaxActiveLines=3

Set the separate line mode: 3 egress and 2 ingress lines.

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1): 	UserManagement:MaxEgressLines=3;MaxIngressLines=2

Set the common line mode: 2 active lines. (MaxActiveLines has unconditional priority over MaxEgressLines and MaxIngressLines).

Vendor-Specific(26): Eltex(35265): Eltex-AVPair(1):
	UserManagement:MaxEgressLines=6;MaxActiveLines=2;MaxIngressLines=5