- Old KB
- Control Portal
- Troubleshooting Guides
-
1Stream Platform
- Admin User Functions
- Application Download
- AutoTask Integration
- BrightGauge
- Call Routing Features
- Call Tools
- ConnectWise Integration
- CrewHu
- CRM Management
- DropBox Integration
- End User Management
- Enterprise Portal
- HubSpot Integration
- Freshdesk Integration
- General Troubleshooting
- Hudu
- InfusionSoft Integration
- Insightly
- Liongard Integration
- Kaseya BMS
- MSPbots Integration
- OneDrive Integration
- Power BI
- Progressive Dialer
- Reports
- Salesforce
- ServiceNow Integration
- Signal
- SyncroMSP
- ZenDesk Integration
- Halo Integration
- Transcription and Analytics
-
Control Portal
- Auto Attendant Functionality
- BLF Keys
- bvoip Fundamentals
- Call Flow
- Call Queue
- Call Recordings
- Call Rules
- Desktop Application User Documentation
- Dial Codes
- DIDs
- Extensions
- Extension Tools
- FAQs
- Google Integration
- Microsoft 365
- Multifactor Authentication
- Phone Hours
- Settings
- Security
- Shop
- SIP Trunks
- SIPTrunk.com Partnership
- Storage
- System Notifications
- System Tools
- Troubleshooting Guides
- Users
- Webclient User Documentation
- Whitelabelling
- Zoho Integration
- WhatsApp Integration
-
Device Management & Provisioning
-
Nucleus for Microsoft Teams
-
1Stream Client
-
Messaging
Inbound Calls Being Sent Twice
This article will provide a walkthrough on how to correct this issue when experienced.
Why is the Caller ID Being Sent Twice?
While Caller IDs are sent once by SIP carriers, in some cases, it can be sent twice. When the caller ID is sent more than once, this is a symptom of a larger issue which is usually found on the SIP carrier's side from their primary registration server blacklisting the phone system's IP.
How to Fix It
To correct this issue, reach out to your SIP Carrier and have them whitelist the phone system's IP. Once the IP has been removed from their blacklist, the caller ID will be sent over once from the SIP Carrier.