Hi Michele, This should have been fixed in ticket #1811 (https://trac.pjsip.org/repos/ticket/1811). Regards, Ming On Thu, May 7, 2015 at 11:41 PM, Michele Cicciotti <michele.cicciotti at privatewave.com> wrote: > If an account is created with a SIP/TLS registrar and contact_use_src_port > set to PJ_TRUE (the default), the hostname of the server will be > unavailable. If the transport was created with verify_server set to PJ_TRUE, > all secure connections will fail, because there will be no server name to > match to the server certificate > > The cause is that, if contact_use_src_port is set, pjsua_acc_get_uac_addr > will call pjsip_endpt_acquire_transport, which will call > pjsip_tpmgr_acquire_transport, which will create a new transport with a NULL > tdata. Since the TLS transport gets the server name from the first request's > tdata, if none is provided, the transport will be created without a server > name > > If contact_use_src_port is not set, the transport will be created as a side > effect of the SIP state machine, by the first message sent, which will have > a tdata with a server name set > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org