Re: [reSIProcate] WSS with AfterSocketCreationFunction causes core

[Nathan Stratton <nathan@xxxxxxxxxxxx>]

On Wed, Jun 12, 2013 at 12:49 PM, Daniel Pocock <daniel@xxxxxxxxxxxxx> wrote:

Is it possible to contribute a small test case reproducing the problem
that we can include in the code base under resip/stack/test for example?

Do you have the same issue with a regular TLS socket?

Sure, this should work:

/***************************************************

 * test.cpp

 * Created on Wed Jun 12 20:07:58 GMT 2013 by alex

 *

 * $Author$

 * $Rev$

 * $Date$

 ***************************************************/

#include <resip/dum/DialogUsageManager.hxx>

#include <resip/stack/ssl/Security.hxx>

#include <resip/stack/SipStack.hxx>

#include <resip/stack/UdpTransport.hxx>

using namespace resip;

void afterSocketCreationFunction(Socket sock, int transport, const char *file, int line)

{

}

int main()

{

  Security *sec = new Security("/home/alex/sip_cert");

  SipStack sip_stack(sec, DnsStub::EmptyNameserverList, 0, false, &afterSocketCreationFunction);

  DialogUsageManager dum(sip_stack);

  dum.addTransport(TLS, 5061, V4, Data::Empty, "alex.exarionetworks.com");

  return 0;

}

 

--

><>
Nathan Stratton                                               Founder, CTO Exario Networks, Inc.
nathan at robotics.net                                     nathan at exarionetworks.com

http://www.robotics.net                                   http://www.exarionetworks.com/

Building the WebRTC solutions today that your customers will demand tomorrow.