Skip to main content

Interlinks

The Interlinks feature allows you to connect multiple FlyNumber phone system instances together, creating a unified communication network. A key benefit is the ability to directly dial Internal Numbers across connected systems, making it perfect for organizations with remote offices or distributed teams.

Main Interlinks interface showing connection options

When you connect two phone system instances:

  • Users can directly dial internal numbers between systems
  • Each system maintains independent configuration
  • Resources are shared based on privacy settings
  • Connections are secure and authenticated
note

Only systems directly connected through an authorization key can access each other's shared resources. For example, if System A connects to Systems B and C:

  • System A can communicate with both B and C
  • Systems B and C cannot communicate with each other
  • Each connection requires its own authorization key

Creating Connections

There are two ways to establish an interlink connection:

1. Generate and Share a Key

Generating a new authorization key

  1. Click "Generate new key"
  2. Enter a name for the connection
  3. Click Save to generate the key

After generation, share the key with the other system administrator:

Copying the generated authorization key

2. Connect Using a Key

To connect using a key from another system:

Creating a new interlink connection

  1. Click "Link to another account"
  2. Enter a name for the connection
  3. Input the authorization key you received

Connection Status

After establishing a connection, you can monitor its status:

Successful interlink connection status

The system uses visual indicators to show connection status:

  • ⚪ Grey circle: Key generated but connection not yet established
  • 🟢 Green circle: Active connection
  • ✖️ Option to delete the connection

You can:

  • Click on a connection to rename it
  • Use the X symbol to delete a connection
  • Monitor connection status in real-time
warning

If an interlink is deleted by either participant:

  • The connection is removed from both systems automatically
  • All shared resource access is immediately terminated
  • The action cannot be undone
  • Users should be notified in advance

Internal Number Integration

When systems are interlinked, they can share access to Internal Numbers. This enables direct dialing between systems using short extension numbers instead of full phone numbers.

Internal Number Behavior

Internal number privacy settings

Key points about internal numbers in interlinked systems:

  1. Number Conflicts

    • If both systems have the same internal number configured
    • Calls will reach the local system's number first
    • Plan your numbering scheme to avoid conflicts
  2. Privacy Controls

    • Privacy Disabled (default): Number is accessible to linked systems
    • Privacy Enabled: Number is only available within its own system
    • Configure privacy when setting up internal numbers
    • Can be modified at any time via the internal number module
  3. Resource Sharing

    • Both systems can access shared internal numbers
    • Privacy settings control accessibility
    • Changes take effect immediately
    • Monitor and document shared resources
Managing Internal Numbers

When using internal numbers across linked systems:

  • Create a consistent numbering plan
  • Document which numbers are shared
  • Use privacy settings strategically
  • Consider departmental boundaries
  • Plan for future expansion

Best Practices

  1. Connection Management

    • Use descriptive names for connections
    • Document shared resources
    • Review connections periodically
    • Monitor usage patterns
  2. Privacy Planning

    • Audit internal number accessibility
    • Consider departmental needs
    • Plan privacy settings carefully
    • Document privacy decisions
  3. Resource Sharing

    • Coordinate numbering plans
    • Avoid duplicate extensions
    • Plan for scalability
    • Consider future growth

Common Use Cases

ScenarioConfiguration Tips
Multi-Office SetupKeep location-specific numbers private
Department IntegrationShare relevant extensions only
Branch ExpansionPlan numbering scheme carefully
Remote TeamsConsider time zone differences
Important Considerations
  • Each authorization key can only link two systems
  • Deleting a connection affects both systems
  • Privacy settings are controlled by the number owner
  • Internal numbers must be unique within each system
  • Local internal numbers take precedence over remote ones