Internal call records is not a cost option rather you need to tab through the other times or scroll down as it is beyond the last item of the first visible page.
"Been there, done that and got the teeshirt
This is correct when running Supervisor in SSH mode you will end up with two logged in users in the CMS. One is for the putty (SSH) tunnel and the other is a telent session the Supervisor client run over this tunnel, Yes Supervisor still uses telnet! this is why you cannot fully disable telnet...
Wed Dec 2 17:02:54 [12] SESS bad sequence, 82 received, 81 expected" means as it says the CMS was told to expect 81 application packets of data but 82 were received. Note: these are not TCP packets rather they are CMS application packets.
I would check the firmware on the CLAN and make sure...
Are the calls missing or does the previous or next interval have more call? Without detailed diagnosis it's impossible to tell.
"Been there, done that and got the teeshirt
A nice simple Vector, NA should in theory have all calls routed through it, are they many force disconnected calls?
You could use disp events on the CM to see if it is reporting any interesting events. Other than this it really is difficult to tell.
"Been there, done that and got the teeshirt
CMS and NA will only record ACD measured Calls. So if these missing calls are not ACD measured calls they will not be recorded. Are you sure the VDN in question is set to be measured to both or external on the CM? If it not set or set to internal there will not be a record on the CMS and thus on...
Sure, ECH data is the cradle to grave data from the CMS, as the ACD summary data and ECH data are derived from the same events the number of calls should be the same.
So one of several things are.
Not all the data has been sent, possible, the ECH logs on the CMS should show failed FTP...
Nice Analyzer (NA) as you found get it's data from the CMS's External Call History data (ECH). The CMS itself only processes ACD measured calls where as CDR will capture all calls if correctly setup. Now the issue is CDR data is quite limted in information compared to the data from the CMS which...
1. The data for ACD 2 will be available until the ACD is removed or has expired though the data sotrage allocation rules, so ACD 2 will already be turned on. However in CMS speak turning on an ACD really means enabling data collection to a live switch (Communication Manager (CM))
2. As you...
No, they are two seperate platforms using completely different databases and OSs. OA takes External Call History and synonym data from the CMS, this data is not directly created on the CM, so you need the CMS before you even start.
OA does take data directly from AIC is used.
"Been there...
The default router is defined in /etc/defaultrouter file. This file can contain an ipaddress of the default router or a name. If it is a ipaddress change it here, if it is name edit the /etc/hosts file find the name and change the ipaddress. A reboot is required to make this change take affect...
What you might wan't to do is multi-homing, I have done this as it moves the real ipaddress between two NICS and thus the user does not need to login again. OK for supervisors but possibly risky for the switch to CMS connection. Needless to say does not come with any support from Avaya...
Pleaes pardon the bad english...
you will she who are are loging in
should read
you will see who is logging in,
"Been there, done that and got the teeshirt
1. ODBC does use Solaris logins and password however as they are accessing the CMS via the ODBC broker they will not show up with the standard who command, however if you increase the odbc_init log level to 7 you will she who are are loging in warned the odbc logs are rolling if there is a lot...
You can't, CMS Supervisor Designer reports can only run in a windows environment. The teminal connection is running and rendering reports directly on SUN platform rather than in the windows based client which renders then within the client itself.
"Been there, done that and got the teeshirt
Interesting question, as the switch hook is on the handset cradle, it is expected that the handset is there so cannot be disabled, so why not leave the handset on the phone for operational reasons but remove the handset cord so it cannot be used for the voice part or just wedge the switch hook...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.