This command allows
you to associate different content IDs with the same ruledef, depending
on the protocol being used.
Product
Important: In StarOS 18.0 and later releases, this
command has been deprecated.
ACS
Privilege
Security Administrator,
Administrator
Mode
Exec > ACS Configuration
> Ruledef Configuration
active-charging service service_name > ruledef ruledef_name
Entering the above
command sequence results in the following prompt:
[local]host_name(config-acs-ruledef)#
Syntax
Syntax Description
if-protocol { http | wsp-connection-less | wsp-connection-oriented } content-id content_id
no if-protocol { http | wsp-connection-less | wsp-connection-oriented }
no
If previously configured,
deletes the specified rule expression from the current ruledef.
http
Specifies HTTP protocol.
This is the same as
the rule expression http
any-match = true.
wsp-connection-less
Specifies WSP connection-less
protocol.
This is the same as
requiring "wsp
any-match = true" but "wtp any-match = false" (that
is, connection-less WAP1.x).
wsp-connection-oriented
Specifies WSP connection-oriented
protocol.
This is the same as
the combined rule expression "wsp any-match = true" and "wtp any-match = true" (that
is, connection-oriented WAP1.x).
content-id content_id
Specifies the content
ID for the specified protocol.
In
12.1 and earlier releases, content_id must
be an integer from 1 through 65535.
In 12.2 and later releases, content_id must
be an integer from 1 through 2147483647.
Usage Guidelines
Use this command to
associate different content IDs with the same ruledef, depending
on the protocol being used.
This command is only
effective for charging ruledefs. See the command
for information on how to configure charging ruledefs.
If a particular ruledef
should have three different values for content-id, depending on whether
the traffic is connection-oriented WAP1.x, connection-less WAP1.x,
or WAP2.0, within the ruledef we should have configuration similar
to the following:
if-protocol wsp-connection-oriented
content-id 1
if-protocol wsp-connection-less
content-id 2
if-protocol http content-id 3
Presumably, the ruledef
would have another configurable like "www url contains foo",
which would cause it to use different content IDs when "foo" was
accessed, depending upon the protocol being used.
Example
The following command
associates HTTP protocol and a content ID of 23:if-protocol http content-id 23