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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Unity 4.0(1) got ''Temp fail'' on IP phone screen, when subscriber retrive

When subscriber retrieve voice mail from IP phone(79xx), if the session

continue longer than 30 seconds, then on the IP phone may show

''temp fail'' on the screen and session stop, have anyone met same problem?

thks..

5 REPLIES
New Member

Re: Unity 4.0(1) got ''Temp fail'' on IP phone screen, when subs

Append: the call manager is v3.3(2).

New Member

Re: Unity 4.0(1) got ''Temp fail'' on IP phone screen, when subs

Check your Unity event logs. See if you are seeing port lockups and or port disconnects at the same time. We had a large number of these because our Unity ports were disconnecting. We found the cause of the disconnects were due to the fact I had 16 availible ports and only 8 of them were registered to callmanager.

Gold

Re: Unity 4.0(1) got ''Temp fail'' on IP phone screen, when subs

You will see this if the Unity port that the phone is connected with deregisters from CallManager while the call is in progress. The only time I have seen this is when 2 Unity servers are trying to register with CallManager using the same name. (e.g. CISCOUM1-VI1 and CISCOUM1-VI1) Two different Unity servers should never be assigned the same port name.

Do you have failover and did you possibility assign the ports the identical name?

Thanks,

Keith

New Member

Re: Unity 4.0(1) got ''Temp fail'' on IP phone screen, when subs

From the eventlog, saw plenty 10001,112,1000,1004,101,102,103,115 errors,

from forum, maybe ''DBwalker '' is required.

This Unity is a single, no failover. thks..

New Member

Re: Unity 4.0(1) got ''Temp fail'' on IP phone screen, when subs

This seems to happen to all the CCM 3.3.2 version. We installed two these kinds system to two customers and had same problem.

We worked it out by globally disabling call waiting in CCM.(under service). If you look at event view you will see TSP port has call waiting enabled this kind of message in CCM.

This for sure is a bug from CCM 3.32. Some people also say patch c can solve this bug.

Anyway, disable call waiting for sure will fix it, but you'll lose this feature for the IP phones. Try patch c.

114
Views
0
Helpful
5
Replies
CreatePlease login to create content