Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9b90306, userName='null'}
AUTH1
bgoswamiREV5REV6radaikalamREV3arossREV1
UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9b90306, userName='null'}
JIRAIDAUTHSBX-95136
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a0c86573c09001659ee32b100026, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c86573c09001658f914ba80014, userName='null'}
aross

Panel

In this section:

Table of Contents
maxLevel4

CAM Changes

Support for Multiple SMM Profiles

The SBC adds support for applying SIP message manipulation (SMM) profiles (SIP adaptor profiles) at both the global and address context levels. The new profiles are in addition to the existing support for input and output profiles applied at the zone and trunk group levels. You have the option to define profiles at any or all of the levels. If more than one profile applies to a session, and "fixed order" execution of the profiles is enabled, the SBC records the names of all the profiles it executed in the CDR for the call. When fixed order execution is not in effect, CDRs contain the name of only the trunk group or zone profile that is executed.

Support CDR for SIPREC Sessions

The SBC is enhanced with CDRs for the SIPREC sessions.These SIPREC CDRs (RECORDING records) are used by Ribbon Protect and SIPREC platforms. When the SBC records the same call towards multiple recorders, it generates a CDR for each recording session towards each SRS separately, including any call attempts. The SBC also generates a SIPREC CDR for recording sessions initiated by CLI/REST command.

Accounting File Version Change

The CAM version of 

Spacevars
0series4
release 06008.0102.00 is XX94.00.00.

For more information, refer to the section Billing Introduction.

CDR Field Changes

New CDR Fields in Release 008.02.00

New CDR field "Ingress Trunk Group for PSX Routing"  is added in START, STOP, ATTEMPT, INTERMEDIATE and EVENT records. Refer to CDR Field Descriptions for more information.

The field "T140 Information" is added to the STOP records. Refer to CDR Field Descriptions for more information.

The field "Remote T140 RTCP Learned Metrics" is added to the STOP records.  Refer to CDR Field Descriptions for more information.

Recording CDR Fields

New fields are populated in the Recording CDR.  Refer to CDR Field Descriptions for more information.

New SIP Variant Sub-Fields

When "fixed order" execution of SMM profiles is specified on a SIP trunk group, the following SIP variant sub-fields are

...

  • Original Calling Number
  • Original Called Number

populated with the names of the profiles used in Ingress Protocol Variant Specific Data (START record field 42) and Egress Protocol Variant Specific Data (START record field 55), as appropriate:

INGRESS PROTOCOL VARIANT SPECIFIC DATA

  • 42.74 Global Ingress SMM Profile Name             :  
  • 42.75 Global Egress SMM Profile Name              :  
  • 42.76 Ac Ingress SMM Profile Name                 :  
  • 42.77 Ac Egress SMM Profile Name                  :  
  • 42.78 Zone Ingress SMM Profile Name     
  • 42.79 Zone Egress SMM Profile Name

For more information, refer to CDR Field Descriptions.


EGRESS PROTOCOL VARIANT SPECIFIC DATA     
 

  • 55.74 Global Ingress SMM Profile Name             : 
  • 55.75 Global Egress SMM Profile Name             
  •  55.76 Ac Ingress SMM Profile Name                
  • 55.77 Ac Egress SMM Profile Name                  :    
  • 55.78 Zone Ingress SMM Profile Name
  • 55.79 Zone Egress SMM Profile Name

...

 

For more information, refer to

...

CDR Field Descriptions.

Pagebreak