i believe integrating applications with our portal environment is a little tricky. Portal does something funky here. When I took my code and unplugged it from portal, Sessions kinda reached the inner window.

After looking for some help online.. I found this solution for older version on Cutechat. Can you tell me what chnage I need to make for the newer cutechat version since method,version, and public key etc must have changed?

It is due to an incorrect relative URL. Open CuteSoft_Client\CUteChat\chat.rane.aspx and look for the ProcessRequest function.  Here is what it should look like before you edit it:

 void System.Web.IHttpHandler.ProcessRequest(HttpContext context)
{
    CuteSoft.Chat.Rane.RaneHandlerFactory.ProcessRequest(context,serviceType);
}

Edit it so that it looks like this instead: 

void System.Web.IHttpHandler.ProcessRequest(HttpContext context)
{
   CuteSoft.Chat.Rane.RaneHandlerFactory.ProcessRequest(context,serviceType);
    Context.Response.Write(
"ChatRaneService=cutechatraneobjectbuilder('chat.rane.aspx','CuteSoft.Chat.ChatRaneService,CuteSoft.Chat,Version=2.0.0.0,Culture=neutral,PublicKeyToken=da0fc3a24b6f18ba',['Test','CHSync','CHDisconnect','CHChangeAvatar','CHChangeSkin','CHSetBlockUser','IMSync','IMDisconnect','IMUpdateDescription','IMUpdateStatus','SetBlockUser','AddContact','RemoveContact']);"
    );
}

 

This effectively reassigns the ChatRaneService variable to have just "chat.rane.aspx" as the URL, rather than "/ChatApplication/CuteSoft_Client/CuteChat/chat.rane.aspx".  This is a problem because the application was using a URL relative to the root of the remote server rather than relative to the current directory.