Cisco Finesse Release 9.1(1) · PDF fileperform operation. Error Code: CTI-4047)

Cisco Finesse Release 9.1(1) SU1

Table of Contents Patch version ............................................................................................................................................. 2

Valid upgrade paths .................................................................................................................................. 2

Upgrading to Cisco Finesse Release 9.1(1) SU1 ........................................................................................ 3

Before you begin ................................................................................................................................... 3

Upgrade procedure ............................................................................................................................... 3

Rollback ..................................................................................................................................................... 4

Resolved caveats in this Engineering Special ............................................................................................ 5

CSCug72602 .......................................................................................................................................... 5

CSCuh87882 .......................................................................................................................................... 5

CSCuh91319 .......................................................................................................................................... 6

CSCui55974 ........................................................................................................................................... 6

CSCuj36392 ........................................................................................................................................... 7

CSCul00976 ........................................................................................................................................... 7

CSCum06500 ......................................................................................................................................... 7

CSCum77728 ......................................................................................................................................... 8

Bug Search Tool......................................................................................................................................... 8

Changes in previous Release 9.1(1) ES releases ....................................................................................... 8

Changes in Cisco Finesse Release 9.1(1) ES5 ........................................................................................ 8

CSCuj63156 ....................................................................................................................................... 8

CSCui38742 ....................................................................................................................................... 9

CSCuj15267 ....................................................................................................................................... 9

CSCuj21714 ....................................................................................................................................... 9

CSCuj21753 ....................................................................................................................................... 9

CSCuj20568 ..................................................................................................................................... 10

CSCuj41876 ..................................................................................................................................... 10

CSCuj74060 ..................................................................................................................................... 10

Changes in Cisco Finesse Release 9.1(1) ES4 ...................................................................................... 11

CSCuh82014 .................................................................................................................................... 11


CSCug52245 .................................................................................................................................... 11

CSCuf51868 ..................................................................................................................................... 11

CSCuf81404 ..................................................................................................................................... 12

Improved handling of network glitches .......................................................................................... 12

Changes to Cisco Finesse Notification Service logging ................................................................... 12


CSCue46527 .................................................................................................................................... 12

CSCue46859 .................................................................................................................................... 13

CSCue68909 .................................................................................................................................... 13

CSCue76720 .................................................................................................................................... 13

CSCue68885 .................................................................................................................................... 14

CSCue31049 .................................................................................................................................... 14

CSCue06426 .................................................................................................................................... 14

CSCue46832 .................................................................................................................................... 14


CSCue30887 .................................................................................................................................... 15

Patch version 9.1.1.11001-2

File Name MD5 Checksum

UCSInstall_CCD_9.1.1.11001-2.sgn.iso fd29b35bb3f8879893ac8bd6685f5d92

Valid upgrade paths From Cisco Finesse Release 9.1(1) FCS version

From Cisco Finesse Release 9.1(1) ES1





Note: The ISOs for Cisco Finesse Release 9.1(1) and 9.1(1) SU releases are bootable. That is, you can

install Finesse directly from the latest SU. For example, if your primary and secondary Finesse server

both have Cisco Finesse Release 9.1(1) ES5 installed and you need to rebuild your secondary node, you

can upgrade your primary node to Release 9.1(1) SU1 and perform a fresh installation of Release 9.1(1)

SU1 on your secondary node.

This patch was created to address customer issues with Finesse.

Cisco Finesse Release 9.1(1) SU1 is cumulative. That is, it contains all fixes from Cisco Finesse Release

9.1(1) ES1, Cisco Finesse Release 9.1(1) ES2, Cisco Finesse Release 9.1(1) ES3, Cisco Finesse Release

9.1(1) ES4, and Cisco Finesse ES5.

Upgrading to Cisco Finesse Release 9.1(1) SU1

Before you begin

Note: You must perform a DRS backup before you perform this upgrade. If you do not perform a DRS

backup and there is a problem with the upgrade, you cannot switch back to the previous version.

To access the DRS application, direct your browser to the following URL:

https://<Finesse server IP address>:8443/drf

For more information, see the detailed online help provided with the DRS application.

Note: Third-party gadgets are not migrated when you perform an upgrade. You must manually upload

the gadgets to the primary and secondary Finesse servers each time you upgrade the system.

After an upgrade, you must reset the password for the 3rdpartygadget account on the primary and

secondary Finesse servers. This password is not migrated across upgrades.

Upgrade procedure

You must perform the following procedure on the primary Finesse node first and then on the secondary

Finesse node.

1) Download Cisco Finesse Release 9.1(1) SU1 from Cisco.com and place the file on an FTP or SFTP

server that you can access from your Finesse system or burn the ISO file to DVD.

2) If you choose to download the ISO to the local disk where vSphere is installed, in the VM console,

click the Connect/Disconnect the CD/DVD devices button and select Connect to ISO image on local

disk.

3) Navigate to the location where the ISO file is stored.

4) SSH to your Finesse system or log in at the system console with the credentials for the platform

administration account.

5) From the command line interface (CLI), run the command utils system upgrade initiate.

6) Follow the instructions provided by the utils system upgrade initiate command.

7) When prompted, select option 3 for local DVD/CD.

8) At the Automatically switch versions if the upgrade is successful prompt, type yes to upgrade and

switch version, or type no to upgrade only without switching version.

Note: The upgrade is not active until a switch version is performed.

9) If you typed no to upgrade without switching version, you must manually switch version. If you

typed yes to automatically switch versions, skip to step 10.

a) To manually switch versions, access the CLI using the platform administration account.

b) Enter the command utils system switch-version.

c) Type yes to confirm. Finesse reboots.

10) Disable Cisco Security Agent (CSA).

a) Access the CLI using the platform administration account.

b) Enter the command utils csa disable.

c) Enter yes to restart.

11) Check that the upgrade was successful by signing in to Finesse (http://<IP address or hostname of

Finesse server>/desktop).

Note: After Finesse restarts, wait approximately 10 minutes before you try to sign in to the desktop.

Finesse services may take a few minutes to reach the STARTED state.

Rollback If there is a problem with the upgrade, you can roll back to the previous version as follows:

1) Perform a switch-version on the primary node.

a) Access the CLI and enter the command utils system switch-version.

b) Enter yes to confirm.

The system attempts to switch back to the original version and reboots if the switch is

successful.

2) Perform a switch-version on the secondary node.

3) Perform a DRS restore.

Note: Do not attempt to reset replication after you perform the switch-version. You must perform a DRS

restore instead. If you attempt to repair replication before the DRS restore, the DRS restore will not

work correctly.

After completing a successful DRS restore, you must reboot both nodes. Replication automatically

recovers after the system reboots.

To monitor the progress, enter the command utils dbreplication runtimestate.

If replication is set up and functioning correctly, the following appears in the output:

REPLICATION STATUS column: Connected for both nodes

DBver & TABLES column: match for both nodes

REPLICATION SETUP (RTMT) & details column: (2) PUB Setup Complete for the publisher node

and (2) Setup Complete for the subscriber node.

Note: Do not attempt to switch forward after performing a rollback. You must upgrade your system

again, as specified in the upgrade procedure in these release notes.

Resolved caveats in this Service Update

CSCug72602

Headline: Mouse pointer sensitivity issue with Finesse 9.1.1

Symptoms: Issue with the mouse pointer sensitivity on Finesse

If a user’s mouse pointer is NOT over a number on the dialpad but on the key, it is an arrow pointer. But

if a user’s mouse pointing IS over a number/text on the dialpad, the mouse pointer changes to a hand

instead of an arrow. Note that it must be directly over the number, not just on the space around the

number on that number’s button area. If a user clicks the keypad with the Arrow pointer on any of the

numbers, it will NOT enter the number even though the key blinks as you click on it. If a user double-

clicks a number, it will put the number in the display above however will not take it as the valid client

code. The mouse actually has to turn into the hand finger pointer over the digit on the key you want in

the keypad in order for it to register. You have to slowly click and make sure you hit the key dead center

in order for it to work. Our users are going to want to enter the DNIS quickly and the way it is working

now you have to do it slowly. The Number !, the *, 0, and # are the worst because there is no text under

the digit number.

Conditions: Pressing DTMF digit on a button that has no alphabet letters.

Workaround: Send DTMF using real phone.

CSCuh87882

Headline: Finesse did not reconnect to CTI after a CTI crash

Symptoms: Finesse remains OUT_OF_SERVICE even though CTI Server is back up and connectable by

other clients.

Conditions: A race condition occurs if the CTI Server drops a successful connection immediately after it

being established, causing Finesse to no longer continue to attempt to reestablish the connection. This

condition occurs if the CTI_ADAPTER component becomes DISCONNECTED immediately (within

milliseconds) of entering CONFIGURING state.

Workaround: Restart Cisco Tomcat to reestablish CTI Connection.

CSCuh91319

Headline: Finesse Agent1- SCCP phone hold issue with remote agent2 conference.

Symptoms: Agent unable to place conference call on hold.

Conditions:

1) Caller calls the contact center.

2) Finesse Agent1 logged in with SCCP phone answers the call and initiates the conference to Agent2 in

remote site.

3) Agent2 at remote site answers the call.

4) Agent1 completes the conference now Agent1, Agent2 and caller are in conference.

5) Agent1 tries to hold the call during conference, prompts with an error message "ERROR (unable to

perform operation. Error Code: CTI-4047)”

Workaround: Use the phone to place conference on hold.

CSCui55974

Headline: Event not published to client when wrapup agt ends held consult call.

Symptoms: Agent receives operation timed out message on the UI when a wrap-up enabled agent ends

a held consult call.

Conditions:

Agent A is wrap-up enabled, receives a wrap-up enabled, routed call and answers that call.

Agent A places a consult call to Agent B (also wrap-up enabled).

Agent B answers.

Agent A places the consult call on hold.

Agent A ends the help consult call.

A receives an operation timed out error.

Workaround: Wait for agents to get out of wrap-up state (wrap-up timer expires or agent changes his

state manually). Call will get cleared on the desktop.

CSCuj36392

Headline: Call control gadget disappears after chained call control scenario

Symptoms: There is code in the Call Control gadget that, when the agent receives a NOT_READY event,

determines whether to show the "Make a New Call" row or not. If the agent talking on a call and a

supervisor is silent monitoring that call, it is possible when the call ends that the NOT_READY event is

sent in such an order that it precedes the DELETE event for one of the dialogs (actual call or silent

monitor call). If this happens, according to the logic, the gadget thinks the agent still is on a call, so it will

not show the "Make a New Call" row but when the last DELETE dialog event comes in, the gadget will

"disappear".

Conditions: This was observed in the complex call scenario involving a conference call and silent monitor

call, however, with any silent monitored call this is a possibility, it depends upon the order of events

received.

Workaround: Logout the agent and log back in.

CSCul00976

Headline: Finesse fails to connect to Ctisvr after network outage

Symptoms: Finesse fails to connect to active CTisvr after a network outage or Ctisvr fails over.

Conditions: Network outage or Ctisvr failover in Finesse 9.x

Workaround: Restart Finesse server

or

Restart tomcat service

----------

Log in to the Finesse CLI and perform the following commands:

utils service stop Cisco Tomcat

<wait until it is finished>

utils service start Cisco Tomcat

---------

CSCum06500

Headline: Call Control gadget missing init error handler

Symptoms: Desktop says "Make a new call", but you cannot actually make any new calls. Also it will not

render any calls that actually come in, since initialization never completed.

Conditions: If clicking on "Make a new call" does not actually open the keypad and allow you to make a

new call.

It appears that changing state to "Ready" seems to alleviate the condition by continuing and completing

the rest of the gadget initialization.

Note that this is an extremely rare race condition where the Desktop makes an API call which succeeds,

and then very soon after, the Call Control gadget attempts this same request which then fails.

Workaround: Log out then log back in.

CSCum77728

Headline: IE8 browser memory leak with Finesse 9.1.1

Symptoms: IE 8 browser has a memory leak with Finesse 9.1.1, which in turn causes the Finesse browser

to freeze up. Also, the agents have login and logout issues when this happens.

Conditions: IE 8 with Finesse 9.1.1

Workaround: N/A

Bug Search Tool To access the Bug Search Tool, go to https://www.cisco.com/cisco/psn/bssport/bss and log in with your

Cisco.com user ID and password.

Changes in previous Release 9.1(1) ES releases Cisco Finesse Release 9.1(1) SU1 includes all fixes from Cisco Finesse Release 9.1(1) ES1, Cisco Finesse

Release 9.1(1) ES2, Cisco Finesse Release 9.1(1) ES3, Cisco Finesse Release 9.1(1) ES4, and Cisco Finesse

Release 9.1(1) ES5. The following sections list the resolved caveats and other changes that were

included from these previous ES releases.

Changes in Cisco Finesse Release 9.1(1) ES5

CSCuj63156

Headline: CCE: Cap pending elements when OpenFire cannot deliver event to client.

Symptoms: Agent desktop does not have the best connection with Finesse server or desktop has issues

that limit connectivity with Finesse server, which leads to frequent re-logins or missing events, etc.

Conditions: If OpenFire is unable to deliver an event, it will add that deliverable to a list called

pendingElements tracked under that session.

The idea is to publish all pendingElements when it detects that there is a successful connection.

However the negative side of this is that the size of this list is not capped. So if some agents/supervisor

don't have the best connection or get in a situation where a session is stuck in OpenFire, each time

https://www.cisco.com/cisco/psn/bssport/bss

OpenFire tries to deliver an event to them, it fails and subsequently adds it to the pendingElements list,

making in grow without check.

Workaround: None. A restart of the Cisco Finesse Notification service may work only temporarily if the

issues continue to persist on agent desktop or flaky network connection.

CSCui38742

Headline: Prevent the command that uses the ALL sequencer in the middle of Load

Symptoms: System becomes slow to respond under certain conditions and as a result, different kinds of

errors are presented to the agent, depending on the action performed at the time.

Conditions: Executing any slow operation in either of the following scenarios:

On the hour or half hour while a CTISystemEvent is received from CCE.

While a UCCE config change is being processed.

causes a bottleneck in the thread pool to mark the hour or the half hour. The system should return to

normal once the expensive operation has completed or timed out.

Workaround: Finesse Server reboot or Finesse service restart

CSCuj15267

Headline: BOSH connection gets terminated because rid is out of order

Symptoms: BOSH connection is terminating unexpectedly. If using the Cisco Finesse Agent Desktop, the

agent may not be able to successfully log in to the desktop. The agent sees the black modal dialog that

says "Loading..." and eventually, the login attempt times out.

Conditions: This appears to be more reproducible under WAN deployments where roundtrip delays of

80ms are present.

Workaround: Re-login to the Agent Desktop.

CSCuj21714

Headline: Finesse does not handle CTI FailureEvent during failover

Symptoms: Finesse is out of service.

Conditions: This occurs when during a failover, the CTI adapter goes to configuring state but before

Finesse completes the recovery, the CTI Server sends peripherals offline events.

Workaround: Restart the Finesse server.

CSCuj21753

Headline: Finesse throws NullPointerException is specific failover scenario

Symptoms: Finesse throws a NullPointerException in the desktop-webservices component.

Conditions: This occurs when during a failover, the CTI adapter goes to configuring state but before it

completes the recovery, the CTI Server sends peripherals offline events.

Workaround: Restart the server.

CSCuj20568

Headline: CCE: Lost Mobile Agent attributes when processing CTIConfigAgentEvent

Symptoms: Mobile Agent loses his attributes. The agent does not see himself as a Mobile Agent

anymore on the desktop (i.e. desktop header does not show work mode and dial number).

Conditions: Mobile Agent refreshes his desktop after logging in or he changes his state.

Finesse receives CTIConfigAgentEvent from CTI. This could occur when a queue membership (Precision

queues or normal skill groups) change happens.

Workaround: None

CSCuj41876

Headline: Finesse NullPointerException while processing AgentConfigEvent

Symptoms: Under certain conditions, changes to an agent's queue (skill group) membership do not get

saved in memory in Finesse.

Conditions: This happens when there is a NullPointerException while processing AgentConfigEvent due

to not being able to find a supervisor for this agent.

Workaround: None.

Potentially, the following workaround may help but can't be confirmed given this is not reproducible in

DE lab.

1) Delete the team for which the supervisor is unable to see queue statistics

2) Delete all the agents in that team

3) Permanently remove the deleted items from Deleted Objects

4) Re-create the agents

5) Re-create the team with the agents

CSCuj74060

Headline: Wrap-up codes are not selectable

Symptoms: Unable to select wrap-up codes for team. This applies to the Team Assignment gadget and

occurs in all team assignment gadgets except for layout. The Team Assignment gadget is working

correctly; it has more rows visible on one element than the parent container has space for, which

creates two scroll bars, and is confusing.

Conditions: When assigning wrap-up codes to a team in Finesse Administration:

1. Create more than 25 wrap-up codes in Finesse Administration.

2. At the team page, select more than 24 wrap-up codes.

Workaround: Click the sort arrow at the top of the available list of wrap-up codes. This will lock the

table so that more wrap-up codes can be selected.


CSCuh82014

Headline: Client receives operation timeout message, fails to receive events

Symptom: Client receives operation timed out message on the UI when attempting to perform

operations (e.g. state change request)

Conditions: Client loses connectivity to the Cisco Finesse Notification Service

Workaround: Agent needs to sign out and stay signed out for 2 minutes so that the Notification Service

can clean out the connections (due to inactivity) and send Finesse unavailable presences. After that,

they can log back in and the desktop should work fine.


CSCug52245

Headline: Call does not get cleared on RONA or if caller hangs up while ringing

Symptom: Call does not get cleared from desktop after RONA or if caller hangs up.

Conditions: Client is experiencing a network glitch or is over a slow network when this happens.

Workaround: Refresh desktop or sign out and sign back in.

CSCuf51868

Headline: DRS backup causes Finesse failover

Symptom: DRS backup for Finesse will cause agents to be logged out and display message of Finesse fail

over.

Conditions: Finesse 9.1.1 and DRS backup

Workaround: Wait for DRS to complete and OpenFire (Cisco Finesse Notification Service) process to

restart and then restart Cisco Tomcat.

CSCuf81404

Headline: After Openfire restart login failed with timeout when Finesse in service

Symptom: Frequent restart of Openfire without restarting Tomcat may cause the system to go to a bad

state where login fails due to timeout although the system still appears to be “In Service”.

At one customer site, when Openfire restarts without Tomcat restart, an agent tries to login to

secondary Finesse, but failed. After that, the customer secondary Finesse entered the following state:

Agent cannot login to secondary Finesse due to timeout error although the secondary Finesse shows in

service.

This problem could happen to either side of Finesse.

Conditions: This problem may happen after an Openfire restart without a Tomcat restart in conjunction

with agents logging in after the Openfire restart.

Workaround: Restart the Finesse webapp (utils service restart “Cisco Tomcat”).

Improved handling of network glitches

The Finesse desktop is now more lenient when operating under sub-optimal network conditions.

Previously, if the desktop lost connection to the Finesse server, the desktop would immediately fail over

to the alternate Finesse server. The desktop can now absorb a lost connection to the Finesse server if

that connection is restored within a 10-second grace period. If the connection cannot be restored within

the grace period, the desktop will fail over to the alternate Finesse server.

Complementary functionality has been added to finesse.js for resiliency. Third-party gadgets should use

the latest version to take advantage of resiliency enhancements, which allow them to operate through

and after a connection outage with minimal code changes.

Changes to Cisco Finesse Notification Service logging

For Cisco Finesse, Release 9.1(1), before you could enable or disable Cisco Finesse Notification Service

logging, you had to stop the Cisco Notification Service and the Cisco Tomcat service. With Cisco Finesse

Release 9.1(1) ES3, this requirement is removed.

To enable or disable Cisco Finesse Notification Service logging, you must first ensure that the Cisco

Finesse Notification Service is running. If the service is not running, the command to enable or disable

logging will fail.


CSCue46527

Headline: Phonebook entries missing after pressing keypad while talking

Symptom: When clicking on the keypad the 2nd time, only the last search output is presented to the

agent – missing the entire list of numbers.

Conditions:

Agent clicks the “Make New Call” button, does a search by name (i.e. NL1) and is connected.

While talking, agent clicks the keypad and sees the listings under NL.

Agent hangs up the call, goes to Not Ready, and then clicks “Make new Call” again.

Only the last entries show up (i.e. the two that start with NL).

Agent can’t delete the search entry and add another search name/number.

Can’t use again until they hit their refresh button for the Finesse URL or log out and back in.

Workaround: Log out and log back in.

CSCue46859

Headline: Cisco Finesse Notification service Out of Memory – OOM in SFDC deployment

Symptom: Cisco Finesse Notification service goes out of memory.

Conditions: Log in to Finesse Agent Desktop and refresh the page several times. This leads to a buildup

of HTTP sessions (1 session per refresh) in the Notification service, which never gets cleaned, and

eventually leads to out of memory.

Workaround: Do not use browser refresh as it is not a supported option. Always use the Agent Sign Out

option to gracefully log out the agent. For developers, the recommendation is to always use the same

resource ID to connect to the XMPP channel for a given agent so the same session will be reused by the

Notification service in such a scenario (multiple browser refreshes).

CSCue68909

Headline: Cisco Finesse Notification Service crashes with OOM

Symptom: Cisco Finesse Notification Service crashes with an Out of Memory error, causing Finesse to be

non-functional.

Conditions: Over a period, the accumulation of HTTP sessions (due to a couple of potential code issues)

may result in this symptom.

Workaround:

Stop Cisco Finesse Notification Service

Stop Cisco Tomcat

Start Cisco Finesse Notification Service

Start Cisco Tomcat

CSCue76720

Headline: Finesse does not go OOS when OF goes OOM when Finesse is going IN_SERVICE

Symptom: Finesse did not go out of service after the Cisco Finesse Notification Service crashed with an

OOM error, immediately after Finesse SystemInfo shows IN_SERVICE (bot not all publishes are made).

Agent’s attempt to log in results in errors but the user receives no notification that the system is not

operational.

Conditions: Cisco Finesse Notification Service crashes with OOM immediately after Finesse SystemInfo

shows IN_SERVICE (but not all publishes are made).

Workaround: Reboot the virtual machine that hosts Cisco Finesse for it to be functional again.

CSCue68885

Headline: Finesse did not go OOS after OF crashed with OOM until 9.5 hours later

Symptom: Finesse did not go out of service after Cisco Finesse Notification Service crashed with an OOM

error. Agent’s attempt to log in results in errors but the user receives no notification that the system is

not operational.

Conditions: Cisco Notification Service crashes with OOM.

Workaround: Reboot the virtual machine that hosts Cisco Finesse for it to be functional again

CSCue31049

Headline: XMPP publish errors in logs

Symptom: Unwanted error logs observed in log file lead to confusion that it may be a real issue.

Conditions: Errors occurred when publishing events on default team node.

Workaround: None.

CSCue06426

Headline: Selecting and deselecting Team List causes browser memory leak

Symptom: Possible browser slowness for supervisor desktop when the Team Performance gadget is in

the layout.

Conditions: Each time the team list dropdown is opened, a new div containing the popup of the team

list is created. Once a team is selected or the user clicks away from the dropdown, the popup goes away

but the div that contained the popup remains on the DOM, resulting in an ever-increasing list of empty

div objects as the team list is accessed.

Workaround: Have the supervisor log out and log back in.

CSCue46832

Headline: reset_3rdpartygadget_password fails

Symptom: Any of the following CLI commands will fail to execute and will hang at the password prompt

when attempted:

utils finesse application_https_redirect*

utils finesse notification*

utils reset_3rdpartygadget_password

This will lock your current console session until the system is rebooted.

Conditions: You install Finesse with an administrator account and the username is not “administrator”

in all lower case.

Workaround: Another console can be opened if you are connected directly to the system by pressing Alt

+ any function key [F1-F6], for a total of up to 6 separate console sessions.

If you are connected via SSH, simply disconnect and reconnect to gain a new session.

To prevent this from happening again, you can create an additional CLI account that uses the username

“administrator” (all lower case) with limited access to CLI commands. This account will be able to run

these commands without an additional password prompt that locks the session.

Removing Additional CLI Account

In Finesse Release 9.1(1), when you created the Administrator User account during installation, if you

used anything other than “administrator”, you could not execute certain CLI commands. The

workaround for this issue was to create a second CLI account with the username “administrator”. This

ES contains a fix for this issue.

If you previously created a second account with the username “administrator”, you can now safely

remove that account.

To remove the account:

Log in to the VOS CLI and run the following command: delete account <account name>


CSCue30887

Headline: Issue with agent logout due to XMPP presence state not waiting 10 secs

Symptom: Agents getting logged out due to XMPP presence

Conditions: This only happens in SalesForce.COM (SFDC) generic connector where the entire SFDC web

page is refreshed after every action, causing the XMPP connection to re-establish.

Workaround: None.

Documents

Cisco Finesse Release 9.1(1) · PDF fileperform operation. Error Code: CTI-4047)