I'm putting together an application that uses JTAPI to track call times.
When I'm tracking an internal call, the call time is pretty much exact and my application gets notified about all call events.
But when tracking external calls (calls that go to the public telephone network) I've noticed that as soon as the call is directed to the router (a Cisco 3800), CallManager sends a connected event when in fact the phone on the other side is still ringing.
Even if the external call never gets answered I get a connected (active call) event.
I have a trace dump of my application that shows the events when they happen and I can provide that if needed but for now I was wondering what, if anything, should be configured either in CallManager 3.3 or the Cisco 3800 so that events are triggered correctly, i.e. get one connected event when the call is actually answered and not when CallManager passes the call to the router.