Technical Documentation

^New

Glossary

Portable Libraries

Supported Platforms Search

Advanced Search |

Search Tips

Supported Platforms

h248-options

Syntax

h248-options {accept-emergency-calls-while-graceful;audit-observed-events-returns;encoding {no-dscp-bit-mirroring;use-lower-case;}h248-profile {profile-name profile-name;profile-version version-number;}implicit-tcp-latchimplicit-tcp-source-filterservice-change {control-association-indications {disconnect {controller-failure (failover-909 | restart-902);reconnect (disconnected-900 | restart-902);}down {administrative (forced-905 | forced-908 | none);failure (forced-904 | forced-908 | none);graceful (graceful-905 | none);}up {cancel-graceful (none | restart-918);failover-cold (failover-920 | restart-901);failover-warm (failover-919 | restart-902);}}virtual-interface-indications {virtual-interface-down {administrative (forced-905 | forced-906 | none);graceful (graceful-905 | none);}virtual-interface-up {cancel-graceful (none | restart-918);warm (none | restart-900);}}context-indications {state-loss (forced-910 | forced-915 | none);}use-wildcard-response;}}

Hierarchy Level

[edit services pgcp gateway gateway-name]

Release Information

Statement introduced in Junos OS Release 8.5.

accept-emergency-calls-while-graceful option introduced in Junos OS Release 10.2.

audit-observed-events-returns option introduced in Junos OS Release 9.3.

encoding option introduced in Junos OS Release 9.3.

service-change option introduced in Junos OS Release 9.3.

use-lower-case option introduced in Junos OS Release 9.5.

h248-profile option introduced in Junos OS Release 10.0.

implicit-tcp-latch option introduced in Junos OS Release 10.4.

implicit-tcp-source-filter option introduced in Junos OS Release 10.4.

Description

Configure options that affect virtual BGF H.248 behavior.

Options

accept-emergency-calls-while-graceful

—

Accept emergency calls when the BGF is in a draining state due to a graceful shutdown.

implicit-tcp-latch

—

If explicit latching has been applied (using using ipnapt/latch) on either gate of a gate pair, implicit latching is not applied. If explicit latching has not been applied on either gate, latching is applied to both gates of the gate-pair. When either of the gates latches, latching is automatically disabled on the other gate.

implicit-tcp-source-filter

—

implicit-tcp-source-filter—Applies source address (but not source port) filtering on incoming packets, using the current remote destination address under if explicit source filtering has not been applied by use of gm/saf or ipnapt/latch

The remaining statements are explained separately.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Choose Country

North America

Europe

Asia Pacific