I have a customer who has a CM rele

[twlcolorado]

I have a customer who has a CM release 6.3 with a main, an ESS and 5 LSPs. Right now all registrations for IP phones are going to CLAN cards, and they want to change that to using the PROCR. Right now on the main location H.323 Registration is set to n. I know that I have to change that to y, and also change MCIPADD in DHCP rule to the IP address of the PROCR.

Here are my questions.

In order to change the PROCR, it needs to be busied out. What effect will that have on the System (We have SIP to voicemail and a few conference phones ... I am guessing they will quit working for a bit, but don't know what else will)?

Once these changes are made, will the IP phones immediately re-register to the PROCR (This is a city government, including law enforcement, and if that happens we will need to set up a maintenance window)?

Also, my ESS has both the H.323 and H.248 Registration fields set to n. Should both of these be yes (all of the LSP locations have both fields set to yes)?

Thanks

 

[kyle555]

Hard to say without seeing the network. Got H248 gateways? Those need to be rearranged to procrs instead of clans. And your recovery/transition points need to be set too if youre sending gateways to procr. You may have had a mgc list of CLAN1 and CLAN2 at site 1 and CLAN3 at the ESS site which would need a transition point of 2 to keep both CLAN1+2 as "not in failover" but with procr, a transition point of just 1 would be appropriate. Were you to have transition point 2 and change the mgc list to procr core and procr ess, your h248 gateways would never fail back from ess because they'd not see themselves in a failedover state.

If you've had the system for a while, what other adjuncts like CDR, SIP signaling, Session Manager, CTI links, CMS etc. Figure those out

Then, what does your IP network map look like? Phones will inherit the region of the subnet in the network map if present. If not, it they inherit the region of the gatekeeper they registered to (the CLAN, or now procr). You wouldn't want all the phones to drop themselves to location 1 because the network map is empty and you put them on procr.

What does your procr interface look like now? Is it "disabled and nothing uses it" or "enabled for SIP stuff but not H323 sets or h248 gateways"? If you're using it for absolutely nothing, then whatever you're doing is through CLANs anyway and you wouldn't need to worry about it too much. Processor ethernet is not control network on customer lan - to say, busying out procr wouldn't take down your IPSIs connections to the CM server. Or at least I don't think so. As far as what I know about how the thing works, procr and control networks are entirely separate functions and despite being on the same interface, should be independent of one another.

CM will then load balance all active registrations across all active gatekeepers in that network region - so, if site 1/NR1 has procr in NR1 and clans in NR1, CM will balance them. You SHOULD have CM in a network region with no DSPs to have a tidy hub and spoke topology.

I also know CM sends all gatekeepers in the NR+failover ones per the network region page to phones in that region. How adding procr in a isolated NR you intend to be a replacement would be interesting. I'd plan for an outage to leave nothing to chance! But do your hub+spoke with procr while you're at it - it'll be your only chance.