Odd; without digging deep into the traces I would say something may be up with those table indices?
I can't guarantee this will help; you could take a BAT export of all the hunt pilots, hunt lists and line groups. Then delete them all from CCM and BAT them back in. Thanks, Ryan > On Jul 25, 2016, at 7:19 PM, Erick Bergquist <erick...@gmail.com> wrote: > > Ryan, > > From the system-history log file (didn't do it myself), a fresh > install of 10.5.1.10000-7 was done then a patch to 10.5.2.11900-3. > Then DRS restore performed. > > Still at 10.5.2.11900-3. > > >> On Mon, Jul 25, 2016 at 4:42 PM, Ryan Huff <ryanh...@outlook.com> wrote: >> How was the upgrade performed? >> >> Sent from my iPhone >> >>> On Jul 25, 2016, at 6:34 PM, Erick Bergquist <erick...@gmail.com> wrote: >>> >>> Anyone seen this on 10.5.2? >>> >>> A client had upgraded from 8.5 to 10.5 and whenever they go to add a >>> new Hunt Pilot and select existing Hunt List they get this error. >>> >>> "Add failed. The Gateway already has port(s) assigned to a DN." >>> >>> If they delete the hunt list and add it back new, adding hunt pilots works >>> fine. >>> >>> They have many hunt lists with numerous hunt pilots pointing to each. >>> >>> >>> Erick >>> _______________________________________________ >>> cisco-voip mailing list >>> cisco-voip@puck.nether.net >>> https://puck.nether.net/mailman/listinfo/cisco-voip _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip