Hi all, I have a problem with simpleua where I want to specify the transport as UDP, TCP or SCTP. I attempt to call bob and I specify the transport as UDP (I know this is an optional parameter in the case of UDP) - see first line of log. This is handled and the port is resolved - see line x17:01:44.732. When the ACK is sent the transport is now 'unspecified' - see line x17:01:44.924. This happens for all transport types. On debugging it appears that pjsip_host_info contains nothing so the app tries to send it via UDP (the default) and then times out for TCP and SCTP based calls. Is this a bug in simpleua or am I doing something wrong? Does the same thing happen in pjsua? Background: we're using simpleua as a test application for using SCTP as a transport. We can workaround this problem but it breaks the use of other transport types. On a positive note, we've made calls using SCTP between two multi-homed PCs using two different wired networks. When we remove the cable on the active network, the call continues on the other network. ./simpleua-i686-pc-linux-gnu 'sip:bob at 192.168.101.23;transport=udp' . 17:01:44.692 udp0x80d7e34 SIP UDP transport started, published address is 192.168.101.160:5060 . 17:01:44.732 dlg0x81183ec UAC dialog created 17:01:44.732 dlg0x81183ec Module mod-invite added as dialog usage, data=0x8118ec0 17:01:44.732 dlg0x81183ec Session count inc to 2 by mod-invite 17:01:44.732 dlg0x81183ec Module mod-100rel added as dialog usage, data=0x8119afc 17:01:44.732 dlg0x81183ec 100rel module attached 17:01:44.732 inv0x81183ec UAC invite session created for dialog dlg0x81183ec 17:01:44.732 endpoint Request msg INVITE/cseq=101 (tdta0x8119bb8) created. 17:01:44.732 inv0x81183ec Sending Request msg INVITE/cseq=101 (tdta0x8119bb8) 17:01:44.732 dlg0x81183ec Sending Request msg INVITE/cseq=101 (tdta0x8119bb8) 17:01:44.732 tsx0x811ac24 Transaction created for Request msg INVITE/cseq=100 (tdta0x8119bb8) 17:01:44.732 tsx0x811ac24 Sending Request msg INVITE/cseq=100 (tdta0x8119bb8) in state Null x17:01:44.732 sip_resolve.c Target '192.168.101.23:0' type=UDP resolved to '192.168.101.23:5060' type=UDP 17:01:44.732 tsx0x811ac24 State changed from Null to Calling, event=TX_MSG 17:01:44.733 dlg0x81183ec Transaction tsx0x811ac24 state changed to Calling 17:01:44.733 simpleua.c Call state changed to CALLING 17:01:44.734 sip_endpoint.c Processing incoming message: Response msg 180/INVITE/cseq=100 (rdata0x80d8244) 17:01:44.734 tsx0x811ac24 Incoming Response msg 180/INVITE/cseq=100 (rdata0x80d8244) in state Calling 17:01:44.734 tsx0x811ac24 State changed from Calling to Proceeding, event=RX_MSG 17:01:44.734 dlg0x81183ec Received Response msg 180/INVITE/cseq=100 (rdata0x80d8244) 17:01:44.734 dlg0x81183ec Route-set updated 17:01:44.734 dlg0x81183ec Transaction tsx0x811ac24 state changed to Proceeding 17:01:44.734 simpleua.c Call state changed to EARLY 17:01:44.735 sip_endpoint.c Processing incoming message: Response msg 200/INVITE/cseq=100 (rdata0x80d8244) 17:01:44.735 tsx0x811ac24 Incoming Response msg 200/INVITE/cseq=100 (rdata0x80d8244) in state Proceeding 17:01:44.735 tsx0x811ac24 State changed from Proceeding to Terminated, event=RX_MSG 17:01:44.735 dlg0x81183ec Received Response msg 200/INVITE/cseq=100 (rdata0x80d8244) 17:01:44.735 dlg0x81183ec Route-set updated 17:01:44.735 dlg0x81183ec Route-set frozen 17:01:44.735 dlg0x81183ec Transaction tsx0x811ac24 state changed to Terminated 17:01:44.735 simpleua.c Call state changed to CONNECTING 17:01:44.735 inv0x81183ec Got SDP answer in Response msg 200/INVITE/cseq=100 (rdata0x80d8244) 17:01:44.735 inv0x81183ec SDP negotiation done, status=0 . 17:01:44.924 inv0x81183ec Received Response msg 200/INVITE/cseq=100 (rdata0x80d8244), sending ACK 17:01:44.924 endpoint Request msg ACK/cseq=100 (tdta0x8122258) created. 17:01:44.924 dlg0x81183ec Sending Request msg ACK/cseq=100 (tdta0x8122258) * *x17:01:44.924 sip_resolve.c Target '192.168.101.23:0' type=Unspecified resolved to '192.168.101.23:5060' type=UDP 17:01:44.924 simpleua.c Call state changed to CONFIRMED /Netdabbler
