class MtasCel

ManagedElement
MtasFunction
MtasServices
MtasMmt
MtasCel

The MtasCel MO represents the Communication Event Logging function in MTAS node.

This MO is created by the system.

Attributes
integerKeyString
key
mandatory
noNotification
restricted
mtasCel
This attribute is the primary key of MtasCel and this section describes the MtasCel attributes.

Takes effect: Not applicable
BasicAdmState
mtasCelAdministrativeState = LOCKED
This attribute indicates the administrative state of the Communication Event Logging function. This attribute determines if MMTel AS can report communication events towards communication event server.

Takes effect: New session
MtasString0to255DT[0..1]
mtasCelEventServerName
This attribute defines the hostname or IP address and optional port for the Communication Event Server. The attribute is used by MTAS to send PUBLISH messages towards Event Server. Attribute can be configured as e.g. ceventserver.operator.net or 10.1.1.1:5060. Optionally, the string may have a : and <port> appended, where <port> is defined as 4 to 5 digits forming a number with the highest value 1024:65535. Numerical IPv6 addresses must be enclosed with brackets for example [1080::8:800:200c:417A]:8080. Port = 0 means that a domain name is specified, so the port to use is fetched from DNS with SRV lookup. When port is not specified MTAS uses the 5060 default SIP port.

Takes effect: New session
MtasCelReportingFilterListDT[0..100] nonUnique
mtasCelReportingFilterList
The attribute defines communication event filters to enable reporting only for given supplementary services. It is a list of strings where each string represents Supplementary-Service-Identity value as per PS MTAS Offline Charging, 3GPP R12 MM XML 15/190 04-AVA 90118.

Takes effect: New session
MtasCelReportingHeaderFilterDT[0..1]
mtasCelReportingHeaderFilter
This attribute defines filter to enable communication event reporting of served user by matching SIP header of INVITE with the pattern value configured as regular expression. It's string value where Header and Pattern is separated by ':'. The pattern is enclosed within "/". Examples:configure as "User-Agent:/ios/" to enable reporting for devices which carry ios sub-string in the User-Agent header.No filtering is applied when it's empty.

Takes effect: New session