OSS · IM System Service Fulfillment – Inventory Management
Integration

Integrations

How external systems connect to and interact with IM

Integration Map

Inbound
SOAP 1.1 / HTTP Real-time (per order)

OM sends work orders to IM when a customer order is created or modified. Uses the EgyptWorkSheetAll endpoint. IM is the consumer.

Bidirectional
Proprietary sync Periodic (scheduled)

IM synchronizes zone, sector, ADSL exchange, and port data from Matrix. Described in IM-Matrix ISD. IM is the consumer during sync, and can push activation commands via AM.

Bidirectional
Proprietary sync Periodic (scheduled)

Same as Matrix but for FTTH — OLTs, ONTs, VLANs, compounds. Described in IM-eMatrix ISD.

Inbound (auth)
LDAPs Per login

Optional AD authentication mode. IM queries AD to verify user passwords when AD auth is configured. User accounts must still exist in IM's local DB.

None (indirect)
N/A N/A

IM does not connect directly to CRM or Self-Care. CRM → OM → IM is the required path. Telecom Egypt is responsible for network connectivity between all systems.

Calling IM from OM — Quick Start

Endpoint Configuration yaml 
# IM SOAP WebService
Host:    http://<IM_SERVER_HOST>:<PORT>/services/EgyptWorkSheetAll
Method:  POST
Headers:
  Content-Type: text/xml; charset=gb2312
  SOAPAction: ""
💡

Key integration points for OM developers

  • 1. Wrap all field values in a <form>...</form> block inside CDATA
  • 2. Set encoding="gb2312" in the XML declaration (not UTF-8)
  • 3. Include flowId — used as idempotency key, duplicate flowIds return errorCode -1003
  • 4. OM must send ALL parameters regardless of service type — empty strings are fine
  • 5. Always check returnCode in the response, not just HTTP status
  • 6. Implement retrial with exponential backoff on errorCode -9999

Network Requirements

⚠

Network connectivity is Telecom Egypt's responsibility

The following connectivity must be ensured by Telecom Egypt before go-live:
  • • DCN (Data Communication Network) with VPN and firewall policies between all OSS servers
  • • NBI (North Bound Interface) licenses for Matrix and eMatrix
  • • Network path from IM servers to AD/LDAP for authentication
  • • Engineers available on Matrix/eMatrix side during UAT and commercial launch

Retrial Mechanism

IM supports configurable retry logic per integration point:

  • •One configuration file per interface (OM, Matrix, eMatrix, etc.)
  • •Configurable: number of retries and interval between each retry
  • •Huawei provides the configuration guide after development and before deployment
  • •Duplicate flowId retries are safe — IM is idempotent for the same flowId