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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Upgraded 3.13 box to K9.2000-2-4.exe and witnessed strange changes

Hi All,

I currently upgraded a Callmanager version 3.13

to the latest patch levels.

see below

###Current CM Patch level as at 2/8/03###

win-OS-Upgrade-K9.2000-2-4.exe

win-K9-MS03-026.exe

SQL7-ServicePack4.1-0-2.exe

SQL7-MS02-061.exe

win-OS-Upgrade-k9.2000-2-4sr5.exe #####available on CCO 1/8/2003####

Windows 2000 Hotfix Validation Report for \\XXReport Date: 8/2/2003 2:05pm

Current Service Pack Level: Service Pack 3

Hotfixes Identified:

Q282784: Current on system.

Q282522: Current on system.

KB817606: Current on system.

KB822679: Current on system.

q323172: Current on system.

Q323255: Current on system.

Q324380: Current on system.

Q326830: Current on system.

Q326886: Current on system.

Q327696: Current on system.

Q327752: Current on system.

Q328310: Current on system.

Q329115: Current on system.

Q329170: Current on system.

Q329834: Current on system.

Q331953: Current on system.

Q810833: Current on system.

Q811114: Current on system.

Q811493: Current on system.

Q814119: Current on system.

Q815021: Current on system.

Q816036: Current on system.

Q816998: Current on system.

KB823559: Current on system.

KB823980: Current on system.

After completion I did some testing and was unable to use Software conference bridge and Music on hold was not working. : (

I made a call and hit The ? button to find the region had been changed after upgrade and was g729

So I changed it back to G.711 Now CB and MOH working again as expected.

Has any one else witnessed this ?

Also im making some test calls and RxSize is fluctuating between 20ms and 10ms this is also strange behavior That i havent seen before.

Service P is fixed at 20ms for 711 2 x voice sample per packet.

The last issue I have noticed is I dial numbers hangup and try use redial and get fast busy also strange .

Perhaps there are other suttlties I've missed we will see what happens under some load come Monday.

Any explanations welcomed ?

Never expect a smooth ride plan for the PERFECT STORM!!!!

6 REPLIES
New Member

Re: Upgraded 3.13 box to K9.2000-2-4.exe and witnessed strange c

More problems reported first thing this morning today.

I was unable to test outgoing calls at remote site after the update for various reasons.

######PROBLEM########

Users at remote site unable to place outgoing calls PSTN.

Trace suggests no pottential match exits which is incorrect users get fast busy after dialing any digit except internal.

The remote site connects back over the wan and I have placed it into permanent fallback mode to enable operational service (in/out calls) for an interim solution.

Tonight after hours I will investigate further.

I've spoken with and old associate of mine who experienced the same issue after installing K9.2000-2-4.exe He said he edited a route pattern(1) and updated and this resolved the problem Has anyone else experienced any problems after this upgrade K9.2000-2-4.exe ?

New Member

Re: Upgraded 3.13 box to K9.2000-2-4.exe and witnessed strange c

allan, u should've made the effort to check if CM 3.1.3 is compatible with K9.2000-2-4 from the CM compatability matrix. From whats stated in the matrix, CM 3.1.3 is not compatible in the least. You should've upgraded it to CM 3.1.4b 1st, then the latest OS.

I would advise you open a TAC case since ur current situation seems dire.

sean.

New Member

Re: Upgraded 3.13 box to K9.2000-2-4.exe and witnessed strange c

Yes you are correct a massive oversight I should have done

The situation is not quite dire though could be better.I could rip the drive and upgrade and see what a 3.14 upgrade does to the box.

I read the patch release document which suggests that it is compatable all releases of CM 3.0,3.1 etc !!!!

Cisco validated this operating system upgrade for use with all releases of Cisco CallManager 3.0, 3.1, 3.2, 3.3

Yes I didnt read the matrix !!!!

So the situation is bad but though i think recoverable sti backup has packed it in as well perhaps the box will self destruct.

New Member

Re: Upgraded 3.13 box to K9.2000-2-4.exe and witnessed strange c

This is not good if you look at the release notes for the patch it say it supports all version of CM even 3.0.

So Cisco have posted conflicting information.

How hard would it be to have a perl script run and check the version of CM and proceed with upgrade if criteria is met.

New Member

Re: Upgraded 3.13 box to K9.2000-2-4.exe and witnessed strange c

Updating the route pattern fixed the problem in previous post at remote site.

Now hopefully someone can answer this one before the tac gets it!!!

When pressing redial button after successfully dialing a number and hanging up.i press redial and phones get fast busy

###################################################

Though say I make a call to an internal number going out the pstn hang up and press redial it works and only then do I get

08/04/2003 19:06:21.722 Cisco CallManager||PretransformCallingPartyNumber=59325

|CallingPartyNumber=59325

|DialingPartition=GeorgeStLocal

|DialingPattern=0.[2-9]XXXXXXX

####A successful scenario is InternalPhone---e1---telco----e1---Internalphone###

So here is the trace from a both a failure and successfull call.remembering all numbers can be dialed redial is the issue.

FAILURE!!!!!!!

08/04/2003 19:09:48.930 Cisco CallManager|StationInit: 565fa5c Stimulus stimulus=1(LastNumberRedial) stimulusInstance=1.|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|StationD: 565fa5c SetSpeakerMode speakermode=1(On).|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|<:AUAPS002-CLUSTER><:XXX><:1><:DIRECTORY number=""><:59325><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|StationD: 565fa5c SetLamp stimulus=9(Line) stimulusInstance=1 lampMode=2(LampOn).|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|StationD: 565fa5c CallState callState=1(OffHook) lineInstance=1 callReference=16780789|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|StationD: 565fa5c DisplayPromptStatus timeOutValue=0 promptStatus='Enter number' lineInstance=1 callReference=16780789.|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|StationD: 565fa5c SelectSoftKeys instance=1 reference=16780789 softKeySetIndex=4 validKeyMask=-1.|<:AUAPS002-CLUSTER><:XXXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|StationD: 565fa5c ActivateCallPlane lineInstance=1.|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|Insert an entry into CiCcp table, now this table has 1 entries|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|Insert an entry into CiCcp table, now this table has 2 entries|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|Digit analysis: match(fqcn="59325", cn="59325", pss="GeorgeStLocal:GeorgeStSTD:GeorgeStInternal:GeorgeStIDD", dd="0041xxxxx8#")|<:AUAPS002-CLUSTER><:XXXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|Digit analysis: potentialMatches=NoPotentialMatchesExist|<:AUAPS002-CLUSTER><:XXXXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|EnvProcessCdr::wait_DbCdrReq|<:AUAPS002-CLUSTER><:XXXXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.945 Cisco CallManager|<:AUAPS002-CLUSTER><:XXXX><:1><:DIRECTORY number=""><:59325><:SEP000750AC6CCD>

08/04/2003 19:09:48.961 Cisco CallManager|StationD: 565fa5c StartTone tone=37(ReorderTone).|<:AUAPS002-CLUSTER><:XXX><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:09:48.961 Cisco CallManager|EnvProcessCdr::insertCdrRecord Insert-Successful CallingPartyDn: 59325 CalledPartyDn: 00413xxxxx8# DateTimeDisconnect: 1059988188 DestNodeID: 0 GlobalCallManagerId: 1 GlobalCallId:

Success!!!!!!!

08/04/2003 19:06:21.722 Cisco CallManager|StationInit: 565fa5c Stimulus stimulus=1(LastNumberRedial) stimulusInstance=1.|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|StationD: 565fa5c SetSpeakerMode speakermode=1(On).|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|<:AUAPS002-CLUSTER><:><:1><:DIRECTORY number=""><:59325><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|StationD: 565fa5c SetLamp stimulus=9(Line) stimulusInstance=1 lampMode=2(LampOn).|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|StationD: 565fa5c CallState callState=1(OffHook) lineInstance=1 callReference=16780781|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|StationD: 565fa5c DisplayPromptStatus timeOutValue=0 promptStatus='Enter number' lineInstance=1 callReference=16780781.|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|StationD: 565fa5c SelectSoftKeys instance=1 reference=16780781 softKeySetIndex=4 validKeyMask=-1.|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|StationD: 565fa5c ActivateCallPlane lineInstance=1.|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|Insert an entry into CiCcp table, now this table has 1 entries|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|Insert an entry into CiCcp table, now this table has 2 entries|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|Digit analysis: match(fqcn="59325", cn="59325", pss="GeorgeStLocal:GeorgeStSTD:GeorgeStInternal:GeorgeStIDD", dd="082359314")|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager|Digit analysis: analysis results|<:AUAPS002-CLUSTER><:><:1><:10.249.7.14><:SEP000750AC6CCD>

08/04/2003 19:06:21.722 Cisco CallManager||PretransformCallingPartyNumber=59325

|CallingPartyNumber=59325

|DialingPartition=GeorgeStLocal

|DialingPattern=0.[2-9]XXXXXXX

|DialingRoutePatternRegularExpression=(0)([2-9]XXXXXXX)

|DialingWhere=

|PatternType=Enterprise

|PotentialMatches=NoPotentialMatchesExist

|DialingSdlProcessId=(1,89,1)

|PretransformDigitString=082359314

|PretransformTagsList=ACCESS-CODE:SUBSCRIBER

|PretransformPositionalMatchList=0:82359314

|CollectedDigits=082359314

|UnconsumedDigits=

|TagsList=ACCESS-CODE:SUBSCRIBER

|PositionalMatchList=0:82359314

Blah blah the call connects...

New Member

Re: Upgraded 3.13 box to K9.2000-2-4.exe and witnessed strange c

Cisco TAC has advised that it is supported on 3.13!!!

149
Views
0
Helpful
6
Replies