Examples of org.freeswitch.esl.client.transport.event.EslEvent

org.freeswitch.esl.client.transport.event.EslEvent

FreeSWITCH Event Socket events are decoded into this data object.

An ESL event is modelled as a collection of text lines. An event always has several eventHeader lines, and optionally may have some eventBody lines. In addition the messageHeaders of the original containing {@link EslMessage} which carried the event are also available.

The eventHeader lines are parsed and cached in a map keyed by the eventHeader name string. An event is always expected to have an "Event-Name" eventHeader. Commonly used eventHeader names are coded in {@link EslEventHeaderNames}

Any eventBody lines are cached in a list.

The messageHeader lines from the original message are cached in a map keyed by {@link EslHeaders.Name}. @author david varnes @see EslEventHeaderNames

            String contentType = message.getContentType();
            if ( contentType.equals( Value.TEXT_EVENT_PLAIN ) ||
                    contentType.equals( Value.TEXT_EVENT_XML ) )
            {
                //  transform into an event
                EslEvent eslEvent = new EslEvent( message );
                handleEslEvent( ctx, eslEvent );
            }
            else
            {
                handleEslMessage( ctx, (EslMessage)e.getMessage() );

        log.debug( "Received new connection from server, sending connect message" );
        
        EslMessage response = sendSyncSingleLineCommand( ctx.getChannel(), "connect" );
        // The message decoder for outbound, treats most of this incoming message as an 'event' in 
        // message body, so it parse now
        EslEvent channelDataEvent = new EslEvent( response, true );
        // Let implementing sub classes choose what to do next
        handleConnectResponse( ctx, channelDataEvent );
    }

Examples of org.freeswitch.esl.client.transport.event.EslEvent

Related Classes of org.freeswitch.esl.client.transport.event.EslEvent