SIP Endpoints Module Documentation
Table of Contents
Section titled βTable of Contentsβ- Navigation & Access
- Screenshots & Visual Interface
- Module Overview (Technical)
- Module Overview (Commercial/Business)
- Module Overview (End User/Administrator)
- Registration Fields Reference
- Common Scenarios & Examples
- Limitations & Important Notes
- Troubleshooting Tips
- Glossary
- Model Context Protocol (MCP) AI Integration
Navigation & Access
Section titled βNavigation & AccessβTo access the SIP Endpoints registration viewer:
- Log in to the Ring2All Web Portal (
https://<domain-or-ip>/login). - In the left navigation sidebar, expand Reports.
- Under PBX Reports, click SIP Endpoints (
/reports/pbx/sip-endpoints). - Inspect live registrations, verify IP and port bindings, check lease expiration intervals, or click Refresh on the toolbar to re-query Telephony Server Sofia registration caches.
Screenshots & Visual Interface
Section titled βScreenshots & Visual InterfaceβSIP Endpoints Real-Time Registration Ledger
Section titled βSIP Endpoints Real-Time Registration LedgerβComprehensive device registration directory detailing extension numbers, authentication realms, contact URIs, transport protocols (UDP/TCP/TLS/WSS), remote IP addresses, network ports, and expiration countdowns.

1. Module Overview (Technical)
Section titled β1. Module Overview (Technical)βWhat Are SIP Endpoints?
Section titled βWhat Are SIP Endpoints?βSIP Endpoints is a registration monitoring interface that displays all currently registered SIP devices (phones, softphones, ATAs). It queries Telephony Serverβs registration database to show which devices are online, their IP addresses, protocols, and registration status.
Architecture
Section titled βArchitectureβββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ SIP Endpoints Architecture ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€β ββ SIP Devices Telephony Server ββ ββββββββββββββββ βββββββββββββββββββββββββββ ββ β Yealink T46U β β mod_sofia β ββ β 192.168.1.10 β βββREGISTERβββββΊ β β ββ β ext: 1001 β β Registration DB β ββ ββββββββββββββββ β ββ 1001: Online β ββ β ββ 1002: Online β ββ ββββββββββββββββ β ββ 1003: Offline β ββ β Zoiper β βββREGISTERβββββΊ β ββ 1004: Online β ββ β 192.168.1.15 β β β ββ β ext: 1002 β βββββββββββββββββββββββββββ ββ ββββββββββββββββ β ββ βΌ ββ βββββββββββββββββββββββββββ ββ β Backend API β ββ β β ββ β show registrations β ββ β β ββ βββββββββββββββββββββββββββ ββ β ββ βΌ ββ Admin Panel ββ ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ββ β SIP Endpoints Page β ββ β β ββ β Stats: 45 Total | UDP: 30 | TCP: 10 | TLS: 5 β ββ β β ββ β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β ββ β β Status β Ext β IP β Port β ProtoβExpiresβ β ββ β ββββββββββΌβββββββΌβββββββββββββββΌββββββββΌβββββββΌββββββββ€ β ββ β β π’ β 1001 β 192.168.1.10 β 5060 β UDP β 2:45 β β ββ β β π’ β 1002 β 192.168.1.15 β 5060 β TCP β 1:30 β β ββ β βββββββββββββββββββββββββββββββββββββββββββββββββββββββ β ββ β β ββ ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ββ ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ2. Module Overview (Commercial/Business)
Section titled β2. Module Overview (Commercial/Business)βBusiness Value
Section titled βBusiness ValueβSIP Endpoints provides device visibility:
| Without SIP Endpoints | With SIP Endpoints |
|---|---|
| Unknown device status | Online/Offline visible |
| No IP tracking | IP addresses shown |
| Blind troubleshooting | Device details available |
| Manual checking | Instant overview |
Use Cases
Section titled βUse Casesβ-
Device Monitoring
- See all registered phones
- Identify offline devices
-
Troubleshooting
- Find device IP address
- Check registration status
-
Capacity Planning
- Total registration count
- Protocol distribution
-
Security
- Monitor registrations
- Identify unknown devices
Feature Highlights
Section titled βFeature Highlightsβ| Feature | Benefit |
|---|---|
| Online/Offline | Device status |
| IP Address | Network location |
| Protocol | UDP/TCP/TLS |
| Expiry Timer | Registration health |
| Search | Find specific devices |
| Stats | Registration overview |
3. Module Overview (End User/Administrator)
Section titled β3. Module Overview (End User/Administrator)βWhat Can You Do?
Section titled βWhat Can You Do?β- View all registered SIP devices
- See online/offline status
- Check IP addresses and ports
- View protocol (UDP/TCP/TLS)
- Monitor registration expiry
- Search by extension or IP
SIP Endpoints Interface
Section titled βSIP Endpoints Interfaceβββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ SIP Endpoints ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€β ββ Active SIP registrations from Telephony Server ββ ββ [π Refresh] π [Search by extension, IP, or hostname... ] ββ ββ π Stats: ββ ββ Total Registrations: 45 ββ ββ By Protocol: UDP: 30 | TCP: 10 | TLS: 5 ββ ββ By Hostname: pbx1: 25 | pbx2: 20 ββ ββ βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ββ βStatusβ Ext β IP Address β Port βProtoβ Realm βExpiresβ ββ ββββββββΌβββββββΌβββββββββββββββΌβββββββΌββββββΌβββββββββΌββββββββ€ ββ β π’ β 1001 β192.168.1.10 β 5060 β UDP βdomain1 β 02:45 β ββ β π’ β 1002 β192.168.1.15 β 5060 β TCP βdomain1 β 01:30 β ββ β π’ β 1003 β192.168.1.20 β 5061 β TLS βdomain1 β 04:15 β ββ β π΄ β 1004 β - β - β - βdomain1 β Exp. β ββ β π’ β 1005 β10.0.0.50 β 5060 β UDP βdomain2 β 03:00 β ββ βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ββ ββ π’ Online: 44 | π΄ Offline: 1 ββ ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββQuick Tips
Section titled βQuick Tipsβ[!TIP] Refresh: Click Refresh to get latest registration data.
[!TIP] Search: Search by extension number or IP address.
[!NOTE] Expiry: Low expiry time is normal - devices re-register automatically.
4. Registration Fields Reference
Section titled β4. Registration Fields ReferenceβDisplay Columns
Section titled βDisplay Columnsβ| Column | Description |
|---|---|
| Status | Online (π’) or Offline (π΄) |
| Extension | Extension/user ID |
| IP Address | Device IP address |
| Port | SIP port number |
| Protocol | UDP, TCP, or TLS |
| Realm | Registration realm/domain |
| Hostname | Telephony Server |
| Expires In | Time until re-registration |
| SIP URL | Full SIP contact URL |
Status Types
Section titled βStatus Typesβ| Status | Description |
|---|---|
| π’ Online | Device is registered |
| π΄ Offline | Registration expired |
Protocols
Section titled βProtocolsβ| Protocol | Port | Description |
|---|---|---|
| UDP | 5060 | Standard SIP |
| TCP | 5060 | Reliable SIP |
| TLS | 5061 | Encrypted SIP |
5. Common Scenarios & Examples
Section titled β5. Common Scenarios & ExamplesβScenario 1: Check If Phone Is Online
Section titled βScenario 1: Check If Phone Is Onlineβ- Open SIP Endpoints
- Search for extension number
- Check status (π’ or π΄)
Scenario 2: Find Device IP Address
Section titled βScenario 2: Find Device IP Addressβ- Search by extension
- Note the IP Address
- Use for network troubleshooting
Scenario 3: Monitor Protocol Usage
Section titled βScenario 3: Monitor Protocol Usageβ- View Stats section
- Check βBy Protocolβ breakdown
- Verify TLS adoption
Scenario 4: Identify Offline Devices
Section titled βScenario 4: Identify Offline Devicesβ- Look for π΄ status
- Note affected extensions
- Troubleshoot connectivity
6. Limitations & Important Notes
Section titled β6. Limitations & Important NotesβTechnical Notes
Section titled βTechnical Notesβ[!NOTE] Registration Window: Devices typically register every 60-300 seconds.
[!NOTE] Multi-Device: One extension can have multiple registrations.
[!WARNING] Network Issues: Offline status may indicate network problems.
Best Practices
Section titled βBest Practicesβ- Regular Monitoring: Check for unexpected offline devices
- Protocol Review: Encourage TLS for security
- IP Tracking: Note unusual IP changes
- Expiry Health: Very short expiry may indicate issues
- Search Smart: Use partial matching
7. Troubleshooting Tips
Section titled β7. Troubleshooting TipsβCommon Issues
Section titled βCommon Issuesβ| Symptom | Possible Cause | Solution |
|---|---|---|
| Device offline | Network issue | Check connectivity |
| Wrong IP | NAT issue | Configure NAT |
| Short expiry | Firewall | Check SIP ALG |
| No registration | Credentials | Verify username/password |
| Multiple entries | Multi-device | Normal for multiple phones |
Diagnostic Commands
Section titled βDiagnostic CommandsβTelephony Server CLI:
# Show all registrationsfs_cli -x "show registrations"
# Show specific profile registrationsfs_cli -x "sofia status profile internal reg"
# Show registration countfs_cli -x "show registrations count"Diagnostic SQL
Section titled βDiagnostic SQLβCheck extension registration status:
-- Extensions are in telephony database-- Registrations are live in Telephony ServerSELECT extension, effective_caller_id_nameFROM public.sip_extensionsWHERE domain_id = [domain_id] AND enabled = true;8. Glossary
Section titled β8. Glossaryβ| Term | Definition |
|---|---|
| SIP | Session Initiation Protocol |
| Registration | Device announcing presence |
| Endpoint | SIP device (phone, softphone) |
| Realm | SIP domain for registration |
| Expiry | Time until registration expires |
| mod_sofia | Telephony Server SIP module |
| NAT | Network Address Translation |
9. Model Context Protocol (MCP) AI Integration
Section titled β9. Model Context Protocol (MCP) AI IntegrationβThe Ring2All Platform Copilot integrates with Telephony Serverβs Sofia SIP registration engine via the Model Context Protocol (MCP). Telecom administrators, desktop support staff, and field engineers can query active device registrations, verify desk phone IP bindings, and detect offline endpoints using conversational prompts.
Exposed MCP Tools
Section titled βExposed MCP Toolsβ| Tool Name | Operation | Primary Parameters | Description |
|---|---|---|---|
query_sip_endpoints |
Live SIP Registrations | extension (string, optional), search (string, optional) |
Queries Telephony Server live registrations (show registrations as json), returning registered extensions, contact URIs, client user agents, network IP addresses, transport protocols, and lease expiries. |
list_extensions |
Extension Directory | search (string, optional) |
Lists all provisioned extensions within the domain to cross-reference configured vs. registered endpoints. |
get_extension_status |
Single Endpoint Health | extension (string) |
Retrieves real-time registration status, current call forwarding rules, and DND state for an extension. |
Operational Safeguards & Network Visibility
Section titled βOperational Safeguards & Network Visibilityβ- Domain Isolation: SIP registration checks automatically enforce the current domainβs SIP realm (
WHERE domain_name = :domain_name). Endpoints belonging to other tenants are hidden. - Read-Only Inspection: Querying registration status performs non-destructive read operations against the Sofia internal memory cache.
- NAT Traversal Diagnostics: The tool returns both the private Contact URI and the external public IP (via received/nat parameters) to quickly diagnose one-way audio or NAT keep-alive failures.
Example MCP Payloads
Section titled βExample MCP Payloadsβ1. Checking Live SIP Registrations (query_sip_endpoints)
Section titled β1. Checking Live SIP Registrations (query_sip_endpoints)β{ "extension": "1001"}Response:
{ "success": true, "data": { "total": 1, "registrations": [ { "extension": "1001", "realm": "company.ring2all.com", "contact": "sip:1001@192.168.1.105:5060;transport=udp", "userAgent": "Yealink SIP-T46U 108.86.0.70", "networkIp": "190.212.45.18", "networkPort": "5060", "expiresSeconds": 240, "status": "Registered" } ] }}2. Querying All Currently Online Devices (query_sip_endpoints)
Section titled β2. Querying All Currently Online Devices (query_sip_endpoints)β{}Copilot Natural Language Prompts
Section titled βCopilot Natural Language Promptsβ- βIs extension 1001 currently registered and online?β
- βShow me all registered SIP endpoints in our domain.β
- βWhat device model and IP address is extension 1004 registered from?β
- βList any configured extensions that are currently unregistered (offline).β
Documentation last updated: January 2026

