Well, the modules will be quite dependent on headers like asserted and preferred identities. For example, the IMS registrar module we are working on will need these header to do the IMS AKA (Authentication and Key Agreement)

On Wed, Nov 2, 2011 at 5:01 PM, Olle E. Johansson <oej@edvina.net> wrote:

2 nov 2011 kl. 15:51 skrev Jason Penton:

> Hi all,
>
> I wanted to ask the community what the best way forward is for incorporating new SIP (IMS specific) headers into Kamailio. Right now I see two ways:
>
> 1. incorporating into existing parser framework in Kamailio
> 2. Leave it up to individual modules to independently parse for appropriate IMS headers.

3. Leave it to the configuration script to handle

>
> I would think 1 would be the best option?
>
> Here are some examples of the extension headers:
> http://docs.redhat.com/docs/en-US/JBoss_Communications_Platform/5.0/html/SIP_Servlets_Server_User_Guide/sect-SIP_and_IMS_Extensions.html#tab-IMS_P-Header_Extensions
>

The big question is really which of these that NEED logic in modules and not in the configuration script.

/O

_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev