Call Rejected - Trigger Failed

Unanswered Question
May 22nd, 2007


Users occassionally get a busy signal when calling our IPCC queue. I have run the Rejected Call Detail Report which confirms this. The reason given is Trigger Failed.

Looking at the logs I see the error

42974982: May 23 12:01:42.043 EST %MIVR-SS_TEL-7-UNK:Route Connection: [5999/(P1-crstapi_1) GCID=(1,9206)->INVALID]->DISCONNECTED, CTI Port selected: TP[id=5,implId=68009,state=IN_USE]

42974983: May 23 12:01:42.043 EST %MIVR-SS_TEL-3-ROUTE_FAILED:Route failed: All Call ids=JTAPICallContact[id=26755,implId=9206/1,inbound=true,App name=ServiceAnalysts,task=null,session=20000049665,seq num=0,cn=5999,dn=5999,cgn=4066,ani=null,dnis=null,clid=null,atype=DIRECT,lrd=null,ocn=5999,route=TR[num=5999],TP=null,List of Active Connections=[5999/(P1-crstapi_1) GCID=(1,9206)->INVALID]->DISCONNECTED,Extension=68009, Did not meet pre-conditions.,Failure reason= call will be rejected,


42974984: May 23 12:01:42.043 EST Did not meet pre-conditions.

why is the trigger is failing?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
aghaznavi Wed, 05/30/2007 - 05:38

This issue occurs when there is a configuration issue with the rigth patterns. Check if the RP configuration is fine. If so, try restarting the server to resolve the issue.

mohsin.kazi Fri, 06/08/2007 - 04:03

I suspect this could be due to CTI port being in USE prior to the call being sent to the Queue, the log displays that too.

Just make sure you have enough CTI port assigned to the trigger to service the queues.


This Discussion