Chronicall with IPOSE

[csalt]

Has been running Chronicall v3.10 with IPO SE r10.0.x (Primary server plus 3 IP500 gateway as expansion systems) for few months and encountered few issues with the Chronicall that showing incorrect info. Not getting very productive response from the support so far. Hope some of you who encountered the similar issues can share your experience.

1. Calls got mixed in C2G. There are calls that got "mixed" together in single call ID in C2G. Call detail Reports will show incorrect data for each agents, total call, total talk time etc are inaccurate.

2. IPO User created and login in IP500 remote office B, when this user temporary move to main office A and he logs in his extension in office A, his outbound calls are shown as internal calls.

Have configured chronicall to use Devlink 3 and created local ISDN trunk in chronicall (except SCN links between IPOSE & IP500 expansions). Not sure if there is anything else that is required.

Thanks

 

[Suporte JustGroup]

Hi csalt!

1. Calls got mixed in C2G. There are calls that got "mixed" together in single call ID in C2G. Call detail Reports will show incorrect data for each agents, total call, total talk time etc are inaccurate.

I have a client pretty much the same as your scenario, but this error started to appear after upgrading from an initial Avaya Release of version 10.
Functioning perfectly = 9.1 when I migrated to 10 the problem appeared, after migrating to 10.1 the same problem disappeared.

What version is your SE?

2. IPO User created and login in IP500 remote office B, when this user temporary move to main office A and he logs in his extension in office A, his outbound calls are shown as internal calls.

Basically this is what will happen, it will understand that the connections are internal because first of all it is a Hotdesk and is logged "remotely". I do not believe that any software on the market will interpret differently. So this is not a problem but a normal interpretation.

 

[csalt]

1. Yes, the system is running IPOSE r10.0... So looks like Chronicall is not able to work well with r10.0. No confirmation from the support on this though.

2. Well, when the user login remotely, they are using remote local trunk to call out and there is nothing routed back to the original gateway, still the system see that as internal...
and the best part is, when the user travel back to his original office and login locally, his outbound calls are still shown as "internal"... still figuring out how to normalize this user back to his original state... tried, reload user & group, restart chronicall, restart server, relogin the phone... nothing help

 

[Andhee]

Engage Xima support. Its likely you will need their latest upgrade/patch.
Worked for me.

If vegetarians love animals so much, why are they eating all of their food?