TCAP:Configuration
From TBwiki
(Difference between revisions)
(added links) |
(added related actions) |
||
| Line 9: | Line 9: | ||
'''Note:''' Step 2 must be repeated for each userpart to configure. | '''Note:''' Step 2 must be repeated for each userpart to configure. | ||
| + | |||
| + | |||
| + | == Related actions == | ||
| + | *[[TCAP:General configuration|TCAP general configuration]] | ||
| + | *[[TCAP:Userpart configuration|TCAP userpart configuration]] | ||
[[category:Needs revising]] | [[category:Needs revising]] | ||
Revision as of 14:44, 9 September 2009
General guidelines for configuration of TCAP for a 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.
