Spike in failed outbound (fastbusy) calls

Unanswered Question
Feb 4th, 2009
User Badges:

I have recieved approx 20 tickets today for internal users attempting to make outbound calls. We have 2 full PRIs for outbound voice and don't appear to have a capacity issue. Looking at the CDR for each failed call, they contain a destCause_value of 1, which according to documentation means "Unallocated/unassigned number". If the user waits a few mins and tries again, the call goes through just fine.

Is this unallocated/unassigned cause code indicating that my telco provider is rejecting the call as a bad number and that I should open a ticket with the voice provider?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Jaime Valencia Wed, 02/04/2009 - 14:33
User Badges:
  • Cisco Employee,
  • Hall of Fame,


that can happen if the telco had some routing issues and was unable to determine where to send the call even if it's a valid and working number

a debug would show all this info but if you don't have it or it has stopped a call to the telco is not a bad idea just to make sure the problem is solved



if this helps, please rate


This Discussion