Preview Tool

Cisco Bug: CSCun38117 - R-IDC cant disconnect unit calls then unit calls wont connect after that

Last Modified

Jun 25, 2018

Products (1)

  • Cisco IPICS PMC Client Software

Known Affected Releases


Description (partial)

If a remote IDC cannot disconnect a P25 unit call, then subsequent P25 unit calls will not connect after that.

1. Install 4.8(1) IPICS with ISSIG. configure NLR then add 2 ISSI channels. Have two IDC's, one in multicast and the other in Remote. Assign two P25 ID's e.g. 00001.001.001D01 and 00001.001.001D02
2. Start both IDC's, then do a unit call from IDC1 (MC-IDC) to the other R-IDC 00001.001.001D02 (IDC 2 P25 ID)
3. Unit call connects, and PTT possible, disconnect the call from R-IDC unit call will stay connected on MC-IDC
4. Disconnect the call on MC-IDC then try again (unknown error shows on the R-IDC) then unit call will fail with "unknown reason" on MC-IDC while sometimes it will recover and unit call will connect when retried from M-IDC (if you disconnect the MC-IDC side immediately after you disconnect the R-IDC side you have a bigger chance to hit the failed Unit call issue)
5. We were able to reproduce this on two different R-IDC's.

IPICS 4.8(1)
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.