Moving CME/CUE to new subnet

Answered Question
Mar 31st, 2009

I am moving a CME/CUE to a new subnet. The dial plan stuff all remains the same. Should just changing the IPs in the config for CME and CUE do the trick? Or might there be other considerations? Thanks.

I have this problem too.
0 votes
Correct Answer by Nicholas Matthews about 7 years 8 months ago

This is the way I like doing readdressing on CUE/CME:

Grab your CME file into a .txt file. Do a find/replace with your new addressing.

Then use the 'config replace ' command. The easiest place is to save your edited configuration on a TFTP/FTP server and just upload it from there. It will dynamically swap your config out without losing connectivity. It's pretty sweet.

There are some things that you still need to change manually. Such as:

-'sccp ccm' addresses. This requires taking it out of the sccp group, deleting it, adding a new address, and putting it back in the group. Take note of this if you're using transcoding/conferencing/analog FXS.

-CUE doesn't support this, as it's a different platform.

If your CUE uses a totally different subnet than your CME source address, you may be able to get away without readdressing CUE. If you do need to address you will want to pay attention to:

-'gateway address' under 'ccn subsystem sip'

-services URL voice voiceview

-ntp server references

-service module interface reference and /32 ip route statement

-any NAT you're doing for CME/CUE addresses.

-dial peers for AA/VM

Happy hunting!

hth,

nick

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Nicholas Matthews Tue, 03/31/2009 - 18:50

This is the way I like doing readdressing on CUE/CME:

Grab your CME file into a .txt file. Do a find/replace with your new addressing.

Then use the 'config replace ' command. The easiest place is to save your edited configuration on a TFTP/FTP server and just upload it from there. It will dynamically swap your config out without losing connectivity. It's pretty sweet.

There are some things that you still need to change manually. Such as:

-'sccp ccm' addresses. This requires taking it out of the sccp group, deleting it, adding a new address, and putting it back in the group. Take note of this if you're using transcoding/conferencing/analog FXS.

-CUE doesn't support this, as it's a different platform.

If your CUE uses a totally different subnet than your CME source address, you may be able to get away without readdressing CUE. If you do need to address you will want to pay attention to:

-'gateway address' under 'ccn subsystem sip'

-services URL voice voiceview

-ntp server references

-service module interface reference and /32 ip route statement

-any NAT you're doing for CME/CUE addresses.

-dial peers for AA/VM

Happy hunting!

hth,

nick

mmedwid Thu, 04/02/2009 - 05:39

It went like a charm Nick. Thanks for the reminders on the service module /32 and etc. Making changes in CUE took a long time as that system takes long pauses that look like hangs when you make a change. Also I noted that CME there were certain dependencies where you had to disassociate resources before proceeding. All worked out in the end.

Actions

This Discussion