CTI Route Point Failure when calling from a PSTN phone

Unanswered Question
Aug 19th, 2009
User Badges:

CTI Route Point Failure when calling from a PSTN phone but works fine when calling from an internal IP phone.



The CUCM version is:

The UCCX Version is:7.0(1)SR03_Build011

Failure Reason:


See attachments for the log of a failed call from PSTN phone and a working call from an IP Phone.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (2 ratings)
astanislaus Wed, 08/19/2009 - 22:33
User Badges:

CSS and Partitions have been elimintaed as being the reason already. These are all setup correctly.

The Voice Gateway is a Cisco 3825 and I am trying to get the show tech for that router.

I can call an IP phone from a PSTN phone without any problem, but I when I call the CTI Route Point - Route Port from a PSTN phone I get busy tone.

As I said before IP phone to the same CTI Route Point - Route Port works fine.

Riccardo Bua Thu, 08/20/2009 - 00:20
User Badges:
  • Cisco Employee,

Hi there,


CallManager believes that either

1) the number you're redirecting to is not in the dial plan or

2) the CTI Port the call is on does not have a proper Calling Search Space to allow it to "see" that number.

I highly suspect the latter. Ensure that all of your CTI Ports have the proper CSS.

If you still have issues after checking that, please open a TAC case for

further analysis.



astanislaus Thu, 08/20/2009 - 02:35
User Badges:


Since it is neither 1 or 2 I will elevate to TAC.

bastienbertout Tue, 11/09/2010 - 01:22
User Badges:


I meet the exact same problem.

Did you have any help from the TAC ?



astanislaus Tue, 11/09/2010 - 01:42
User Badges:

I will dig up my old cases and see what the resolution was, but no guarantees.

astanislaus Tue, 11/09/2010 - 14:43
User Badges:

The problem turned out to be a CSS issue (Calling Search Space Issue).

The CSS on the gateway couldn’t directly see the partition that the UCCX trigger point was in.

There was a translation pattern in between.

Once the CSS was updated to include the partition of the UCCX trigger points all worked fine.

bastienbertout Tue, 11/09/2010 - 23:52
User Badges:

Thanx a lot for taking the time to bring me this answer.

I met exactly the same problem.

Everything is working great now.




astanislaus Wed, 11/10/2010 - 01:17
User Badges:


Good to know that is fixed.

Thanks for the rating.


vicen.giles Thu, 11/10/2011 - 03:54
User Badges:

Hello Astanislaus

I had the same problem as you, and yes, the CSS on the gateway ports needs to have the CTI route points partition included. You say there were a translation pattern in between.

If the CSS on the gateway includes more than an single partition the translation pattern (that we use to add a digit prefix on the calling party number) do not work on my system.

Did your translation pattern still works?



This Discussion