CommPower CP-145, Руководство по установке и администрированию

Страница: 53 / 121

ACP-145 Gateway Installation and Administration Manual
5-10 /cpe/cp-145/adm/004 (07/14)
Primary/Copy:
This field defines whether the Precedence mapping rule
applies to the Primary recipients only, the Carbon Copy recipients only, or
both Primary and Carbon Recipients.
Precedence Value: This section has three options: None, Integer Value, and
All Integers not defined within this table.
When an X.400 message is received, the CP-145 system will consult this table
to determine if a translation rule applies to the newly received message.
 None: Use this option to define the translation rule when the
Precedence value is missing from a message. If the received X.400
file does not have a Precedence value for the Primary or CC
recipients, the CP-145 system will look to see if there is a rule defined
for None.

NOTE
: When a rule is established for None, the only relevant
Actions that can be defined are Rejected/NDN, or Add.
For example, if the rule was set for Both, None, and NDN, then
when a message is received without Precedence, both primary and
carbon copy recipients will not get the message and the originator
will receive a Non Delivery Notification.
 Integer: Use this option to define the translation rule that will occur
when a received X.400 message contains a Precedence value that
should be converted to another value before being transmitted to the
next Gateway. For example, the United States Precedence value of
Critic is not a valid value in the United Kingdom. In this case, the
integer value of 17 (which represents Critic) could be mapped to the
value of 4 - Flash, which is a valid value in the UK.
 All Integers Not Defined in this table: Use this option to define
the translation rule that will occur when a received X.400 message
contains any Precedence value that does not exist in the table. For
example, a Gateway could be configured so that any other undefined
Precedence values will always be mapped to Routine. Another option
is that any undefined Precedence values not in the table are always
Rejected/NDN.
Action:
This field defines the action to be performed when a Precedence
Rule exists for the received X.400 Message.

Delete:
If the action is set to Delete, then the Precedence value that
exists will be removed from the message.

Add:
If the action is set to Add, then the value that exists in the
Add/Map Value field will be inserted into the message. This option
only applies if the Precedence Value = None.

Map:
If the action is set to Map, then the value that exists in the
Add/Map Value field will take the place of the existing value in the
message.