DSC/ILF Provisioning over CAI3G

Ericsson Dynamic Activation 1

1	Introduction
1.1	Purpose and Scope
1.2	Target Groups
1.3	Typographic Conventions
1.4	Prerequisites
1.5	Namespaces
1.6	Operations
1.7	Web Service Interface
1.8	MOType
1.9	MOId
2	Set Subscription
2.1	Request Data
2.2	Example
3	Get Subscription
3.1	Request Data
3.2	Response Data
3.3	Example
4	Set SLFSubscription
4.1	Request Data
4.2	Example
5	Get SLFSubscription
5.1	Request Data
5.2	Response Data
5.3	Example
6	Faults or Errors
6.1	Dynamic Activation Internal Errors
6.2	Subordinate ILF Error Codes
Reference List

1 Introduction

This section contains information about the prerequisites, purpose, scope, and target group for the document. This section also contains information about typographic conventions used in this document.

1.1 Purpose and Scope

This document describes the Individual Locator Function (ILF) CAI3G interface that is provided for provisioning of Diameter Signaling Controller (DSC).

CAI3G is an Ericsson propriety interface that enables provisioning of user and subscriber data in telecommunication and IT networks. It is a web service interface based on Simple Object Access Protocol (SOAP) 1.1.

Note:: This document is not a tutorial of CAI3G, and it must be used together with document Generic CAI3G Interface 1.2, Reference [2].

1.2 Target Groups

The target group for this document is as follows:

System Integrator

For more information about the different target groups, see Library Overview, Reference [1].

1.3 Typographic Conventions

Typographic conventions are described in the document Library Overview, Reference [1].

In addition, this document uses the following to indicate operations:

C	Create
S	Set
G	Get
D	Delete

1.4 Prerequisites

This document is written with the assumption that the users:

Have basic knowledge about the Ericsson™ Dynamic Activation (EDA) product.
Have knowledge about Generic CAI3G Interface 1.2, Reference [2].

1.5 Namespaces

The following namespaces are referred to in this document:

CAI3G 1.2 Namespace:
http://schemas.ericsson.com/cai3g1.2/
ILF Provisioning Namespace:
http://schemas.ericsson.com/ema/UserProvisioning/ILF/
SLF Provisioning Namespace:
http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/

1.6 Operations

See the following table for the operations, or Managed Objects (MOs), and valid operations covered in this document.

Table 1 DSC/ILF Provisioning
MO	Operations
MO	Create	Get	Set	Delete
SLFSubscription		x	x
Subscription		x	x

1.7 Web Service Interface

The Web Services Definition Language (WSDL) and XML Schema Definition Language (XSD) files that describe the provisioning interface can be found in /home/dveinstaller/da/. It is also possible to download the files and view or store them in an appropriate area by following below instruction:

Save the zip file, Multi_Activation_WSDL_ and_ XSD_ files.zip, to a local folder.
Unpack the zip file.

1.8 MOType

MOType is a plain text string based on the type xs:string. An MOType consists of two parts. One is the namespace of the MO, and the other is the MO name string that is always starting with an alphabetical character in either upper or lower case, followed by zero or more alphabetical characters, digits or underscores.

Those two parts are connected with symbol @. The syntax of the MOType string is MO_Name@MO_Namespace. The name string of an MOType must follow the regular expression: [A-Za-z][A-Za-z0-9]*

The MO name together with the MO namespace must be globally unique.

1.9 MOId

MOId is an XML fragment containing the MOId parameter-value pairs that are used to identify an MO instance in the interface data model. CAI3G 1.2 standard supports compound MO identifiers or multiple MO identifier. The following is an example of an MOId:

Example 1 Example of MOId

<MOId>
   <msisdn>46455395000</msisdn>
   <imsi>46234563545000</imsi>
</MOId>

The MOId is defined as a sequence of xs:any element in CAI3G schema file. It is the developers responsibility to define the real schema for this parameter.

The MOId is also the key attributes that must be defined in the top-level element, CreateMODefinition or SetMODefinition, within MOAttributes parameter.

Each implementation of CAI3G interface is to define own logic relationship of MOId. It is also the CAI3GAgents responsibility to interpret this parameter correctly by either the hard-coded logic or the dynamic parsing of the schema.

2 Set Subscription

This section covers the ILF Subscription command SetSubscription.

MOType

Subscription@http://schemas.ericsson.com/ema/UserProvisioning/ILF/

2.1 Request Data

MOId

Table 2 Set Subscription MOID Parameters
Parameter	Type	Occurrence	Description
`imsi`	Digital string 6-15 digits Each digit is 0-9	Optional	IMSI
`msisdn`	Digital string 5-15 digits Each digit is 0-9	Optional	MSISDN
`publicIdentity`	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	Restricted SIP URI or TEL URL Examples: sip - `sip:impu1@operator.com` tel - `tel:+34657881898`
`privateIdentity`	String 1-256 bits	Optional	Private identity

MOAttributes

The following table covers the parameters that can be used in a SetSubscription request.

Table 3 Set Subscription MO Attributes
Parameter		Type	Occurrence	Description
`imsiEntry`⁽¹⁾			Optional
	`imsi`	Digital string 6-15 digits Each digit is 0-9	Mandatory	This attribute contains the IMSI associated with the subscriber.
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS
`msisdnEntry`⁽¹⁾			Optional
	`msisdn`	Digital string 5-15 digits Each digit is 0-9	Mandatory	This attribute contains the MSISDN associated with the subscriber.
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS
`publicIdEntry`⁽¹⁾			Optional
	`publicIdentity`	String 1-256 bits prefixed with "tel:" or "sip:"	Mandatory	Restricted SIP URI or TEL URL Examples: sip - `sip:impu1@operator.com` tel - `tel:+34657881898`
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS
`privateIdEntry`⁽¹⁾			Optional
	`privateIdentity`	String 1-256 bits	Mandatory	Private identity
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS

(1) if nil = true, the Delete operation is executed.

2.2 Example

An example of a SetSubscription message is as follows:

Example 2 Set Subscription Message

Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/"
 xmlns:ilf="http://schemas.ericsson.com/ema/UserProvisioning/ILF/">
  <soapenv:Header>
    <cai3:SessionId>72e3e45b8b104936a30b144ba334f945</cai3:SessionId>
  </soapenv:Header>
  <soapenv:Body>
    <cai3:Set>
      <cai3:MOType>
      Subscription@http://schemas.ericsson.com/ema/UserProvisioning/ILF/
      </cai3:MOType>
      <cai3:MOId>
        <ilf:imsi>413685500000502</ilf:imsi>
        <ilf:msisdn>46455395000</ilf:msisdn>
        <ilf:publicIdentity>sip:alice_create@test.company.com</ilf:publicIdentity>
        <ilf:privateIdentity>alice_create</ilf:privateIdentity>
      </cai3:MOId>
      <cai3:MOAttributes>
        <ilf:setSubscription imsi="413685500000502" msisdn="46455395000"
         privateIdentity="alice_create" publicIdentity="sip:alice_create@test.company.com">
          <ilf:imsiEntry imsi="413685500000502">
            <ilf:imsi>413685500000502</ilf:imsi>
            <ilf:destination>HSS4</ilf:destination>
          </ilf:imsiEntry>
          <ilf:msisdnEntry msisdn="46455395000">
            <ilf:msisdn>46455395000</ilf:msisdn>
            <ilf:destination>HSS4</ilf:destination>
          </ilf:msisdnEntry>
          <ilf:publicIdEntry publicIdentity="sip:alice_create@test.company.com">
            <ilf:publicIdentity>sip:alice_create@test.company.com</ilf:publicIdentity>
            <ilf:destination>HSS3</ilf:destination>
          </ilf:publicIdEntry>
          <ilf:privateIdEntry privateIdentity="alice_create">
            <ilf:privateIdentity>alice_create</ilf:privateIdentity>
            <ilf:destination>HSS5</ilf:destination>
          </ilf:privateIdEntry>
        </ilf:setSubscription>
      </cai3:MOAttributes>
    </cai3:Set>
  </soapenv:Body>
</soapenv:Envelope>

Response:
<S:Envelope xmlns:S=""http://schemas.xmlsoap.org/soap/envelope/"">
  <S:Header>
    <SessionId xmlns=""http://schemas.ericsson.com/cai3g1.2/"">
   72e3e45b8b104936a30b144ba334f945</SessionId>
    <TransactionId xmlns=""http://schemas.ericsson.com/cai3g1.2/""
    xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xsi:nil=""true""/>
    <SequenceId xmlns=""http://schemas.ericsson.com/cai3g1.2/""
    xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xsi:nil=""true""/>
    <Context xmlns=""http://schemas.ericsson.com/cai3g1.2/""
    xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xsi:nil=""true""/>
  </S:Header>
  <S:Body>
    <SetResponse xmlns=""http://schemas.ericsson.com/cai3g1.2/""/>
  </S:Body>
</S:Envelope>

3 Get Subscription

This section covers the ILF Subscription command GetSubscription.

The GetSubscription operation returns the related data using the provided msisdn, imsi, publicIdentity, or privateIdentity value.

MOType

Subscription@http://schemas.ericsson.com/ema/UserProvisioning/ILF/

3.1 Request Data

MOId

The following table covers the parameters that can be received in a GetSubscription request.

Table 4 Get Subscription MOID Parameters
Parameter	Type	Occurrence	Description
`imsi`	Digital string 6-15 digits Each digit is 0-9	Optional	IMSI
`msisdn`	Digital string 5-15 digits Each digit is 0-9	Optional	MSISDN
`publicIdentity`	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	Restricted SIP URI or TEL URL Examples: sip - `sip:impu1@operator.com` tel - `tel:+34657881898`
`privateIdentity`	String 1-256 bits	Optional	Private identity

3.2 Response Data

MOAttributes

The following table covers the parameters that can be received in a GetSubscription response.

Table 5 Get Subscription MO Attributes
Parameter		Type	Occurrence	Description
`imsiEntry`			Optional
	`imsi`	Digital string 6-15 digits Each digit is 0-9	Mandatory	This attribute contains the IMSI associated with the subscriber.
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS
`msisdnEntry`			Optional
	`msisdn`	Digital string 5-15 digits Each digit is 0-9	Mandatory	This attribute contains the MSISDN associated with the subscriber.
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS
`publicIdEntry`			Optional
	`publicIdentity`	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	Restricted SIP URI or TEL URL Examples: sip - `sip:impu1@operator.com` tel - `tel:+34657881898`
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS
`privateIdEntry`			Optional
	`privateIdentity`	String 1-256 bits	Optional	Private identity
	`destination`	String	Mandatory	The attribute describes the destination value. Example: HSS

3.3 Example

An example of a GetSubscription message is as follows:

Example 3 Get Subscription Message

Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/"]
 xmlns:ilf="http://schemas.ericsson.com/ema/UserProvisioning/ILF/">
   <soapenv:Header>
      <cai3:SequenceId>33</cai3:SequenceId>
      <cai3:TransactionId>44</cai3:TransactionId>
      <cai3:SessionId>55</cai3:SessionId>
   </soapenv:Header>
   <soapenv:Body>
      <cai3:Get>
         <cai3:MOType>Subscription@http://schemas.ericsson.com/ema/UserProvisioning/ILF/
         </cai3:MOType>
         <cai3:MOId>
            <ilf:publicIdentity>sip:alice@test.company.com </ilf:publicIdentity>
         </cai3:MOId>
      </cai3:Get>
   </soapenv:Body>
</soapenv:Envelope>

Response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/" 
xmlns:ilf="http://schemas.ericsson.com/ema/UserProvisioning/ILF/">
   <soapenv:Header>
      <cai3:SequenceId>33</cai3:SequenceId>
      <cai3:TransactionId>44</cai3:TransactionId>
      <cai3:SessionId>55</cai3:SessionId>
   </soapenv:Header>
   <soapenv:Body>
      <cai3:GetResponse>
         <cai3:MOAttributes>
            <ilf:getResponseSubscription publicIdentity="sip:alice@test.company.com">
               <ilf:publicIdEntry publicIdentity="sip:alice@test.company.com">
                  <ilf:publicIdentity>sip:alice@test.company.com</ilf:publicIdentity>
                  <ilf:destination>HSS2</ilf:destination>
               </ilf:publicIdEntry>
            </ilf:getResponseSubscription>
         </cai3:MOAttributes>
      </cai3:GetResponse>
   </soapenv:Body>
</soapenv:Envelope>

The subscriber with publicIdentity sip:alice@test.company.com from destination HSS2 is printed.

4 Set SLFSubscription

This section covers the ILF command setSLFSubscription.

Some parameters of setSLFSubscription do not support the Set operation currently, but still they are allowed parameters in the request.

MOType

SLFSubscription@http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/

4.1 Request Data

MOId

Table 6 Set SLF Subcription MOID Parameters
Parameter	Type	Occurrence	Description
`subscriberId`⁽¹⁾	String	Mandatory	N/A

(1) This parameter is ignored during ILF provisioning currently.

MOAttributes

The following table covers the parameters that can be used in a SetSLFSubscription request.

Table 7 Set SLFSubscription MO Attributes
Parameter		Type	Occurrence	Description
`slfName`⁽¹⁾		String	Optional	N/A
`imsiEntry`			Optional
	`imsi`	Digital string 6-15 digits Each digit is 0-9	Optional	This attribute contains the IMSI associated with the subscriber.
	`diaserver`	String	Optional	The attribute describes the destination value. Example: HSS
	`imsiValidForModules`⁽¹⁾	String with minimum length 2	Optional	N/A
`msisdnEntry`			Optional
	`msisdn`	Digital string 5-15 digits Each digit is 0-9	Optional	This attribute contains the MSISDN associated with the subscriber.
	`diaserver`	String	Optional	The attribute describes the destination value. Example: HSS
`publicIdEntry`			Optional
	`publicIdentity`	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	Restricted SIP URI or TEL URL Examples: sip - `sip:impu1@operator.com` tel - `tel:+34657881898`
	`diaserver`	String	Optional	The attribute describes the destination value. Example: HSS
`privateIdEntry`			Optional
	`privateIdentity`	String 1-256 bits	Optional	Private identity
	`diaserver`	String	Optional	The attribute describes the destination value. Example: HSS
`imsiRangeEntry`			Optional
	`imsiRange`⁽¹⁾	Digital string 0-15 digits Each digit is 0-9	Optional	N/A
	`diaserver`⁽¹⁾	String	Optional	N/A
`msisdnRangeEntry`			Optional
	`msisdnRange`⁽¹⁾	Digital string 0-15 digits Each digit is 0-9	Optional	N/A
	`diaserver`⁽¹⁾	String	Optional	N/A
`publicIdRangeEntry`			Optional
	`publicIdRange`⁽¹⁾	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	N/A
	`diaserver`⁽¹⁾	String	Optional	N/A
`privateIdRangeEntry`			Optional
	`privateIdRange`⁽¹⁾	Sting 1-256 bits	Optional	N/A
	`diaserver`⁽¹⁾	String	Optional	N/A

(1) This parameter is ignored during ILF provisioning currently.

4.2 Example

An example of a SetSLFSubscription message is as follows:

In the following example, the Set operation for slfName is ignored.

Example 4 Set SLFSubscription Message

Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/"
 xmlns:ns="http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/">
   <soapenv:Header>
      <cai3:SequenceId>33</cai3:SequenceId>
      <cai3:TransactionId>44</cai3:TransactionId>
      <cai3:SessionId>55</cai3:SessionId>
   </soapenv:Header>
   <soapenv:Body>
      <cai3:Set>
         <cai3:MOType>
          SLFSubscription@http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/
         </cai3:MOType>
         <cai3:MOId>
            <ns:subscriberId>abc</ns:subscriberId>
         </cai3:MOId>
         <cai3:MOAttributes>
            <ns:setSLFSubscription subscriberId="abc">
               <ns:slfName>aaa</ns:slfName>
               <ns:imsiEntry imsi="413685500000502">
                  <ns:imsi>413685500000502</ns:imsi>
                  <ns:diaserver>HSS4</ns:diaserver>
               </ns:imsiEntry>
               <ns:msisdnEntry msisdn="1234502">
                  <ns:msisdn>1234502</ns:msisdn>
                  <ns:diaserver>HSS4</ns:diaserver>
               </ns:msisdnEntry>
               <ns:publicIdEntry publicId="sip:alice@test.company.com">
                  <ns:publicId>sip:alice@test.company.com</ns:publicId>
                  <ns:diaserver>HSS3</ns:diaserver>
               </ns:publicIdEntry>
            </ns:setSLFSubscription>
         </cai3:MOAttributes>
      </cai3:Set>
   </soapenv:Body>
</soapenv:Envelope>

Response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/">
   <soapenv:Header>
      <cai3:SequenceId>33</cai3:SequenceId>
      <cai3:TransactionId>44</cai3:TransactionId>
      <cai3:SessionId>55</cai3:SessionId>
   </soapenv:Header>
   <soapenv:Body>
      <cai3:SetResponse/>
   </soapenv:Body>
</soapenv:Envelope>

5 Get SLFSubscription

This section covers the ILF command getSLFSubscription.

Some parameters of getSLFSubscription do not support the Get operation currently, but still they are allowed parameters in the request.

MOType

SLFSubscription@http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/

5.1 Request Data

MOId

Table 8 Get SLF Subcription MOID Parameters
Parameter	Type	Occurrence	Description
`subscriberId`⁽¹⁾	String	Mandatory	N/A

(1) This parameter is ignored during ILF provisioning currently.

MOAttributes

The following table covers the parameters that can be used in a getSLFSubscription request.

Table 9 Get SLFSubscription MO Attributes
Parameter	Type	Occurrence	Description
`slfName`⁽¹⁾	String	Optional	N/A
`imsiEntry`	Digital string 6-15 digits Each digit is 0-9	Optional	This attribute contains the IMSI associated with the subscriber.
`msisdnEntry`	Digital string 5-15 digits Each digit is 0-9	Optional	This attribute contains the MSISDN associated with the subscriber.
`publicIdEntry`	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	Restricted SIP URI or TEL URL Examples: sip - `sip:impu1@operator.com` tel - `tel:+34657881898`
`privateIdEntry`	String 1-256 bits	Optional	Private identity
`imsiRangeEntry`⁽¹⁾	Digital string 0-15 digits Each digit is 0-9	Optional	N/A
`msisdnRangeEntry`⁽¹⁾	Digital string 0-15 digits Each digit is 0-9	Optional	N/A
`publicIdRangeEntry`⁽¹⁾	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	N/A
`privateIdRangeEntry`⁽¹⁾	Sting 1-256 bits	Optional	N/A

(1) This parameter is ignored during ILF provisioning currently.

5.2 Response Data

MOId

The following table covers the parameters that can be received in a getSLFSubscription request.

Table 10 Get SLF Subcription MOID Parameters
Parameter	Type	Occurrence	Description
`subscriberId`⁽¹⁾	String	Mandatory	N/A

(1) This parameter is ignored during ILF provisioning currently.

MOAttributes

The following table covers the parameters that can be used in a getSLFSubscription response.

Table 11 Get SLFSubscription MO Attributes
Parameter		Type	Occurrence	Description
`subscriberId`⁽¹⁾		String	Mandatory	N/A
`imsiEntry`			Optional
	`imsi`	Digital string 6-15 digits Each digit is 0-9	Mandatory	This attribute contains the IMSI associated with the subscriber.
	`diaserver`	String	Mandatory	The attribute describes the destination value. Example: HSS
`msisdnEntry`			Optional
	`msisdn`	Digital string 5-15 digits Each digit is 0-9	Mandatory	This attribute contains the MSISDN associated with the subscriber.
	`diaserver`	String	Mandatory	The attribute describes the destination value. Example: HSS
`publicIdEntry`			Optional
	`publicIdentity`	String 1-256 bits prefixed with "tel:" or "sip:"	Optional	Restricted SIP URI or TEL URL Examples: sip - `sip:impu1@operator.com` tel - `tel:+34657881898`
	`diaserver`	String	Mandatory	The attribute describes the destination value. Example: HSS
`privateIdEntry`			Optional
	`privateIdentity`	String 1-256 bits	Optional	Private identity
	`diaserver`	String	Mandatory	The attribute describes the destination value. Example: HSS

(1) This parameter is ignored during ILF provisioning currently.

5.3 Example

An example of a GetSLFSubscription message is as follows:

Example 5 Get SLFSubscription Message

Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/"
 xmlns:ns="http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/">
   <soapenv:Header>
      <cai3:SequenceId>33</cai3:SequenceId>
      <cai3:TransactionId>44</cai3:TransactionId>
      <cai3:SessionId>55</cai3:SessionId>
   </soapenv:Header>
   <soapenv:Body>
      <cai3:Get>
         <cai3:MOType>
          SLFSubscription@http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/
         </cai3:MOType>
         <!--Optional:-->
         <cai3:MOId>
            <ns:subscriberId>abc</ns:subscriberId>
         </cai3:MOId>
         <cai3:MOAttributes>
            <ns:getSLFSubscription subscriberId="abc">
               <ns:slfName>aaaaaa</ns:slfName>
               <ns:publicIdEntry publicId="alice@company.com.cn"/>
            </ns:getSLFSubscription>
         </cai3:MOAttributes>
      </cai3:Get>
   </soapenv:Body>
</soapenv:Envelope>

Response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:cai3="http://schemas.ericsson.com/cai3g1.2/"
 xmlns:ns="http://schemas.ericsson.com/ema/UserProvisioning/SLF/1.1/">
   <soapenv:Header>
      <cai3:SequenceId>33</cai3:SequenceId>
      <cai3:TransactionId>44</cai3:TransactionId>
      <cai3:SessionId>55</cai3:SessionId>
   </soapenv:Header>
   <soapenv:Body>
      <cai3:GetResponse>
         <cai3:MOId>
            <ns:subscriberId>abc</ns:subscriberId>
         </cai3:MOId>
         <cai3:MOAttributes>
            <ns:getResponseSLFSubscription subscriberId="abc">
               <ns:subscriberId>abc</ns:subscriberId>
               <ns:publicIdEntry publicId="sip:alice@test.company.com">
                  <ns:publicId>sip:alice@test.company.com</ns:publicId>
                  <ns:diaserver>HSS2</ns:diaserver>
               </ns:publicIdEntry>
			   </ns:getResponseSLFSubscription>
         </cai3:MOAttributes>
      </cai3:GetResponse>
   </soapenv:Body>
</soapenv:Envelope>

6 Faults or Errors

The generic structure for fault responses is covered in Generic CAI3G Interface 1.2, Reference [2]. That document also covers the generic fault codes, which are applicable to all CAI3G operations.

This section covers the subordinate CAI3G errors. They can appear in the errorcode element in the error message.

The following is an example of a CAI3G error message:

Example 6 CAI3G Error Message

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:cai3g="http://schemas.ericsson.com/cai3g1.2/">
   <S:Header>
      <cai3g:SessionId>2cf0bf2f77d245cc8adeae4ae0311d36</cai3g:SessionId>
      <cai3g:SequenceId>12345</cai3g:SequenceId>
      <cai3g:TransactionId>12345</cai3g:TransactionId>
   </S:Header>
   <S:Body>
      <ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/"
       xmlns:ns3="http://www.w3.org/2003/05/soap-envelope">
         <faultcode>ns2:Server</faultcode>
         <faultstring>This is a server fault</faultstring>
         <detail>
            <Cai3gFault:Cai3gFault xmlns="http://schemas.ericsson.com/cai3g1.2/"
             xmlns:Cai3gFault="http://schemas.ericsson.com/cai3g1.2/">
               <faultcode>4006</faultcode>
               <faultreason>
                  <reasonText>External error.</reasonText>
               </faultreason>
               <faultrole>NEF</faultrole>
               <details>
                  <UserProvisioningFault:UserProvisioningFault
                   xmlns="http://schemas.ericsson.com/ema/UserProvisioning/" 
xmlns:UserProvisioningFault="http://schemas.ericsson.com/ema/UserProvisioning/">
                     <respCode>36006</respCode>
                     <respDescription>No such object. External error. Failed when 
provisioning ILF. - [Processed by PG Node: node1]</respDescription>
                  </UserProvisioningFault:UserProvisioningFault>
               </details>
            </Cai3gFault:Cai3gFault>
         </detail>
      </ns2:Fault>
   </S:Body>
</S:Envelope>

6.1 Dynamic Activation Internal Errors

The following table covers Dynamic Activation internal error codes. They can appear in any CAI3G responses.

Table 12 General Dynamic Activation Internal Error Codes
Error Code	Error Message
1003	Unrecognized namespace. No data view associated
1004	Access denied. Invalid principal or credentials
1005	Not authorized to perform current operation on selected data view
1006	Invalid parameter
1009	Unsupported operation
1010	Invalid session ID
1011	Target is not found
1095	Communication error while interacting with a Network Element
1096	Time-out expired during wait for answer from Network Element
1097	Failure during processing of the request
1098	Could not process request because of resource limitation
1099	System error
1101	External error
1103	License error
2001	Format error
2002	Unreasonable value
2005	Storage shortage in log data file

6.2 Subordinate ILF Error Codes

The following table covers the subordinate ILF error codes.

Table 13 ILF Specific Error Codes
Resp Code	Description	MO	Operation
36006	No such object. No data found in ILF.	`SLFSubscription` `Subscription`	G/S
36099	Other ILF Error.	`SLFSubscription` `Subscription`	G/S

Reference List


[1] Library Overview, 18/1553-CSH 109 628 Uen
[2] Generic CAI3G Interface 1.2, 2/15519-FAY3020003 Uen