JoelEzell wrote:Yeah, EngagementDesigner is good at a lot of things; string parsing is not one of them. It's definitely easier to do that in Java code. I don't have any examples of use of IncomingSipMessageListener, but it's pretty straightforward. Just create a class that implements that Interface and has an annotation of IncomingMessageListener. Something like this. You can then use SipRequest.getHeader() to get the value of the header. The attributes in the callAttributes map are the same as the attributes accessible through the Call interface.

@IncomingMessageListener
public class MySipMessageListener
{
void requestReceived(SipRequest request, Map callAttributes)
{
}

void responseReceived(SipResponse response, Map callAttributes)
{
}
}

void requestReceived(SipRequest request, Map callAttributes)

{

  logger.info(request.toString());

  if (callAttributes.isEmpty()) {

            logger2.info("Empty \n\n\n");

        } else {

            logger2.info("Not EMPTY \n\n\n");

        }

}

JoelEzell wrote:Is this the dialog establishing INVITE? If so, it would be expected that callAttributes would be empty. This set of name/value pairs is there for your application to use for your own use. The platform will never populate anything there on its own. The SIP headers are available through the SipMessage interface, if that's what you were going for.

JoelEzell wrote:OK. So at this point, you're all good, right?