What is FeatReason:33 in JTAPI Events?

[derrickgunter]

Hi Friends,

What does FeatReason:33 in JTAPI events mean?  I can't find this defined in the Cisco JTAPI docs. Like this:

2136: Nov 03 16:49:21.536 ADT %JTAPI-JTAPI-7-UNK:(P1-devuser1) 1184538/1 ConnCreatedEv 6017::1 [#126] Cause:100 CallCtlCause:0 CiscoCause:31 FeatReason:33

2137: Nov 03 16:49:21.536 ADT %JTAPI-JTAPI-7-UNK:{ CcnCall=Call:[GCID=(1184538/1),CID=23600251] Connection=[6017::1/(P1-devuser1) GCID=(1,1184538)->ACTIVE]->IDLE: creating new Connection for CCNCall }

2138: Nov 03 16:49:21.536 ADT %JTAPI-JTAPIIMPL-7-UNK:(P1-devuser1) GCID=(1,1184538)->ACTIVECallManager.deliverEvents: deliver 1 events with METACODE 129

2139: Nov 03 16:49:21.536 ADT %JTAPI-JTAPI-7-UNK:[1184538/1]CallImpl.deliverEvents(): for all 1 observers

2140: Nov 03 16:49:21.536 ADT %JTAPI-JTAPIIMPL-7-UNK:[com.genesyslab.ciscocm.CcmCallObserver@792ef193]ObserverProxy.queueEvents: queuing asynchronously

2141: Nov 03 16:49:21.536 ADT %JTAPI-MISC-7-UNK:ObserverThread(com.genesyslab.ciscocm.CcmCallObserver@792ef193): queuing com.cisco.jtapi.JtapiCallEventSet

2142: Nov 03 16:49:21.536 ADT %JTAPI-CTI-7-UNK:{ALL EXTERNAL ADDRESSES|Call:(P1-devuser1) GCID=(1,1184538)->ACTIVE} ExternalCallStateChanged [ state=OFFERING cause=100 processEvent= reason =33 ]

2143: Nov 03 16:49:21.536 ADT %JTAPI-JTAPIIMPL-7-UNK:{(P1-devuser1) GCID=(1,1184538)->ACTIVE} Handling External STATE_OFFERING for 6017::1

2144: Nov 03 16:49:21.536 ADT %JTAPI-JTAPI-7-UNK:(P1-devuser1) 1184538/1 ConnInProgressEv 6017::1 [#127] Cause:100 CallCtlCause:0 CiscoCause:31 FeatReason:33

2145: Nov 03 16:49:21.536 ADT %JTAPI-JTAPIIMPL-7-UNK:ObserverThread(com.genesyslab.ciscocm.CcmCallObserver@792ef193): delivering JCES[1]

2146: Nov 03 16:49:21.536 ADT %JTAPI-JTAPIIMPL-7-UNK:[com.genesyslab.ciscocm.CcmCallObserver@792ef193]ObserverProxy.deliverEvents()

2147: Nov 03 16:49:21.536 ADT %JTAPI-JTAPI-7-UNK:(P1-devuser1) 1184538/1 CallCtlConnOfferedEv 6017::1 [#128] Cause:100 CallCtlCause:-1 CiscoCause:31 FeatReason:33

We are tested extend and connect functionality.  Maybe it is related.

See attached jtapi log for full sample.

Thanks,
Derrick

[derrickgunter]

Related question: What is CiscoAddress.getType() value of 11?  There is no 11 constant define in CiscoAddress object.

Thanks.

[mpotluri]

Feature Reason can be accessed by apps using getCiscoFeatureReason() API.  Notes from Cisco JTAPI javadocs:

int  getCiscoFeatureReason()

Returns the Cisco Unified Communications Manager Feature Reason for this event.

To function properly, some applications need to know the reason why an event happened. This interface provides the CiscoFeatureReason in JTAPI Call events for current and new features. Existing features, such as transfer, continue to receive the CiscoCause provided by the older interface CiscoCallEv.getCiscoCause(), while this interface will provide REASON_TRANSFER for transfer.

Caution: Applications should make sure to handle unrecognized reasons and provide default behavior, because new reasons could be added in the future and this interface may not be backward compatible.

The possible values are defined in the CiscoFeatureReason interface.

I don't think we should see 11 for getType(). What is the scenario? Corresponding JTAPI log is needed as well.

[derrickgunter]

Thanks Mohan. In my case the 33 is from CiscoConnection.getReason(), not getCiscoFeatureReason().

CiscoConnection lists only:

  public static final int REASON_DIRECTCALL = 1;

  public static final int REASON_TRANSFERREDCALL = 2;

  public static final int REASON_FORWARDNOANSWER = 3;

  public static final int REASON_FORWARDBUSY = 4;

  public static final int REASON_FORWARDALL = 5;

  public static final int REASON_REDIRECT = 6;

  public static final int REASON_OUTBOUND = 99;

Is CiscoConnection.getReason() the same as getCiscoFeatureReason()?

Thanks again,

Derrick

PS  Sorry, I made a mistake about geType() 11. Forget that question.

[derrickgunter]

Any thoughts? Thanks.

[mpotluri · Accepted solution]

All reason are derived from the same value from CTI and I expect to see the same value for both reasons (reason in Connection and getCiscoFeatureReason()).

[derrickgunter]

Thanks Mohan.

Derrick