Differences

This shows you the differences between two versions of the page.

--- devel:completing_outbound [2013/02/20 15:35] – [Work required to complete registrar support] oej
+++ devel:completing_outbound [2013/03/29 01:48] (current) – pdunkley
@@ Line 1: / Line 1: @@
 This page contains some notes describing the work to fully complete outbound (RFC 5626) support on Kamailio.  It is believed that the current Kamailio feature set is sufficient to provide separate Edge Proxy and Registrar servers supporting outbound.
-===== Work required to complete registrar support =====
-  * registrar module
-    * New exported function allowing a specific contact to be removed (to be used when Edge Proxy returns 430 to the registrar)
-    * Add a required header in mode 2 if the client supports outbound.
-    *
-<code>If outbound registration succeeded, as indicated by the presence of
-   the outbound option-tag in the Require header field of a successful
-   registration response, the UA begins sending keep-alives as described
-   in Section 4.4.
-   </code>
-    * Support for RFC 5626 section 6:
-<code>
-   When receiving a REGISTER request, the registrar MUST check from its
-   Via header field if the registrar is the first hop or not.  If the
-   registrar is not the first hop, it MUST examine the Path header of
-   the request.  If the Path header field is missing or it exists but
-   the first URI does not have an "ob" URI parameter, then outbound
-   processing MUST NOT be applied to the registration.  In this case,
-   the following processing applies: if the REGISTER request contains
-   the reg-id and the outbound option tag in a Supported header field,
-   then the registrar MUST respond to the REGISTER request with a 439
-   (First Hop Lacks Outbound Support) response; otherwise, the registrar
-   MUST ignore the "reg-id" parameter of the Contact header.
-</code>
 ===== Single-server (combined edge proxy and registrar) =====
   * registrar module