Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

Symbols  A  B  C  D  E  G  I  L  M  N  O  P  R  S  T  W

 

Symbols

3GPP    
Charging-Rule-Base-Name
gateway    
configuration example
3GPP gateway    
charging rule    
installation example
removal example
charging rule installation    
service activation
charging rule removal    
service deactivation
charging rule report
Charging-Rule-Base-Name
Charging-Rule-Install
Charging-Rule-Name
configuration statements
configuration summary
directory-connection    
configuring
directory-eventing    
configuring
file logging    
configuring
grouped configurations    
configuring
Gx interface    
configuring
initial properties    
configuring
Juniper-Substitution
Juniper-Substitution-Name
Juniper-Substitution-Value
local properties    
configuring
managing
NIC proxies    
configuration prerequisites
resolution information, configuring
NIC proxy    
configuring
non-parameterized charging rule
object adapter Internet address    
configuring
overview
parameterized charging rule
PCRF
peer communication    
redundancy
restarting
SAE    
mapping between concepts
service accounting
service activation sequence
service deactivation sequence
service modification sequence
session termination sequence
starting
stopping
subscriber login sequence
subscriber logout sequence
subscriber type    
configuring
system logging    
configuring
3GPP Gy    
configuration statements
configuration summary
directory-connection    
configuring
directory-eventing    
configuring
file logging    
configuring
grouped configurations    
configuring
initial properties    
configuring
interface    
configuring
local properties    
configuring
managing
NIC proxies    
configuration prerequisites
resolution information, configuring
NIC proxy    
configuring
object adapter Internet address    
configuring
overview
peer communication    
redundancy
restarting
service activation sequence
service deactivation sequence
starting
stopping
subscriber login sequence
subscriber logout sequence
subscriber type    
configuring
system logging    
configuring
3GPP Gy NIC proxies    
cache, configuring    
SRC CLI
NIC replication, configuring    
SRC CLI
replication, configuring    
SRC CLI
resolution information, configuring    
SRC CLI
 

A

Application Services Gateway.     See Web Services Gateway    
arguments for scripts and methods
ASG (Application Services Gateway).     See Web Services Gateway    
 

B

B2B environments
business partner responsibilities    
Dynamic Service Activator
business partners
business-to-business environments
 

C

classify-traffic condition    
expanded classifiers    
configuring
clients    
gateway    
testing
Web Services Gateway
Web Services Gateway
configuration namespace
conventions    
notice icons
text
customer support    1
contacting JTAC
 

D

Diameter    
peers    
configuring    12
documentation    
comments on
dynamic properties
Dynamic Service Activator    
access constraints    
defining    12
access to attributes    
configuring, SRC CLI
access to methods    
configuring, C-Web interface
configuring, SRC CLI
access to methods and scripts    
configuring, C-Web interface    12
configuring, SRC CLI    12
access to scripts    
configuring, C-Web interface
configuring, SRC CLI
access to service sessions    
configuring, SRC CLI
API
attributes    
access to
configuring with C-Web interface
configuring with SRC CLI
gateway extension    
description
general properties    
configuring, C-Web interface
configuring, SRC CLI
groups    
configuring with C-Web interface
configuring, SRC CLI
interacting with Web application server    12
loading    
sample data
logging properties    
configuring, C-Web interface    12
configuring, SRC CLI
methods    1
access to    1234
monitoring with SRC CLI
NIC proxies, monitoring    
SRC CLI
NIC proxies, viewing    
C-Web interface
SRC CLI
overview
properties for clients and scripts    
configuring, C-Web interface    12
configuring, SRC CLI    12
redundancy
sample data    12
scripts    
access to    1234
service sessions    
access to
session handles    
configuring, SRC CLI
SOAP operations, monitoring    
SRC CLI
SOAP operations, viewing    
C-Web interface    12
starting with C-Web interface
starting with SRC CLI
statistics, viewing    
C-Web interface
SRC CLI
subscriber types    
configuring, SRC CLI
test environment    
configuring, SRC CLI    12
PCMM services
testing    1
clients    12
Web application gateway client    12
 

E

events, publishing    123
expanded classifiers    
configuring
 

G

gateway    
SRC    12
gateway extension
 

I

IMS service sessions    
configuring
test environment    
configuring
testing    12
SRC CLI
 

L

local properties    
configuration    
SRC CLI    12
directory location of SRC data, configuring    12
logging properties    
Dynamic Service Activator    1
configuring with C-Web interface    12
 

M

managing    
SAE via external applications    12
services via external application
manuals    
comments on
methods    
Dynamic Service Activator
 

N

namespace, configuration
NIC (network information collector)    
Dynamic Service Activator and
testing    
test data    12
test data, 3GPP Gy
NIC proxies    
cache, configuring    
SRC CLI    12
configuration prerequisites
Dynamic Service Activator    12
NIC replication, configuring    
SRC CLI    123
replication, configuring    
SRC CLI
resolution information, configuring    
SRC CLI    12
notice icons
 

O

operation    
Dynamic Service Activator
 

P

priorityList    123
publishing events    123
 

R

randomPick    123
redundancy    
Dynamic Service Activator
roundRobin    123
 

S

SAE (service activation engine)    
configuring 3GPP gateway as external plug-in
configuring 3GPP Gy as external plug-in
configuring IMS as external plug-in
managing via external applications    12
scripts    
running on SAE
services    
managing via external application
sessions    
service    
testing
SOAP    
interfaces, public
requests
SRC owners    1
Dynamic Service Activator
SRC SOAP Gateway.     See Web Services Gateway    
static properties
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
 

W

Web application gateway client    
configuring, SRC CLI    12
Web application server    1
interacting with Dynamic Service Activator    12
Web applications    
Web Services Gateway
Web Services Description Language.     See WSDL    
Web Services Gateway    1
clients    1
managing
testing
Web application
wholesaler-retailer environments
WSDL files

Related Documentation

Configuring a NIC Proxy for IMS (SRC CLI)

Tasks to configure the NIC proxy are:

Configuring Resolution Information for a NIC Proxy

You create a NIC proxy for each subscriber type to be configured. Subscriber types that have different subscriber ID types can use the same NIC proxy.

Use the following configuration statements to configure the NIC proxy:

shared ims configuration nic-proxy-configuration name
shared ims configuration nic-proxy-configuration name resolution { resolver-name resolver-name; key-type key-type; value-type value-type; expect-multiple-values; constraints constraints; }

To configure resolution information for a NIC proxy:

  1. From configuration mode, access the statement that configures the NIC proxy configuration. In this sample procedure, the NIC proxy called ip is configured.
    user@host# edit shared ims configuration nic-proxy-configuration ip resolution
  2. Specify the NIC resolver that this NIC proxy uses. This resolver must be the same as one that is configured on the NIC host.
    [edit shared ims configuration nic-proxy-configuration ip resolution] user@host# set resolver-name resolver-name
  3. Specify the NIC data type that the key provides for the NIC resolution.
    [edit shared ims configuration nic-proxy-configuration ip resolution] user@host# set key-type key-type

    To qualify data types, enter a qualifier within parentheses after the data type; for example, to specify username as a qualifier for the key LoginName:

    [edit shared ims configuration nic-proxy-configuration ip resolution] user@host# set key-type LoginName (username)
  4. Specify the type of value to be returned in the resolution for the application that uses the NIC proxy.
    [edit shared ims configuration nic-proxy-configuration ip resolution] user@host# set value-type value-type
  5. (Optional) If the key can have more than one value, specify that the key can have multiple corresponding values.
    [edit shared ims configuration nic-proxy-configuration ip resolution] user@host# set expect-multiple-values
  6. (Optional. Available at the Advanced editing level.) If the application provides a constraint in the resolution request, specify the data type for the constraint. The constraint represents a condition that must or may be satisfied before the next stage of the resolution process can proceed.
    [edit shared ims configuration nic-proxy-configuration ip resolution]user@host# set constraints constraints
  7. (Optional) Verify your configuration.
    [edit shared ims configuration nic-proxy-configuration ip resolution] 
    user@host# show 
    resolver-name /realms/ip/A1;
    key-type Ip;
    value-type SaeId; 

Changing the Configuration for the NIC Proxy Cache

You can modify cache properties for the NIC proxy to optimize the resolution performance for your network configuration and system resources. Typically, you can use the default settings for the cache properties. The configuration statements are available at the Advanced editing level.

Use the following configuration statements to change values for the NIC proxy cache:

shared ims configuration nic-proxy-configuration name cache {
cache-size cache-size;
cache-cleanup-interval cache-cleanup-interval;
cache-entry-age cache-entry-age;
}

To configure the cache for a NIC proxy:

  1. From configuration mode, access the statement that specifies the NIC proxy configuration. In this sample procedure, the NIC proxy called ip is configured.
    user@host# edit shared ims configuration nic-proxy-configuration ip cache
  2. (Optional) Specify the maximum number of keys for which the NIC proxy retains data.
    [edit shared ims configuration nic-proxy-configuration ip cache]user@host# set cache-size cache-size

    If you decrease the cache size or disable the cache while the NIC proxy is running, the NIC proxy removes entries in order of descending age until the cache size meets the new limit.

  3. Specify the time interval at which the NIC proxy removes expired entries from its cache.
    [edit shared ims configuration nic-proxy-configuration ip cache] user@host# set cache-cleanup-interval cache-cleanup-interval
  4. (Optional) Specify how long an entry remains in the cache.
    [edit shared ims configuration nic-proxy-configuration ip cache]user@host# set cache-entry-age cache-entry-age
  5. (Optional) Verify your configuration.
    [edit shared configuration nic-proxy-configuration ip cache] 
    user@host# show 
    cache-size 10000; 
    cache-cleanup-interval 15; 

Configuring a NIC Proxy for NIC Replication

Typically, you configure NIC replication to keep the NIC highly available. You configure NIC host selection to specify the groups of NIC hosts to be contacted to resolve a request, and to define how the NIC proxy handles NIC hosts that the proxy is unable to contact. The configuration statements are available at the Normal editing level.

Use the following configuration statements to configure NIC host selection for a NIC proxy:

shared ims configuration nic-proxy-configuration name nic-host-selection { groups groups ; selection-criteria (roundRobin | randomPick | priorityList); }
shared ims configuration nic-proxy-configuration name nic-host-selection blacklisting { try-next-system-on-error; number-of-retries-before-blacklisting number-of-retries-before-blacklisting ; blacklist-retry-interval blacklist-retry-interval ; }

To configure a NIC proxy to use NIC replication:

  1. From configuration mode, access the statement that specifies the NIC proxy configuration. In this sample procedure, the NIC proxy called ip is configured.
    user@host# edit shared ims configuration nic-proxy-configuration ip nic-host-selection
  2. (Optional) Specify the list of groups of NIC hosts that the NIC proxy can contact for resolution requests.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection] user@host# set groups groups
  3. (Optional) If you configure more than one group, specify the selection criteria that the NIC proxy uses to determine which NIC host to contact.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection] user@host# set selection-criteria (roundRobin | randomPick | priorityList)

    where:

    • roundRobin—NIC proxy selects NIC hosts in a fixed, cyclic order. The NIC proxy always selects the next host in the list.
    • randomPick—NIC proxy selects NIC hosts randomly from the list.
    • priorityList—NIC proxy selects NIC hosts according to their assigned priorities in the list. If the host with the highest priority in the list is not available, the NIC proxy tries the host with the next-highest priority, and so on.

      Priorities are defined by the order in which you specify the groups. You can change the order of NIC hosts in the list by using the insert command.

  4. (Optional) Verify your configuration.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection] 
    user@host# show 
    groups ;
    selection-criteria round-;
  5. Access the statement that specifies the NIC proxy configuration for blacklisting—the process of handling nonresponsive NIC hosts.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection] user@host# edit blacklisting [edit shared ims configuration nic-proxy-configuration ip nic-host-selection blacklisting]
  6. (Optional) Specify whether or not the NIC proxy should contact the next specified NIC host if a NIC host is determined to be unavailable.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection blacklisting]user@host# set try-next-system-on-error
  7. (Optional) Change the number of times the NIC proxy tries to communicate with a NIC host before the NIC proxy stops communicating with the NIC host for a period of time. The default is 3.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection blacklisting]user@host# set number-of-retries-before-blacklisting number-of-retries-before-blacklisting
  8. (Optional) Change the interval at which the NIC proxy attempts to connect to an unavailable NIC host. The default is 15 seconds.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection blacklisting]user@host# set blacklist-retry-interval blacklist-retry-interval
  9. (Optional) Verify your configuration.
    [edit shared ims configuration nic-proxy-configuration ip nic-host-selection blacklisting] 
    user@host# show 
    try-next-system-on-error;
    number-of-retries-before-blacklisting 3;
    blacklist-retry-interval 15;

Configuring NIC Test Data

To test a resolution without the NIC, you can configure a NIC proxy stub to take the place of the NIC. The NIC proxy stub comprises a set of explicit mappings of data keys and values in the NIC proxy configuration. When the SRC component configured to use a NIC proxy stub passes a specified key to the NIC proxy stub, the NIC proxy stub returns the corresponding value. When you use a NIC proxy stub, no NIC infrastructure is required.

Use the following configuration statements to configure a NIC proxy stub from the [edit] hierarchy level.

shared ims configuration nic-proxy-configuration name test-nic-bindings { use-test-bindings; }
shared ims configuration nic-proxy-configuration name test-nic-bindings key-values name { value;}

To use the NIC proxy stub for IMS:

  1. In configuration mode, navigate to the NIC proxy configuration and specify the data type of the key you want to map to a value. In this sample procedure, the key ip is specified for the NIC proxy called ip.
    [edit shared ims configuration nic-proxy-configuration ip] user@host# set resolution key-type ip
  2. Enable a NIC proxy stub for a resolution.
    [edit shared ims configuration nic-proxy-configuration ip] user@host# set test-nic-bindings use-test-bindings
  3. Specify the values of the keys for testing. These statements are available at the Advanced CLI editing level.
    [edit shared ims configuration nic-proxy-configuration ip] user@host# set test-nic-bindings key-values name value

    where:

    • name—Indicates the NIC data value for the proxy.
    • value—Specifies a value for the NIC data type.

    For example, to set up a login name to IP mapping for login name jane@virneo.com to the IP address 192.0.2.30:

    [edit shared ims configuration nic-proxy-configuration ip] user@host# set test-nic-bindings key-values jane@virneo.com 192.0.2.30

Related Documentation

Modified: 2016-05-26