%% You should probably cite rfc5626 instead of this I-D. @techreport{ietf-sip-outbound-20, number = {draft-ietf-sip-outbound-20}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-sip-outbound/20/}, author = {Rohan Mahy and Francois Audet and Cullen Fluffy Jennings}, title = {{Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)}}, pagetotal = 50, year = 2009, month = jun, day = 10, abstract = {The Session Initiation Protocol (SIP) allows proxy servers to initiate TCP connections or to send asynchronous UDP datagrams to User Agents in order to deliver requests. However, in a large number of real deployments, many practical considerations, such as the existence of firewalls and Network Address Translators (NATs) or the use of TLS with server-provided certificates, prevent servers from connecting to User Agents in this way. This specification defines behaviors for User Agents, registrars, and proxy servers that allow requests to be delivered on existing connections established by the User Agent. It also defines keep-alive behaviors needed to keep NAT bindings open and specifies the usage of multiple connections from the User Agent to its registrar. {[}STANDARDS-TRACK{]}}, }