devel:completing_outbound
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
devel:completing_outbound [2013/01/08 10:45] – created pd | 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. | This page contains some notes describing the work to fully complete outbound (RFC 5626) support on Kamailio. | ||
- | |||
- | ===== 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) | ||
- | * Support for RFC 5626 section 6: | ||
- | < | ||
- | 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 | ||
- | | ||
- | the request. | ||
- | the first URI does not have an " | ||
- | | ||
- | 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 | ||
- | | ||
- | MUST ignore the " | ||
- | </ | ||
===== Single-server (combined edge proxy and registrar) ===== | ===== Single-server (combined edge proxy and registrar) ===== |
devel/completing_outbound.1357641956.txt.gz · Last modified: 2013/01/08 10:45 by pd