Devices Unregister on CM

[Neily]

We are having lots of problems with devices unregistering on our call managers.

Even the MOH server (which is on the call manager) unregisters!

We get various reasons including: TCP-Timeout; Failback; Phone Keypad; CM-aborted-TCP

Has anyone got any ideas as too why?

THANKS

 

[jneiberger]

What version of CallManager is this? On what platform? Have you been monitoring the server itself to make sure it isn't overloaded? Have you verified that you have no network-related issues, perhaps layer two issues on the switch local to the CallManager, or maybe some sort of routing issue?

 

[Neily]

CCM4.1(2) On an HP Cisco certified Windows 2k server.

Our network seems fine for all other uses (and we use it a lot!) but since installing CM 6 months ago.

We are checking our network, but I am wondering if there are any other things that could cause it.

The whole setup seems wrong and the man that did our config has been sacked but we can't afford to get this replaced/reinstalled!

THANKS

 

[jneiberger]

Don't you have SMARTnet? You should just open up a ticket with Cisco. This isn't the sort of thing you want to let go on for very long or your users will revolt.

 

[Neily]

We've got a company who supports us, though they aren't currently being of much help!

 

[jneiberger]

Can they open up a ticket with Cisco for you?

 

[Neily]

I think they already have!

Cisco said not support config or something!

 

[jneiberger]

I don't understand what you mean.

 

[Neily]

well alot of our devices are IP Communicator 1.1.5 running on CCM 4.1(2) with IPCC 3.

Apparently this is unsupported!

 

[jneiberger]

Interesting. Did Cisco tell you what you'd need to do to get support? In other words, what must you do to get this to be a supported configuration?

 

[Neily]

I believe it is just because of our IPCC servers not being on version 4 (which we are getting upgraded soon!)

Are you not aware of this then?

Would be a nice way for us to get some free stuff or something else from our support co

 

[jneiberger]

I'm not very familiar with IPCC or IP Communicator, so I wasn't sure what the latest releases were. It seems like the company you pay for service isn't doing a very good job. I don't understand how an old version of IPCC would make all of your other devices unregister periodically. They are unrelated, so Cisco should be able to help you.

If I were you, I would pressure your support company for some real support.

 

[CharlesNY]

CallManager 4.1(2)SR1
IP Communicator 1.1(5)
IPCC Express 3.5(2)

These are supported by Cisco. Check out the

Cisco CallManager Compatibility Matrix

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm

What kind of CPU and memory do you have? I believe your system does not have enough horse power to run all those.

Charles

 

[Neily]

Hi CharlesNY thanks for the reply,

The machines running IP Communicator are running 512Mb each.

The servers are:

Publisher = 1.5Gb; P4 3.06GHz
Subscriber = 1.5Gb; P4 3.06GHz
IPCC 1 = 3.5Gb; Xeon 3.4GHz
IPCC 2 = 3.5Gb; Xeon 3.4GHz

All are HP Servers

THANKS

 

[CharlesNY]

Your servers seems to have enough CPU/Memory. Next question would be how many total users do you have ? this includes users using IP communicator and users using IP phones (if any).

with your systems configuration, it should support at least 500 phones/IP communicators.

When the MOH unregisters, does the IP communicators unregister at the same time? Does this happen often? like once a day? Would you be able to check the CPU utilization when the MOH unregisters? Are there any IP communicators that "did not get unregister" are they any broadcast/multicast traffic on the server network?

I would look into high CPU utilization on the CCM or if there is a network problem. But the network problem will not cause the MOH to unregister unless it's high CPU or someone restart the MOH process.

Charles

 

[Neily]

We have between 150 and 200 users.

Devices unregister randomly. So MOH may go now but all other phones would be fine. Then say an hour later one IP Communicator would unregister.

It looks (having just looked at event logs) like a device unregisters around every 20 or 30 mins, through out the day.

We are keep being told its a 'Network Issue' but as we don't use Cisco switched they won't help us!

I have just noticed that one of the NICS is CCM2 (Subscriber) is offline and keeps going on and off.

Maybe this would cause it??

 

[pndscm]

Do you have your NIC's hard coded for speed and duplex? Also hard code your switch ports to match. They may be trying to auto negotiate speed and duplex.

 

[jneiberger]

Actually, it would be unwise to hard code your speed and duplex unless you absolutely have to. The safest setting is to leave your servers and switches set to AUTO, especially if you're using Cisco switches made in the last five years.

Besides, this type of negotiation only happens when the link first comes up. It doesn't happen more than once unless the link itself flaps.

John

 

[Neily]

I'm actually going to check the cabling for this tonight so will up date after that!

 

[pndscm]

Why not hard code speed and duplex on servers? I have seen these auto negotiate to 100 half.
For years Cisco has said if you have 2 devices that can auto negotiate, hard code at least one of them. And Neily states that they are NOT using Cisco switches.