These are the internal diagnostic codes often seen in:
- SIP logs
- CLS traces
- Snooper
- CDR reports
- Response Group logs
- Front-End event logs
They provide more detailed meaning than standard SIP response codes.
Common Internal Diagnostic IDs
| Diagnostic ID | Meaning | Typical Cause | Notes |
|---|---|---|---|
| 1018 | User not found | SIP URI does not exist in AD | Often paired with 404 |
| 1020 | User not enabled for Skype | AD object exists but not SfB-enabled | Check Get-CsUser |
| 1035 | Call failed to route | No matching voice route | Dial plan / Voice policy issue |
| 1041 | User busy | Endpoint is already in call | Similar to 486 |
| 1053 | User not registered | Client not signed in | Often paired with 480 |
| 1067 | Media negotiation failure | Codec mismatch or encryption issue | Often 488 SIP |
| 1080 | Call declined | User manually rejected call | Common with 603 |
| 1100 | Timeout waiting for response | Endpoint unreachable | Network or client offline |
| 1200 | Database error | Backend SQL issue | Check FE / SQL connectivity |
| 1300 | Response Group agent unavailable | No agents available | Informal mode common |
| 1301 | Response Group timeout | No agent answered in time | Workflow timeout |
| 1400 | PSTN gateway failure | Mediation / SBC issue | Check trunk |
| 1410 | Media bypass failed | Bypass negotiation error | Often firewall related |
| 1500 | Edge connectivity failure | Federation or external issue | Edge / firewall |
| 2005 | Policy restriction | Call blocked by policy | Voice or conferencing policy |
| 3007 | CMS replication issue | Management store not synced | Check replication status |
Diagnostic IDs Common in Response Groups (RGS)
Given how frequently these appear in enterprise deployments:
| Diagnostic ID | Meaning | Common Scenario |
|---|---|---|
| 1300 | No agents available | All agents signed out |
| 1301 | Agent timeout | Agent did not answer |
| 1302 | Workflow misconfiguration | Queue or group error |
| 1305 | Agent declined call | Informal RGS + DND/Busy |
| 1080 | Call declined | User manually rejected |
Diagnostic ID vs SIP Code Example
Example you might see in logs:
SIP: 603
Diagnostic ID: 1305
Meaning:
- SIP 603 = Decline
- Diagnostic 1305 = Agent declined in Response Group
The diagnostic ID gives the true root cause.
How to View Diagnostic IDs
You can find these in:
- Snooper logs (OCSLogger / CLSViewer)
- Front-End event logs
- Response Group call reports
- CDR database records
To check replication issues:
Get-CsManagementStoreReplicationStatus
To check user registration:
Get-CsUser -Identity user@domain.com
Important Notes
- SIP codes show protocol response
- Diagnostic IDs show Skype internal logic
- Always correlate both together when troubleshooting