TCAP:Configuration: Difference between revisions
(initial content) |
mNo edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
General guidelines for configuration of TCAP for | General guidelines for configuration of TCAP for proper operation include the following steps: | ||
#The TCAP general | #The TCAP [[TCAP:General configuration|general configuration]] must precede all other messages (other configuration TCAP allocation, get, states and stats). The response of this message is a TCAP handle. ('''Note:''' All fields of a configuration message alloc must be filled unless explicitly optional or not defined for certain variants.) | ||
#The TCAP userpart | #The TCAP [[TCAP:Userpart configuration|userpart configuration]] must be made (with the TCAP handle from step 1) for a particular subsystem number. The response of this message is a TCAP userpart handle. | ||
| Line 11: | Line 11: | ||
== Related actions == | |||
[[ | *[[TCAP:General configuration|TCAP general configuration]] | ||
*[[TCAP:Userpart configuration|TCAP userpart configuration]] | |||
Latest revision as of 15:29, 24 April 2018
General guidelines for configuration of TCAP for proper operation include the following steps:
- The TCAP general configuration must precede all other messages (other configuration TCAP allocation, get, states and stats). The response of this message is a TCAP handle. (Note: All fields of a configuration message alloc must be filled unless explicitly optional or not defined for certain variants.)
- The TCAP userpart configuration must be made (with the TCAP handle from step 1) for a particular subsystem number. The response of this message is a TCAP userpart handle.
Note: For any reconfiguration with a TCAP message, all reconfigurable parameters must be filled appropriately even if the intention is to modify a single parameter.
Note: Step 2 must be repeated for each userpart to configure.