Xima Chronicle 2

[wotanuta]

I have installed Chronicle and it is unable to find any call data on any reports. It see's our IPO 500 and sees the users and hunt groups. Any ideas??

 

[TomMills]

what settings have you programmed?

 

[wotanuta]

Only the IP address of the IPO and password. Couldn't see any other settings that I have to configure.

 

[TomMills]

all i have programmed is the ip address, subnet and password.

port 9080

server ip should be localhost

port 3306

mine logs just fine.

go to cradle to grave and put a date range spanning the last few days, this will show any call data that has been collected and that reports can be run against.

Check thats you firewall ports are open or try turning it off altogether

 

[wotanuta]

Thats the same settings as I have. The firewall on my laptop is off. Is there a refresh rate. Have only got the beat trial version without live reporting. Only installed it this morning.

 

[TomMills]

yeah i have the beta version, that is all that is currently available as far as i know.

i havent done anything with refresh rate. have you emailed the support guys, they are really good,

do you not have any call data collected at all?

 

[wotanuta]

None whatsoever. Have emailed them this morning but no reply as of yet. Thanks for replying.

 

[wotanuta]

Just a thought if Tom is still around. What settings did you configure on the IPO??. I assume it uses the CDR field

 

[TomMills]

no settings on the IPO whatsoever, it uses UDP connection of some sort, so you dont need to change anything on the IPO.

sorry i cant be of more help but it just kinda works, all you can check is that the password and IP is set correctly, and maybe restart the chronicall services.

there are three of them in the usual spot.

i would restart all three (or make sure that they have actually started?)

 

[wotanuta]

Thanks Tom

Will try it on another site to see if it works there.

 

[SPIPOffice]

I had the same issue, I found I could only make changes on the PC the xima was installed on.

I'm sure you done this already, as your using a IP500, the defualt PBX monitor password is password.

 

[wotanuta]

Thanks. Only found out this morning that it uses the monitor password to collect data.

 

[h382]

I have just started testing this out as well. I am amazed from the little bit of stuff they have working now, and how they seem to "get it right".

I have requested from their developers to incorporate a graph like interface for trunk usage, etc.

What I am really needing right now is something that will tell me how many channels I maxxed out during a particular month. I have 2 PRI's, 46 channels, and I I'd like to go to my provider and say, "I only used a total of 25 channels at any given time, I can turn down the rest."

Almost like the System Status application with it's graphs, but shows where my max usage point was, and at what time.

 

[TomMills]

it is good stuff, will be interesting to see how it is once all of the other features are active, just had a play with the trunk reports, to see if i could get that info out but looks like it is missing,

anyone been asked to fill out a questionnaire yet?

 

[wotanuta]

It seems to be working quite well for me. Not sure if there are slight differences in the US - UK terminology in respect of the wording of some reports. For example, does inbound in a lot of the reports mean internal as opposed to external inbound calls as I can't see the figures tallying. Any US or UK gents out there that can advise???

 

[TomMills]

im in uk and inbound is inbound. i.e if you run an inbound call report on an extn, it should show ALL calls IN to that extn whether they originate from outside the system or from another internal extn

 

[wotanuta]

OK. Thanks for that (Again)

 

[TomMills]

no worries, still playing around with it myself in spare moments, only downer is the greyed out features.

but looks like it will be very cool when finished, hope i get a free copy for trialing it, i have only found one bug but surely that is a good thing

 

[wotanuta]

What bug have you found cos like you am playing around with it in spare time.

 

[TomMills]

just from a custom report, it wouldnt let me do what i wanted to do in short.

it was just a conflict when trying to use too many specifics on one report