Symptoms

Provider created Service Template in PBA-E based on Reseller Management service gate, created Service Plan using this Service Template and created reseller using created Service Plan.

In PBA-E account was created as reseller, however in POA the account was created as regular customer account.

As a result reseller cannot create own customers and subscriptions for them in POA.

Cause

Service Template created on base of Reseller Management gate is wrong, the parameter External Provisioning Template is empty in Service Template properties.

The only possible value for the parameter External Provisioning Template in a Service Template based on Reseller Management service gate is PEM Reseller. If this parameter is filled in PBA-E Service Template then during reseller provisioning PBA-E will perform the following actions:

  • create regular customer in POA
  • send API request pem.promoteToReseller

As a result account in POA will be promoted to reseller. Otherwise, if the parameter External Provisioning Template is empty in Service Template in PBA-E, then account will be created as reseller in PBA-E only, in POA it will be created as regular customer because PBA-E will not send API request pem.promoteToReseller to POA.

Resolution

Follow the steps below to send API request pem.promoteToReseller to POA to covert customer account to reseller.

  1. Log into POA Management Node

  2. Create XML file pem.promoteToReseller.xml with the following content

    <?xml version='1.0'?>
    <methodCall>
      <methodName>pem.promoteToReseller</methodName>
      <params>
        <param>
          <value>
            <struct>
              <member>
                <name>account_id</name>
                <value><i4>1000101</i4></value>
              </member>
            </struct>
          </value>
        </param>
      </params>
    </methodCall>
    

    Replace 1000101 with ID of the broken reseller account.

  3. Send API request to POA using e.g. curl utility

    ~# curl -d@pem.promoteToReseller.xml http://localhost:8440
    

Internal content