topic Re: InvalidStateException for working device in Call Control

InvalidStateException for working device

ashish.nijai — Wed, 16 Jul 2014 17:33:12 GMT

I am developing JTAPI application for making call using super provider.

I am using a device to call which is in good state. I can create terminal with provider.createTerminal().

When i tried to make call using JTAPI application from that device, it gives me InvalidStateException with device state =4

The device is in good state and can dial calls manually. It also registered as JTAPI device.

Still it shows InvalidStateException whenever I try to dial programmatically.

Help please.

Re: InvalidStateException for working device

mpotluri — Wed, 16 Jul 2014 18:02:02 GMT

Ashish,

Did you add call observer on the address or terminal before making a call? Application should add observer and call observer on the address/terminal, wait till a inService event is received and then do call features.

Re: InvalidStateException for working device

ashish.nijai — Thu, 17 Jul 2014 20:28:32 GMT

Why it is mandatory to add observer?

Any reason for it?

Please specify

Re: InvalidStateException for working device

mpotluri — Thu, 17 Jul 2014 21:05:23 GMT

Yes. Application should have call observer before calling any feature API. Adding call observer will open the signaling needed to create the correct JTAPI call model.