Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

ICM 7.2.4 CTI Server failover

The following ICM 7.2.4 setup:

CCM PG with CTI Server A and B side geographically separated, with 2 separate networks for visible and private LAN.

Failover using ICM service control stop/start, killing dos boxes of icm processes all work ok. However unplugging the visible network cable on e.g. A side results in PG pim and jtapigw processes to become active on the B side, but NOT the CTI server process on the B side.

ICM setup on A and B side with settings like

PG private: xxxpg03ap, xxxpg03bp

CG private: xxxpg03ap, xxxpg03bp

CG visible: xxxpg03a, xxxpg03b

which result in a CG registry key with

CGPrivateInterfaceA/B: xxxpg03ap, xxxpg03bp

CGPublicInterfaceA/B: xxxpg03a, xxxpg03b

and

PGPrivateInterfaceA/B: xxxpg03ap, xxxpg03bp

PGPublicInterfaceA/B: xxxpg03ap !!!, xxxpg03bp !!!

and the same on the B side

On another platform with similar setup (but v7.1.5) the values are

on the A side

PGPublicInterfaceA/B: xxxpg03a, xxxpg03a !!!

and on the B side

PGPublicInterfaceA/B: xxxpg03b !!!, xxxpg03b

Can somebody explain to me what the values means and what they should be ?

I tried about every combination of private and visible ip# in the registry, but it did not solve the issue.

Network settings are according to Cisco ICM windows staging spec.

Any ideas ?

Thanks

4 REPLIES
Green

Re: ICM 7.2.4 CTI Server failover

Well, the first ones you marked with !! appear to be wrong. Surely the public interface has to be:

A side:

(A) xxxpg03a and (B) xxxpg03b.

B side:

(A) xxxpg03a and (B) xxxpg03b.

The 7.1.5 looks wrong too.

A side:

PGPublicInterfaceA/B: xxxpg03a, xxxpg03b

B side:

PGPublicInterfaceA/B: xxxpg03a, xxxpg03b

Regards,

Geoff

New Member

Re: ICM 7.2.4 CTI Server failover

Hi Geoff

The thing is that these (wrong) values are set by the icm setup !

I modified the registry into what I thought are the correct settings but it did not make a difference.

Regards

Green

Re: ICM 7.2.4 CTI Server failover

Peter,

Do you mean you ran ICM setup with correct values and it puts those incorrect values in there? That's pretty hard to believe.

Did you run it again and double check?

Regards,

Geoff

New Member

Re: ICM 7.2.4 CTI Server failover

yes !!!

I ran ICM setup several times, always the same result.

I ran setup with garbage then with correct values, deleted registry, deinstalled SR4, reinstalled SR4, etc.

Very weird.

But even with the correct values put in the registry manually, the failover fails when unplugging network cables. Failover with process stop/start is ok.

617
Views
0
Helpful
4
Replies
CreatePlease to create content