Communication Submodule: Phone
 

Overview
 

The Phone submodule is responsible for managing all mobile phone numbers within the communication system. It provides full control over the lifecycle of phone numbers, including creation, validation, API synchronization, suspension handling, refresh operations, and bulk import.
 

This module is deeply integrated with external communication provider APIs, allowing the system to validate phone numbers, retrieve real-time usage data, manage suspension states, and keep phone information synchronized in real-time.
 

URL:

https://user.bull36.com/dashboard/communication/phone
 

Submodule Tab:

Phone
 

Purpose and Scope
 

The 'Phone' submodule serves as the single source of truth for phone numbers used across the entire communication system. Every phone number appearing in customer communication packages, ESIM allocations, or package matching flows originates from this module.
 

Its scope of operation includes:
 

• Management of unassociated phone numbers

• Validation of phone numbers via external APIs

• Tracking of suspension and activation status

• Synchronization of live communication data

• Centralized intake capability via Excel/CSV file import
   

Functional Description
 

The 'Phone' submodule allows users to:
 

• Add new phone numbers with automatic API validation

• Edit existing phone records

• Delete unused phone numbers

• Suspend or unsuspend phone numbers via communication company APIs

• Refresh phone data to retrieve the latest usage and package details

• View real-time API information such as ICCID, data usage, APN, and package

• Import large quantities of phone numbers using Excel or CSV files
   

The system ensures that every phone number is validated, synchronized, and accurately represented before it is used elsewhere on the platform.


 

Table Structure and Columns
 

1. Mobile Number
 

• Displays the full phone number

• Stored in communication_phone.phone_number

• Example format: 919687263716
   

2. Company
 

• Displays the communication provider associated with the phone

• Loaded from communication_company

• Supports localization
   

• Examples:
   

  • Cellcom

  • Pelephone

  • Partner
     

3. Status
 

• Indicates whether the phone is currently active or suspended

• Derived from the suspended column

• States:

  • Active: The phone is active (suspended = 0)

  • Suspended: The phone is blocked by the provider (suspended = 1)

• Clicking on the status opens the Change Status modal window
   

4. API Details
 

• Displays decoded data from phone_detail_api JSON
   

• Includes:
   

  • Data Usage: Total usage in MB

  • APN: Access Point Name

  • ICCID: SIM Identifier

  • Package: Current communication package
     

• Data is automatically updated on refresh or status change
   

5. Refresh
 

• Allows users to manually refresh phone data from the external API

• Calls the phone_refresh endpoint

• Updates usage, package, ICCID, and suspension status

• Displays success or error messages based on the API response
   

6. Actions
 

• Edit: Opens a modal phone edit window

• Delete: Removes a phone after confirmation
  
  
   

  Import Functionality
   

  Bulk Upload Support
   

• Excel (.xls, .xlsx)

• CSV (.csv)
   

• Import Process:
   

• File upload

• Column mapping

• Data validation

• Phone record insertion

• List refresh
   

• ---

  Linked Modules
   

• Customer Communication: Phones associated with customers

• Company: Provider selection

• Package: API package matching
   

• ---

  Summary
   

  The Phone submodule provides:
   

• Full lifecycle management of phone numbers

• Reliable integration with external APIs

• Real-time status and usage synchronization

• Robust suspension and refresh processes

• Bulk intake via Excel/CSV

• Secure and organization-aware access control
   

• This module forms the foundation for all communication-related operations within the communication system, ensuring accuracy, consistency, and real-time visibility of phone data across the platform.