PureEngage On-Premises

 View Only

Sign Up

  • 1.  Incorrect chat protocol (coming as Basic) from web application

    Posted 10-02-2014 16:27
    Hello, we are integrating chat application to our website and we used sample code snippets that comes out of box. For some reason, the chat protocol is coming as "Basic" instead of "Flex" for the new connection and hence failing. Does anyone know what might be issue? Any help will be appreciated.

    22:48:10.212 Trc 59201 new connection created with conn_id=460:42 (type=BASIC) ? First attempt
    22:48:21.632 Std 59211 error { |basic: Wrong protocol} while parsing packet from conn_id=460:42 (type=BASIC)
    22:48:21.632 Trc 59272 debug - received packet of size=1304 with hex: **00 3C 00 3F 00 78 00 6D 00 6C 00 20 00 76 00 65 00 72 00 73 00 69 00 6F ..**
    22:48:21.632 Std 59208 closing conn_id=460:42 (type=BASIC). Reason: error while parsing incoming data
    22:48:21.632 Trc 59202 connection was closed for conn_id=460:42 (type=BASIC)


  • 2.  RE: Incorrect chat protocol (coming as Basic) from web application

    Posted 10-17-2014 09:30
    Hi,

    Please open a case to investigtae the faced problem.

    In the opened case please specify the eServices components version. Also please send us the ChatServer debug log covering the problem and your sources reflecting the implementation of chat application.

    Roman T


  • 3.  RE: Incorrect chat protocol (coming as Basic) from web application

    Posted 10-09-2017 12:25
    Hi Satish

    Set connection to chat webapi port at GMS application object, instead of default port.

    It helped to me
    br
    Robert