Bill Shannon
added a comment - 29/Jun/10 3:17 PM My understanding is that we don't have callflow monitoring in 3.1.
I don't know whether we will have it for 3.2.
Reassigning to Nazrul, who can either close it, mark it as "target 3.2",
or assign it to someone who is working on this.

A fix for this issue was initially identified for possible inclusion in the 3.2 release, but after further 3.2 planning, the feature or improvement did not make the cut. This issue is being targeted for a future release. If based on a reevaluation, it is targeted for 3.2, then update the "fix version" again.

Tom Mueller
added a comment - 05/Apr/11 1:08 PM A fix for this issue was initially identified for possible inclusion in the 3.2 release, but after further 3.2 planning, the feature or improvement did not make the cut. This issue is being targeted for a future release. If based on a reevaluation, it is targeted for 3.2, then update the "fix version" again.