Use the existing re-encryption timeout CLI, which is used at rulebase level, for re-encryption.įor AES-GCM encryption, use the optional salt flag. This configuration is same as the one used for the RC4MD5 In this release, the X-Header Insertion and Encryption features are supported only on the GGSN and P-GW.įollowing are the software requirements for the new TLS_RSA_WITH_AES_256_GCM_SHA_384 attribute in CDR:Ĭonfigure AES-256-GCM-sha384 encryption algorithm with 256-bit keys. To HTTP/WSP GET and POST request packets, and HTTP Response packets for use by end applications, such as mobile advertisement insertion (MSISDN, IMSI, IP address, user-customizable, and so The X-Header Insertion and X-Header Encryption features, collectively known as Header Enrichment, enables to append headers In this release, the TLS_RSA_WITH_AES_256_GCM_SHA_384 algorithm is introduced for enhanced security. Revision history details are not provided for features introduced before releases 21.2 and N5.1. show active-charging rulebase statistics nameįeature Summary and Revision History Table 1.show active-charging charging-action statistics name.show active-charging charging-action name.Monitoring and Troubleshooting the X-Header Insertion and Encryption feature.Verifying the X-Header Insertion and Encryption Configuration.Configuring Charging Action for Insertion of X-Header Fields. Configuring X-Header Insertion and Encryption.Limitations to the Header Insertion and Encryption Features.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |