- Using Cisco Unified SIP Proxy Software
- Cisco Unified SIP Proxy Module EXEC Commands
- Cisco Unified SIP Proxy EXEC Commands
- Cisco Unified SIP Proxy Configuration Commands
- Cisco Unified SIP Proxy SIP Commands
- Cisco Unified SIP Proxy SIP Server Commands
- Cisco Unified SIP Proxy Radius Server Commands
- Cisco Unified SIP Proxy Trigger Commands
- Cisco Unified SIP Proxy Route Commands
- Cisco Unified SIP Proxy Policy Commands
- Cisco Unified SIP Proxy Accounting Commands
- Cisco Unified SIP Proxy Security Commands
- Module Commands for Cisco Unified SIP Proxy
Cisco Unified SIP Proxy Accounting Commands
–
event
accounting
To enter accounting configuration mode, use the accounting command in Cisco Unified SIP Proxy configuration mode. To change the accounting configuration to the factory default values, use the no or default form of this command.
Syntax Description
Command Default
Command Modes
Cisco Unified SIP Proxy configuration (cusp-config)
Command History
|
|
|
|---|---|
Examples
The following example enters accounting configuration mode to configure RADIUS accounting:
The following example returns all values entered in accounting configuration mode to the default values:
Related Commands
|
|
|
|---|---|
client-side
To enable RADIUS accounting on the client side, use the client-side command in Cisco Unified SIP Proxy accounting configuration mode. To disable RADIUS accounting on the client side, use the no form of this command.
Syntax Description
Command Default
Command Modes
Cisco Unified SIP Proxy accounting configuration (cusp-config-acct)
Command History
|
|
|
|---|---|
Usage Guidelines
Client side accounting refers to the accounting of the side of the call where the REP SIP element (Cisco Unified SIP Proxy in this case) acts as a client, sending requests (sending INVITE/BYE). The accounting for the client side of the call is configurable to be enabled or disabled on a global basis (on a node). After being enabled, the accounting behavior is further defined by the accounting triggers, defined for client side transactions.
Examples
The following example enables RADIUS accounting on the client side:
The following example disables RADIUS accounting on the client side:
Related Commands
|
|
|
|---|---|
enable (accounting)
To enable RADIUS accounting on the Cisco Unified SIP Proxy, use the enable command in Cisco Unified SIP Proxy accounting configuration mode. To disable RADIUS accounting, use the no form of this command.
Syntax Description
Command Default
Command Modes
Cisco Unified SIP Proxy accounting configuration (cusp-config-acct)
Command History
|
|
|
|---|---|
Usage Guidelines
When you enter the enable command, all the accounting-related command settings take effect. If the commands were not modified, then the default configuration values take effect.
If RADIUS accounting is disabled, no accounting is done even if the client-side and server-side commands are enabled. If RADIUS accounting is enabled, accounting takes place on the client side if the client-side command is enabled and on the server side if the server-side command is enabled.
Examples
The following example enables RADIUS accounting:
The following example disables RADIUS accounting and overrides all other settings on the Cisco Unified SIP Proxy:
Related Commands
|
|
|
|---|---|
event
To configure RADIUS accounting events, use the event command in Cisco Unified SIP Proxy accounting configuration mode. To remove RADIUS accounting events, use the no form of this command.
event { server | client } { request | response } sequence sequence-number {start | interim | stop | stop-fail} [ condition condition ]
no event { server | client } { request | response } sequence sequence-number {start | interim | stop | stop-fail} [ condition condition ]
Syntax Description
Command Default
Command Modes
Cisco Unified SIP Proxy accounting configuration (cusp-config-acct)
Command History
|
|
|
|---|---|
Examples
The following example configures a RADIUS Start event to be sent if trigger condition c1 is satisfied when a request is received on the server transaction side:
The following example configures a RADIUS Stop event that is sent unconditionally when a response is received on the server transaction side:
The following example removes RADIUS accounting on the server side for the start event on request transactions:
Related Commands
|
|
|
|---|---|
Creates a trigger condition and enters Cisco Unified SIP Proxy trigger configuration mode. |
header (accounting)
To configure which SIP headers are to be included in RADIUS messages, use the header command in Cisco Unified SIP Proxy accounting configuration mode. To remove the SIP headers from the RADIUS messages, use the no form of this command.
header header-name { request | response }
no header header-name { request | response }
Syntax Description
Command Default
Command Modes
Cisco Unified SIP Proxy accounting configuration (cusp-config-acct)
Command History
|
|
|
|---|---|
Usage Guidelines
The headers specified with this command are only added to Start and Interim RADIUS messages (as configured using the event command). For Stop messages, the headers are only present for Stop-fail events.
Examples
The following example adds a via header from the request SIP message to the RADIUS accounting message:
The following example removes the via header obtained from the request SIP message from the RADIUS accounting record:
Related Commands
|
|
|
|---|---|
server-side
To enable RADIUS accounting on the server side, use the server-side command in Cisco Unified SIP Proxy accounting configuration mode. To disable RADIUS accounting on the server side, use the no form of this command.
Syntax Description
Command Default
Command Modes
Cisco Unified SIP Proxy accounting configuration (cusp-config-acct)
Command History
|
|
|
|---|---|
Usage Guidelines
Server side accounting refers to the accounting of the side of the call where the REP SIP element (Cisco Unified SIP Proxy in this case) acts as the server, receiving a transaction request 12 (incoming INVITE/BYE). The accounting for this side of the call is configurable to be enabled or disabled on a global basis (on a node). When enabled, the accounting behavior is further defined by the accounting triggers, defined for server side transactions.
Examples
The following example enables RADIUS accounting on the server side:
The following example disables RADIUS accounting on the server side:
Related Commands
|
|
|
|---|---|
Feedback