1.1. Conditions 1.2. Edge Proxy Keep-Alives (STUN) 1.3. Flow Timer This module provides C-API functions to enable Kamailio to be used as an outbound Edge Proxy (see RFC5626 section 5). The path and rr modules will bind to this module if it is loaded before they are. 1.1. Conditions The module analyses SIP requests so that other module (e.g. path, rr) can determine whether to apply RFC5626 processing. This section applies if outbound processing is not forced by the force_outbound_flag flag, or disabled with force_no_outbound_flag. REGISTER request: * single Via: header (first hop) and Contact: header has ;reg-id parameter Non-REGISTER requests if either of the following conditions is true: * top Route header URI is myself and has ;ob parameter * Supported: outbound... header, single Via: header, and Contact: header has ;ob parameter 1.2. Edge Proxy Keep-Alives (STUN) Outbound Edge Proxies MUST support STUN NAT keep-alives on their SIP UDP ports. Kamailio supports this though the “stun” module. 1.3. Flow Timer The maximum interval at which a User Agent must send a keep-alive may be specified by the Registrar using the Flow-Timer: header in 2xx responses to REGISTERs. When using TCP or TLS as the SIP transport care should be taken to set the “tcp_connection_lifetime” on the Edge Proxy to a value slightly larger than the interval the Registrar is using for flow timer. Setting “tcp_connection_lifetime” to less than the interval could cause connections to be lost, and setting it to
Copyright © 2012-2013 Crocodile RCS Ltd
