Page History

...

• Userpart value is the content before "@". If there is a ";" in that portion, the userpart value contains only the parts present before it.
• Hostpart value is the content after "@". The value contains the content until the end of the header line or until a ";" or ">" is met.

...

SMM Rules on a Live System

Spacevars
0 product

supports SMM rules on a live system.

Spacevars
0 product

allows the user to modify the SMM rules on a live system when SMM rules are applied. The existing rules continue to exist. The new rules are active once confirmed or applied.  

Spacevars
0 product

user can now edit or update the SMM rules of the Sip Adaptor profile without changing the admin state in a Live environment.

Two Variables comparison Support

A new SMM functionality is added to compare two variables. Two new criterion values, variables-equal and variables-not-equal, are added to determine:

• If the two variables exist and are equal.
  or
• If the two variables exist and are not equal.

Write CDRs using SMM Rules Support

Five new CDR fields of 256 bytes each are introduced to log the proprietary information to the accounting records using the SMM rules:

• SMM-Field-1
• SMM-Field-2
• SMM-Field-3
• SMM-Field-4
• SMM-Field-5

These new fields are present in Sip Specific Protocol string of the START, STOP, IMMEDIATE, and ATTEMPT records for session based accounting.

The value of the above SMM CDR fields are stored with:

• Header value of the SMM rules.
• Parameter value of the SMM rules.
• The value stored in the variable.
• The token value.

Dropping "18x with 100Rel" and Handling Prack

Spacevars
0 product

supports to generate and send the PRACK messages internally and sent the PRACK back to the IAD if an incoming 18x with 100Rel is dropped.

Warning

There are some limitations for this enhancement too: It is assumed that the dropped 18x will not carry a new offer. If a 18x is dropped by the SMM rule, for a call to succeed, the "200 OK for INVITE" contains the SDP. If End-to-End PRACK is enabled, do not use SMM rules to drop "18x with 100Rel". If a "18x with 100Rel" is dropped on Egress, the Required Header received from the Ingress will not be passed to the Egress when Required Header Transparency is enabled. If a "18x with 100Rel" is dropped by the SMM rule, the INVITE with "Require:100 rel" is not supported.

Native SDP Manipulation Support

Spacevars
0 product

used SMM to manipulate SDP by using a regular expression.

Spacevars
0 product

is enhanced to create SMM rules to directly manipulate SDP in a more refined way.

Info
There is only CLI command and no EMA support for Native SDP Manipulation Support.

The following are the new capabilities to manipulate the SDP content:

ADD Operation

The user can now:

• add a line to the session block
• add a line to the specific media stream
• add a parameter to the specific SDP line in either session block or media stream
• add a codec (codec name) to a specific instance of a particular media stream or all instances of that particular media stream
• add a new stream to the SDP

DELETE Operation

The user can now:

• delete a line in the session block
• delete a line in a specific media stream
• delete a parameter from a specific SDP line
• delete a codec (codec name) in a specific instance of a particular media stream or all instances of that particular media stream
• delete a codec by the position as it appears in the "m=" line in a specific instance of a particular media stream or all instances of that particular media stream

GET Operation

The user now use this new GET operation to store the:

• payload type for a given codec (full codec name) in a specific instance of a particular media stream
• codec position as it appears in the "m=" line for given codec (partial codec will be supported) in a specific instance of a particular media stream

STORE Operation

The user can use this existing operation to store:

• a line in the session
• a line in a specific media stream
• a parameter in a specific SDP line

FILTER-CODEC Operation

The user can this new operation to filter or re-arrange the codec in a particular media stream. The from operand value represents the codec pattern being applied for the filtering. The patterns contains up to 25 comma separated codec names or wildcard codec "*". There should be not more than one wildcard "*" codec appears in the codec pattern.

Note
Limitations: You can use the Value type as "From" which allows you to specify up to 25 comma separated codec pattern. However, the total length of the pattern can not exceed 128 bytes. You can use the Variable type as "From" which allows you to specify up to 25 comma separated codec pattern. However, the total length of the pattern can not exceed 256 bytes.

CONDITION EXIST Criterion

The user can:

• use this new criterion type (sdpContent) to determine whether specific media stream contains any codec specific criterion
• use this new messageBody type (messageBody: SDP) to detemine whether the SDP content exist in the message body