<div dir="ltr">FYI the issue was that BAT inserted the Pickup Group Numbers into the numplan table, but errored out on inserting the Pickup Group Names into the the appropriate table, leaving the numplan entries orphaned. The solution that TAC eventually worked out was to use the CLI to remove them from the table. The command they used was:<br>
<br>run sql delete from numplan where dnorpattern = 'XXXX'<br><br>where XXXX was the bad pickup group number. I knew that the issue was a bad entry in the numplan table, but I had didn't try to delete it myself as I had always been told that you could only perform SQL selects without root access. I guess you live and learn!<br>
<br>Thanks,<br>Adam<br><br><div class="gmail_quote">On Tue, Jul 29, 2008 at 5:20 PM, Adam <span dir="ltr"><<a href="mailto:cisco@adman.net">cisco@adman.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">I was trying to use BAT to load up a bunch of Call Pickup Groups on CUCM 6.1(2) system and ran into a not-so-slight issue. There were about five groups that had an invalid character (& or /) in the group name and those errored out during the BAT import. This wouldn't be an issue, except that it appears that BAT "half" imported them. If I search for them under Call Pickup Groups they don't show up, however they're hidden in the dial plan somewhere. If I try and do a route plan report it gives an "unmapped exception null" error and shows nothing. The strangest part is if I click on the view in file button it exports a CSV file and they show up there as call pickup groups. I'm going to open a TAC case tomorrow once I get back on site as I cannot get the server serial number (a different CUCM 6.x bug!). I figured I would post here to see if anyone had come across this, or had any ideas to try.<br>
<br>Thanks,<br>Adam<br></div>
</blockquote></div><br></div>