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

Strange CM call routing

I've got a very simple lab setup. A single Publisher running 4.1(3) with two phones. Each phone is assigned a single line (one has 2973, the other 2974). Initially, both phones were using Default CSS and partition. Either could call eachother fine. There are absolutely no other Route Patterns or Translation Patterns configured.

I then added three partitions:

Demo-Internal-PT

Demo-Local-PT

Demo-LD-PT

And the CSS "Demo-Unrestricted" with all three partitions.

I then assigned the phones the Demo-Unrestricted CSS and each line to the Demo-Internal-PT.

Now the weirdness. DNA shows that each phone should be able to call eachother (see attachment). However, whenever either phone attempts to call the other, it gets a re-order after dialing the first digit '2'. The following is in the SDL trace:

CI=16777277 Fqdn=2973 Cgpn=2973 Number= requestID=8490197 DigitAnalysisComplexity=0

CI=16777277 Block ForegoPotentialMatches OnNetrequestID =8490197

CI= 16777277 pi.piid=30 pi.l=0

CI= 16777277 pi.piid=30 pi.l=0

CI= 16777277 pi.piid=30 pi.l=0

CI= 16777277 pi.piid=30 pi.l=0

Tone=InsideDialTone Direction=0 Line=1 CI=16777277

CallState = overlap_sending2

KeypadButton=2 Line=1 CI=16777277

KeypadButton=2 Line=1 CI=16777277

CI=16777277 Line=1

Line=1 CI=16777277 SKIndex=6 Mask=ffffffff

CI=16777277 Fqdn=2973 Cgpn=2973 Number=2 requestID=0 DigitAnalysisComplexity=0

CI=16777277 Block NoPotentialMatchesExist OnNetrequestID =0

I have re-booted the server and restarted both phones, but I keep getting the same results.

Any Suggestions?

1 ACCEPTED SOLUTION

Accepted Solutions
Green

Re: Strange CM call routing

Hi,

10/18/2006 19:50:21.584 CCM|StationInit: (0000009) SoftKeyEvent softKeyEvent=2(NewCall)

10/18/2006 19:50:21.584 CCM|Digit analysis: match(pi="1",fqcn="2973", cn="2973", plv="5", pss="NULL", TodFilteredPss="NULL", dd="",dac="0")|<:STANDALONECLUSTER><:IT-DEMO-CCM01><:1><:10.1.10.4><:SEP0008026324F7>

pss="NULL"

You are hitting:

CSCsa96655

Change of CSS assigned to a device requires a restart of CM service

Symptom:

Calls result in reorder tone after first digit is dialed.

Condition:

This has been observed with CallManager version 4.1(3) when a changing the CSS assigned to a device. For example:

1. Phone A can call Phone B

2. Phone A is assigned CSS (Test). The Test CSS contains the partition assigned to the DN for Phone B.

3. Create a new CSS called Test1. Assign the same partitions to Test1 that is assigned to Test.

4. Assign this Test1 CSS to Phone A.

5. When Phone A tries to call Phone A, Phone A user will hear reorder/Annunciator after the first digit dialed.

6. CCM detailed trace will show that the PSS assinged to Phone A is not Test1 but it is "NULL"

Workaround:

Restart the Cisco CallManager service on all nodes.

It is fixed in 4.1.3SR1, go ahead and apply latest SR available in CCO.

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-41

3 REPLIES
Green

Re: Strange CM call routing

We need CM traces showing the dialing forest To generate the dialing forest from each phone, please do the following:

To dump the dialing forest, please dial the codes as follows:

- Go off hook, dial **##*2 (get busy signal), hang up

- Go off hook, dial **##*4 (get busy signal), hang up

Upload ccm trace detailed also to see Partitions in CSS.

Since its a lab apply latest SR.

New Member

Re: Strange CM call routing

Hi, I'm now attaching CCM and SDL detailed traces while doing the above.

Green

Re: Strange CM call routing

Hi,

10/18/2006 19:50:21.584 CCM|StationInit: (0000009) SoftKeyEvent softKeyEvent=2(NewCall)

10/18/2006 19:50:21.584 CCM|Digit analysis: match(pi="1",fqcn="2973", cn="2973", plv="5", pss="NULL", TodFilteredPss="NULL", dd="",dac="0")|<:STANDALONECLUSTER><:IT-DEMO-CCM01><:1><:10.1.10.4><:SEP0008026324F7>

pss="NULL"

You are hitting:

CSCsa96655

Change of CSS assigned to a device requires a restart of CM service

Symptom:

Calls result in reorder tone after first digit is dialed.

Condition:

This has been observed with CallManager version 4.1(3) when a changing the CSS assigned to a device. For example:

1. Phone A can call Phone B

2. Phone A is assigned CSS (Test). The Test CSS contains the partition assigned to the DN for Phone B.

3. Create a new CSS called Test1. Assign the same partitions to Test1 that is assigned to Test.

4. Assign this Test1 CSS to Phone A.

5. When Phone A tries to call Phone A, Phone A user will hear reorder/Annunciator after the first digit dialed.

6. CCM detailed trace will show that the PSS assinged to Phone A is not Test1 but it is "NULL"

Workaround:

Restart the Cisco CallManager service on all nodes.

It is fixed in 4.1.3SR1, go ahead and apply latest SR available in CCO.

http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-41

371
Views
0
Helpful
3
Replies
CreatePlease to create content