Custom Query (2195 matches)

When calling pjsip_resolve() on an IPv4 address, we will return both the IPv4 address and its synthesized IPv6 address (if any).

Note that since pjsip_resolve() has no information of the NAT64 mode nor the bound transport, it will still return the IPv6 address.

See also ticket #1976.

This ticket will enable TURN client to establish TCP connection with the client's peers:

client <--[tcp]--> TURN server <--[tcp]--> peer

The RFC 6062 describes two modes: open outgoing TCP connection to peer and accept incoming TCP connection from peer, this ticket implements only the latter mode, i.e: accept mode.

General flow for accept mode:

1. Client establishes TCP connection to TURN server, this is called control connection.
2. Client sends Allocate request with REQUESTED-TRANSPORT attribute with value set to TCP.
3. Client sends CreatePermission request to allow peer to initiate TCP connection to TURN server.
4. When peer initiates TCP connection to the allocated address on TURN server, client will receive ConnectionAttempt indication with CONNECTION-ID attribute.
5. If client decides to accept the connection, it should establish another TCP connection to TURN server, this connection is for data connection.
6. Client sends ConnectionBind request on that data connection with CONNECTION-ID attribute with value set to the same value in previous ConnectionAttempt indication.
7. Once client receives ConnectionBind success response, the data connection is fully established, the TURN server will simply relay data until any side closes the connection.

How to use

TURN socket application needs to do the following:

1. When calling pj_turn_sock_create(), conn_type must be set to PJ_TURN_TP_TCP.
2. When calling pj_turn_sock_alloc(), param.peer_conn_type must be set to PJ_TURN_TP_TCP.
3. Implement TURN socket callbacks on_connection_attempt and on_connection_status, please check the TURN socket docs for more info.
4. The rest is as usual, e.g: sending data can be done using pj_turn_sock_sendto(), incoming data will be notified via callback on_rx_data.

Thank you Guillaume Roguez and Sébastien Blin from Savoir-faire Linux for the patch.

Stack trace:

pjsua_call_on_incoming()
pjsip_dlg_respond(dlg, rdata, sip_err_code, NULL, NULL, NULL);
pjsip_dlg_create_response()
pjsip_endpt_create_response()

There is a possibility, when media initialization fails, that sip_err_code is never set (the value is still zero), hence resulting in the assertion in pjsip_endpt_create_response():

PJ_ASSERT_RETURN(st_code >= 100 && st_code <= 699, PJ_EINVAL);