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

Inter Cluster trunk calls not happening

Hello Experts,

I made a intercluster trunk ( non gatekeeper controlled) between call manager clusters.


Created

New Device Pool

New Region

Route Group (Trunk)

Route List

Route pattern.

I went to the DNA and here is the output;

      Cisco Unified Communications Manager Dialed Number Analyzer Results


    * Results Summary
          o Calling Party Information
                + Calling Party = 6991
                + Partition =
                + Device CSS =
                + Line CSS = CSS_International
                + AAR Group Name =
                + AAR CSS =
          o Dialed Digits = 6006
          o Match Result = RouteThisPattern
          o Matched Pattern Information
                + Pattern = 600X
                + Partition = Part_Internal
                + Time Schedule =
          o Called Party Number = 6006
          o Time Zone = Greenwich Standard Time
          o End Device = SAT-TCF-RL
          o Call Classification = OffNet
          o InterDigit Timeout = NO
          o Device Override = Disabled
          o Outside Dial Tone = NO
    * Call Flow
          o TranslationPattern :Pattern=
                + Positional Match List = 6006
                + Calling Party Number = 6991
                + PreTransform Calling Party Number =
                + PreTransform Called Party Number =
                + Calling Party Transformations
                      # External Phone Number Mask = NO
                      # Calling Party Mask =
                      # Prefix =
                      # CallingLineId Presentation =
                      # CallingName Presentation =
                      # Calling Party Number = 6991
                + ConnectedParty Transformations
                      # ConnectedLineId Presentation =
                      # ConnectedName Presentation =
                + Called Party Transformations
                      # Called Party Mask =
                      # Discard Digits Instruction =
                      # Prefix =
                      # Called Number =
          o Route Pattern :Pattern= 600X
                + Positional Match List = 6006
                + DialPlan =
                + Route Filter
                      # Filter Name =
                      # Filter Clause =
                + Require Forced Authorization Code = No
                + Authorization Level = 0
                + Require Client Matter Code = No
                + Call Classification =
                + PreTransform Calling Party Number = 6991
                + PreTransform Called Party Number = 6006
                + Calling Party Transformations
                      # External Phone Number Mask = NO
                      # Calling Party Mask =
                      # Prefix =
                      # CallingLineId Presentation = Default
                      # CallingName Presentation = Default
                      # Calling Party Number = 6991
                + ConnectedParty Transformations
                      # ConnectedLineId Presentation = Default
                      # ConnectedName Presentation = Default
                + Called Party Transformations
                      # Called Party Mask =
                      # Discard Digits Instruction = None
                      # Prefix =
                      # Called Number = 6006
          o Route List :Route List Name= SAT-TCF-RL
                + RouteGroup :RouteGroup Name= SAT-TCF-RG
                      # PreTransform Calling Party Number = 6991
                      # PreTransform Called Party Number = 6006
                      # Calling Party Transformations
                            * External Phone Number Mask = Default
                            * Calling Party Mask =
                            * Prefix =
                            * Calling Party Number = 6991
                      # Called Party Transformations
                            * Called Party Mask =
                            * Discard Digits Instructions =
                            * Prefix =
                            * Called Number = 6006
                      # Device :Type= InterClusterTrunk-NonGatekeeperControlled
                            * End Device Name = SAT-TCF-CLUSTER
                            * PortNumber = 0
                            * Device Status = UnKnown
                            * AAR Group Name =
                            * AAR Calling Search Space =
                            * AAR Prefix Digits =
                            * Inbound Fast Start = Disabled
                            * Outbound Fast Start = Disabled
                            * Call Classification = Use System Default
                            * Tunneled Protocol = None
                            * Calling Party Transformations
                                  o PreTransform Calling Party Number = 6991
                                  o Calling Party Selection = Originator
                                  o Calling Party Presentation = Default
                                  o CallerID DN =
                                  o Calling Party Number = 6991
    * Alternate Matches
          o Note: Information Not Available


NOTE: The analysis results are purely based on configurations available in the Cisco Communications Manager database. For Gateway outbound calls, call

details might differ depending on the Gateway's settings.

Help will be highly appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Inter Cluster trunk calls not happening

OK, but you don;t mention what's the behavior.

You get the "you call cannot be completed..."?

Phone rings but then stops?

Doesn't ring?

Do you add or remove whatever digits are needed to call the other end?

An ICT could be wrong on either side and this affects calls, have you checked the other side??

Correct inbound CSS?

Correct call routing if using prefixes or any other DN transformations?

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
4 REPLIES
Cisco Employee

Re: Inter Cluster trunk calls not happening

OK, but you don;t mention what's the behavior.

You get the "you call cannot be completed..."?

Phone rings but then stops?

Doesn't ring?

Do you add or remove whatever digits are needed to call the other end?

An ICT could be wrong on either side and this affects calls, have you checked the other side??

Correct inbound CSS?

Correct call routing if using prefixes or any other DN transformations?

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
Community Member

Re: Inter Cluster trunk calls not happening

Thanks Java for your response.

There was no ringing...

Yeah I added digit to call other site.

Yeah configured CSS on both sides (wrong one).

Well I got it working here is some troubleshooting ....

Calls from Cluster B Office to Cluster A:

it was giving TCP communication error, strange thing is I had mentioned subscriber IP Address in the remote call manager in ICT configuration page. But Cluster A Call Manager Cluster was not accepting call setup from it. I removed IP Address, saved and put the same IP again. And it started working.

CCM traces:

06/06/2010 19:08:13.884 CCM|H225Handler::SdlConnectionInd, rejecting the TCP connection from IP=10.112.211.201. Incoming H225 call on Port=1720, can't find this port in the registered H323 endpoints port list.

Calls from Cluster A to Cluster B:

The IP Phone(test Phone) partition was not included in the CSS that I specified in the trunk config.

06/06/2010 20:29:22.086 CCM|Digit analysis: wait_DmPidErr - Name=Unregistered Pid=(0,0,0)

06/06/2010 20:29:22.086 CCM|Digit analysis: wait_DmPidErr: dialingPartition=[410129cb-cb8b-7e5c-86d1-beb774c36c46] dialingPattern=[6919] dialingWhere=[], PID=(0,0,0)

Cluster B's route plan report showed 2 entries for 6919, one in Part_EM the other in Part_Internal.  The original digit analysis showed the following:

06/06/2010 20:29:22.085 CCM|Digit analysis: match(pi="2", fqcn="", cn="6001",plv="5", pss="Part_EM:Part_Internal:VMPilotNumberPT:VMRestrictedPT:Part_National:Part_Mobile:Part_Local:Part_TollFree:Part_Emergency:Part_E1_EM:Part_E1_Emergency:Part_PMT_Local:Part_E1_Mobile:Part_E1_National:Part_E1_Toll_Free_calls:Part_International:Part_E1_International:Part_E1_Tollfree2:huntpilot_partition:Part_STC_Helpline:Part_TollFree2:Airline_Part", TodFilteredPss="Part_EM:Part_Internal:VMPilotNumberPT:VMRestrictedPT:Part_National:Part_Mobile:Part_Local:Part_TollFree:Part_Emergency:Part_E1_EM:Part_E1_Emergency:Part_PMT_Local:Part_E1_Mobile:Part_E1_National:Part_E1_Toll_Free_calls:Part_International:Part_E1_International:Part_E1_Tollfree2:Part_STC_Helpline:Part_TollFree2:Airline_Part", dd="6919",dac="0")

Note that after "pss=" Part_EM is first in the list thus CUCM tried to route the call to EM device profile not the actual phone.  I removed this partition from CSS used by ICT, we retested and the call  6001 to 6919 completed properly.

I will put a complete document for ICT so other dont get stuck as I got

Thanks & Regards,

Mudasir Abbas

Community Member

Re: Inter Cluster trunk calls not happening

Hi.

I see you got this working, but I think the error (rejecting the TCP  connection from IP=10.112.211.201. Incoming H225 call on Port=1720,  can't find this port in the registered H323 endpoints port list) really points directly to misconfigured Device Pool/CCM Group.

Check out the SRND:

"It is important to configure a corresponding intercluster trunk (non-gatekeeper controlled) that has a Unified CM Group containing the same servers that were defined as remote Unified CM servers in the first cluster. A similar configuration is required in each Unified CM cluster connected by the intercluster trunks."

Cheers,

Tore

Re: Inter Cluster trunk calls not happening

That was huge....  I was doing testing and couldnt figure out why CSIM start would not work...  well, the dial peer was pointing to a CUCM server that was not in the Device Pool of the Gateway....   bah!  thanks for the tip!

2986
Views
5
Helpful
4
Replies
CreatePlease to create content