SCM Engineering Rules

This appendix provides SCM-specific engineering rules or guidelines that must be considered prior to configuring the ASR 5000 for your network deployment. General and network-specific rules are located in the appendix of the System Administration and Configuration Guide for the specific network type.

The following rules are covered in this appendix:

SCM Context and Service Rules

  • Multiple SCM services can be configured in the same context (the general rules of 256 maximum services per system and 64 maximum contexts per system apply)
  • SCM services configured within the same context cannot communicate with each other
  • When running collapsed with an access service such as the HA, the CSCF service correlates its call-line with the corresponding HA service call-line. If the HA service call goes down, the CSCF service aborts its call.

SCM Subscriber Rules

  • When running collapsed with an access service such as the HA, the CSCF service correlates its call-line with the corresponding HA service call-line. If the HA service call goes down, the CSCF service aborts its call.

AoR Regular Expression Rules

Regular expressions can be used in source aor and destination aor keywords. Individual characters, sometimes referred to as wildcards or meta characters, can be used to create AoR ranges or broader groups to which rules or policies can be applied.

Meta Characters

Currently, the following meta characters are supported:
  • “$.” (dollar period): can be used in the username, domain, or sub-domain portion of the AoR. The following examples show how this character can be used:
    • $.@Provider.com - matches all users from the “Provider” domain
    • $.@$..com - matches all users with a “.com” domain only
    • mobile$.@Provider.com - matches “Provider” users who have an AoR starting with “mobile”
  • “$” (dollar sign): use to substitute any single character. Example:
    • $11 matches 911, 411, etc.
  • “%” (percent symbol): use to signify the start of a pattern such as add/delete/substitute for translations.

AoR Regular Expression Patterns

The uri-readdress aor keyword found in the Translation Configuration mode, supports the use of regular expression patterns. Individual characters, sometimes referred to as wildcards or meta characters, can be used to create AoR ranges or broader groups to which rules or policies can be applied. In a regular expression pattern, the meta character “%” is used to signify the beginning of an add, delete, or substitute command used for translations.

The syntax of a pattern is:
  • %-nump
  • %+numssub
  • %numt
  • %+psub
Character/Variable Description
- Delete
+ Add
num Numeric character up to 32.
p Prefix
s Suffix
t Truncate
sub Substitute alpha and/or numeric string or “-” (hyphen) or “.” (dot)


Syntax examples:
  • %-nump: Removes (-) specified number (num) of characters from the prefix (p) of the username.
  • %+numssub: Adds (+) specified number (num) of characters (sub) to suffix (s) of the username.
  • %numt: Truncates (t) the username to a specified number (num) of characters.
  • %+psub: Adds (+) specified number (num) to prefix of a dial number.
Practical examples:
  • %-3p: Deletes first three characters from the prefix
  • %+3s111: Adds 111 as the suffix
  • %10t: Truncates the username to 10 characters
  • %+psub: Translation from number 23XY to 155588823XY using the following command:
    uri-readdress user %+p1555888 base-criteria destination aor 23$.
    

Session Recovery Rules

RFC 3261 Proxy

  • Only one call context in the call leg can be recovered. If the call leg is in multiple calls, only the active primary call context will be recovered after a sessmgr task failure.
  • Session recovery should be enabled before the CSCF service creation.