Discover, Review, Enjoy — Byte by Byte

Category: Skype

Telephony – Skype for Business Internal Diagnostic IDs

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 IDMeaningTypical CauseNotes
1018User not foundSIP URI does not exist in ADOften paired with 404
1020User not enabled for SkypeAD object exists but not SfB-enabledCheck Get-CsUser
1035Call failed to routeNo matching voice routeDial plan / Voice policy issue
1041User busyEndpoint is already in callSimilar to 486
1053User not registeredClient not signed inOften paired with 480
1067Media negotiation failureCodec mismatch or encryption issueOften 488 SIP
1080Call declinedUser manually rejected callCommon with 603
1100Timeout waiting for responseEndpoint unreachableNetwork or client offline
1200Database errorBackend SQL issueCheck FE / SQL connectivity
1300Response Group agent unavailableNo agents availableInformal mode common
1301Response Group timeoutNo agent answered in timeWorkflow timeout
1400PSTN gateway failureMediation / SBC issueCheck trunk
1410Media bypass failedBypass negotiation errorOften firewall related
1500Edge connectivity failureFederation or external issueEdge / firewall
2005Policy restrictionCall blocked by policyVoice or conferencing policy
3007CMS replication issueManagement store not syncedCheck replication status

Diagnostic IDs Common in Response Groups (RGS)

Given how frequently these appear in enterprise deployments:

Diagnostic IDMeaningCommon Scenario
1300No agents availableAll agents signed out
1301Agent timeoutAgent did not answer
1302Workflow misconfigurationQueue or group error
1305Agent declined callInformal RGS + DND/Busy
1080Call declinedUser 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

Telephony – Skype for Business Server 2019 Cheat Sheet

This page contains commonly used PowerShell commands for administering Skype for Business Server 2019.

Designed for quick reference during troubleshooting, migrations, health checks, and day-to-day admin tasks.

Run all commands from the Skype for Business Management Shell unless stated otherwise.


1. Basic Environment Information

Check Pool Version

Get-CsPool | Select Identity, Version

Check Skype Server Version (Local)

Get-CsServerVersion

Check Topology Services

Get-CsWindowsService

2. Service Health & Status

Check All Skype Services

Get-CsWindowsService | Where-Object {$_.Status -ne "Running"}

Start All Skype Services

Start-CsWindowsService

Stop All Skype Services

Stop-CsWindowsService

Check Replica Status

Get-CsManagementStoreReplicationStatus

3. User Management

Get a User

Get-CsUser -Identity user@domain.com

List All Users in a Pool

Get-CsUser -Filter {RegistrarPool -eq "pool.domain.com"}

Enable a User

Enable-CsUser -Identity user@domain.com -RegistrarPool "pool.domain.com" -SipAddress "sip:user@domain.com"

Move User to Another Pool

Move-CsUser -Identity user@domain.com -Target "newpool.domain.com"

Disable a User

Disable-CsUser -Identity user@domain.com

4. Response Group (RGS) Commands

List All Response Groups

Get-CsRgsWorkflow

Get Specific Workflow

Get-CsRgsWorkflow -Identity "service:ApplicationServer:pool.domain.com/WorkflowName"

Get All Queues

Get-CsRgsQueue

Get All Agent Groups

Get-CsRgsAgentGroup

Export a Workflow

Export-CsRgsConfiguration -Source "pool.domain.com" -FileName "C:\RGSBackup.zip"

Import RGS Configuration

Import-CsRgsConfiguration -Source "pool.domain.com" -FileName "C:\RGSBackup.zip"

5. Dial Plans & Voice Routing

Get Dial Plans

Get-CsDialPlan

Get Voice Policies

Get-CsVoicePolicy

Get PSTN Usage

Get-CsPstnUsage

Get Voice Routes

Get-CsVoiceRoute

Test Number Normalization

Test-CsPhoneNumberNormalization -DialedNumber "+441234567890" -DialPlan "Global"

6. Conferencing & Meetings

Get Conferencing Policy

Get-CsConferencingPolicy

Get Meeting Configuration

Get-CsMeetingConfiguration

Get External Access Configuration

Get-CsExternalAccessConfiguration

7. Certificates

View Certificates

Get-CsCertificate

Assign Certificate

Set-CsCertificate -Type Default

8. CMS & Database

Check CMS Location

Get-CsManagementStoreReplicationStatus

Install / Update Databases

Install-CsDatabase -Update -ConfiguredDatabases -SqlServerFqdn sqlserver.domain.com

9. Edge Server Commands

Check Edge Services

Get-CsWindowsService -ComputerName edgeserver.domain.com

Check Federation

Get-CsAccessEdgeConfiguration

10. Troubleshooting Commands

Test Front-End Services

Test-CsWindowsService

Test SIP Connectivity

Test-CsRegistration -TargetFqdn pool.domain.com

Check Event Logs

Get-WinEvent -LogName "Lync Server"

Test SQL Connectivity

Test-NetConnection sqlserver.domain.com -Port 1433

Common Migration Commands

Move All Users from Old Pool to New Pool

Get-CsUser -Filter {RegistrarPool -eq "oldpool.domain.com"} | 
Move-CsUser -Target "newpool.domain.com"

Export Topology

Export-CsConfiguration -FileName "C:\TopologyBackup.zip"

Notes

  • Always use -WhatIf when running bulk changes
  • Confirm CMS replication is healthy before major changes
  • Validate database versions after CU installs
  • Always back up RGS before migration

© 2026 bytesmith17

Theme by Anders NorénUp ↑