Subname Syntax and Wildcarding
You can wildcard one or both portions (name and subname) of a media type and subname pair:
- When you wildcard the name portion of the value, you can provide a specific subname that the Oracle® Enterprise Session Border Controller uses to find matching media profiles.
- When you wildcard the subname portion of the value, you can provide a specific name that the Oracle® Enterprise Session Border Controller uses to find matching media profiles.
The following table defines and explains subname wildcarding and syntax:
| Syntax | Example Value | Description |
|---|---|---|
| <name> | PCMU | Matches any and all media profiles with the name value configured as PCMU. This entry has the same meaning as a value with this syntax: <name>::*. |
| <name>:: | PCMU:: | Matches a media profile with the name with the name value configured as PCMU with an empty subname parameter. |
| <name>::* | PCMU::* | Matches any and all media profiles with the name value configured as PCMU with any and all subname configured. |
| <name>::<subname> | PCMU::64k | Matches a media profiles with the name with the name value configured as PCMU with the subname parameter set to 64k. |
| * | * | Matches anything, but does not have to be a defined media profile. |
| *::* | *::* | Matches any and all media profiles, but requires the presence of media profile configurations. |
| *::<subname> | *::64k | Matches all media profiles with this subname. You might have a group of media profiles with different names, but the same subname value. |
| *:: | *:: | Matches any media profiles with an empty subname parameter. |
| :: | :: | Invalid |
| ::* | ::* | Invalid |
