[cisco-voip] Best Way To Bulk Update Lines/Directory Numbers?

[Pete Brown]

Haven’t tested it past 12.0, but I posted a GUI tool for running AXL SQL queries.

https://www.adhdtech.com/CUCM%20AXL%20Query.exe


From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Gary Parker
Sent: Monday, June 12, 2023 10:16 AM
To: NateCCIE <nateccie at gmail.com>
Cc: voip puck <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Best Way To Bulk Update Lines/Directory Numbers?

Brilliant, thanks Nate. I can build the command lines in the spreadsheet I hold the data in. Nice one.

Gary

From: NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>>
Date: Monday, 12 June 2023 at 15:08
To: Gary Parker <G.J.Parker at lboro.ac.uk<mailto:G.J.Parker at lboro.ac.uk>>
Cc: voip puck <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Best Way To Bulk Update Lines/Directory Numbers?

** THIS MESSAGE ORIGINATED OUTSIDE LOUGHBOROUGH UNIVERSITY **

** Be wary of links or attachments, especially if the email is unsolicited or you don't recognise the sender's email address. **
SQL is the way to go here.

Super easy to dump the commands into the cli, “run sql update numplan set fkroutepartition = ‘newguid’ where dnorpattern = ‘extension’”

Call forward can be set the same way, but I don’t have that memorized still.
Sent from my iPhone

On Jun 12, 2023, at 6:41 AM, Gary Parker <G.J.Parker at lboro.ac.uk<mailto:G.J.Parker at lboro.ac.uk>> wrote:

Hi folks, I’m migrating users from CUCM to Teams Phone and need to update:

  1.  Route Partition
  2.  Forward All Destination
for a specific set of directory numbers that cannot be identified with a search based on CUCM data. The partition change will be to identify migrated numbers, the cfwdall will be to send calls out to a voice gateway that then sends the call to our Teams tenant via SIP.

It looks like I can do the Route Partition with an export/update line appearance job, so that’s good/simple.

The call forward details will be different for each line. If the DN is 123456, the cfwdall will be to 901509123456, so this must be done with a custom file.

If I do Phones -> Export Phones -> All Details’ I can see the call forward details for the lines on those phones in there, but there doesn’t seem to be a way to import that data back in as an update, only as ‘Phones -> Insert Phones’ for new devices.

I could delete the existing phones I want to update, then Insert the modified entries back again as new phones, but I’m worried what other interactions that may break.

The other option seems to be to do a full ‘Export -> Device Data -> Phone’ for the database tar file, edit the required lines, then Import again, but as you have to do the whole database that is very time consuming and also, I’d imagine, service affecting?

I explored the option in the past of trying to forward calls placed to a line in the migrated partition using a transformation pattern but could not get this to work (I believe I posted about it on this list).

If anyone has an alternative suggestion for achieving the call forwarding I’d love to hear it.

Is there a way to forward calls from all the DNs to a kind of pilot number that then forwards again to a new destination based on the forwarding station? So, say for example, I forward calls from 635635 to 222222, some logic on 222222 forwards the call to 901509635635; and for calls to 222333, forward to 222222, which then forwards to 901509222333

--
Gary Parker
Unified Communications Service Manager
Loughborough University, IT Services
Phone - +441509635635<tel:+441509635635>
Teams - g.j.parker at lboro.ac.uk<callto:g.j.parker at lboro.ac.uk>
https://www.osx.ninja/pubkey.txt

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20230612/0345cff9/attachment.htm>