
Configuration Procedures and Considerations
# P0602477 Ver: 3.1.11 Page 291
Port Service States
By default, the system places all inbound-only ports out of service when an
application is not bound to them. All other outbound-only and bi-directional port are
in an in-service state, regardless of whether or not an application is bound to them. For
example, in the following configuration:
defpool line.in
defpool line.out
cfgrsrc line.in,phone.1-24.mps.1
cfgrsrc line.out,phone.25-48.mps.1
cfgrsrc line.in,phone.49-72.mps.1
cfgrsrc line.out,phone.49-72.mps.1
lines 1-24 are inbound only and are in an out-of-service state until an application is
bound to them. Lines 25-48 are outbound only, and lines 49-72 are bi-directional, and
they are in an in-service state until either the TMS takes them down or the user
manually takes them down (using the CCM outOfService command, see the
Command Reference Manual). Line pools, that are not explicitly defined as “line.in”,
are assumed to be outbound only and stay in an in-service state.
Applications cannot bind to lines if the line is out of service and is not part of a
“line.in” pool. Lines that are out of service and are not part of a “line.in” pool are
automatically marked as unusable and removes those lines from ALL pools.
Network Failure Detection (Pinging)
The Pool Manager pings other remote PMGRs in the network to verify network
operation. Pinging is enabled by default and should not be disabled (or its default
values changed) unless call processing functions require maximum available network
throughput.
Ping commands are set in pmgr.cfg:
pings on | off - Enable/disable remote PMGR pinging
pingmaxoutstanding # - Set the number of times a ping can be missed
before PMGR considers the remote PMGR unreachable
pingperiod # - Set the amount of time between pings
Komentarze do niniejszej Instrukcji