Staged migration to new cluster

Unanswered Question
Feb 13th, 2014
User Badges:

Hi all,


Would appreciate your advice.


We currently run CUCM 7 in parallel with a PABX system. Calls come in over H323 gateways and if the number doesnt exist in Cisco land, the call is forwarded to the PABX.


We are looking to migrate to CUCM 9 for the purpose of simplifying config and removing unused accounts. ie. Build the 9 cluster and move users over from cucm7 in stages.


The problem is, how do you have some users in CUCM9, some in CUCM7 and some in PABX all at the same time? The dial plan is all over the place - ie there is no logical separation of users with regards to their assigned extensions.




Cheers.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Carlo Poggiarelli Fri, 02/14/2014 - 01:39
User Badges:
  • Green, 3000 points or more

Hi.

An idea could be to create a new voce vlan with a new dhcp scope with option 150 pointing to the ip address of the new CUCM 9 Cluster. That will allow you to migrate users just changing voice vlan on the switch port.


About the dial plan.

You should remove the migrated extension from the old system and create a route pattern to allow old user to reach migrated users extension.


Eg.

Old cluster range 3000 - 3999

You migrate a user with extension 3100

- Create a Sip trunk between old and new Cluster both on old and new cluster

- Create a route pattern 3XXX both on old and new clusters pointing to the previously created Sip Trunk

- Migrate the user with suggested method

- Remove extension 3100 from the old cluster.





HTH



Regards


Carlo





Please rate all helpful posts

"The more you help the more you learn"

rmoh66300 Fri, 02/14/2014 - 01:49
User Badges:

Hi,


Thanks for that. But not quite. That's what we're currently doing between the pabx and cucm7 cluster. The addition of a 3rd system makes the migration a little more complex.

Carlo Poggiarelli Fri, 02/14/2014 - 02:32
User Badges:
  • Green, 3000 points or more

Hi.

Not really complex.

If you consider to let icoming calls to land on new CUCM9, applying what suggested, an incoming call culd follow this path:



Incoming call

H323GW-->>CUCM9-->(if not present) --->>CUCM7-->>(if not present)--->>PABX


A call from CUCM7 Extension.


CUCM7--->>(if not present within the cluster) -->>PABX(if not present)--->>(CUCM9)


Other  calls from other cluster or PABX could follow the same flow.



HTH



Regards


Carlo



Please rate all helpful posts

"The more you help the more you learn"

Actions

This Discussion