Hello,

In developing a JTAPI application to interact with your call
manager via CTI Route Points, we're seeing a case where our application
is not able to pick up incoming calls because the line is busy.

Our application is liked to a CTI Route Point, and a caller can access
the
application by called the CTI Route Point extension. Some of the inbound
calls are reject even before they reach our application. Others are not.
The only difference between these calls is the CalledID. I have a number
of CTI Port extensions, which are forwarded to the same CTI Route Point
number. So, the Called ID represents the CTI Port extension which is
being dialed.

For some extensions, I get the following log from the jtapi.jar (See
below)
note the CALLREJECTED. This doesn't happen when any of the other
CalledIDs
are made.

Why is this rejection happening?

345409: Nov 19 16:41:07.692 PST

%JTAPI-CTI-7-UNKP1-p
yagoCM)& #123;Line:VM_Juneau_CRP:5798(1,63710)|Ca
ll:[GCID=(909871/1),CID=
19262
529]}
CallStateChanged [ state=IDLE cause=CALLREJECTED destType=IN_CLUSTER
destCM=1
fwdDestination=null unModifiedCg=7796 unModifiedCd=5798

unModifiedOriginalCd=6308 unModifiedLastRedirected=6308 calling=7796

callingName= called=5798 calledName= origParty=6308 origName=

lastRedirected=6308 lastRedirectedName= origin=UNKNOWN (0)
reason=DIRECTCALL
activeTone=0 deviceName=null bRemoteInUse=false bPrivacy=false

CallSelectStatus=0 CallingPartyPI=True CallingPartyDisplayNamePI=True

CalledPartyPI=True CalledPartyDisplayNamePI=True
OriginalCalledPartyPI=True
OriginalCalledPartyDisplayNamePI=True LastRedirectPartyPI=True

LastRedirectPartyDisplayNamePI=True ]

[ Post a follow-up to this message ]