[OpenSIPS-Users] B2BUA help

[opensipslist at encambio.com]

Hello Anca,

An ven., févr 05, 2010, opensipslist at encambio.com schrieb:
>An ven., févr 05, 2010, Anca Vamanu schrieb:
>>If you use the trunk svn branch, you have a parameter in b2b_logic
>>module - "custom_headers". You can set it to "WWW-Authenticate,
>>Authorization" and the content of these headers will be passed on
>>the other side.
>>
>That's great, thanks Anca. I'll try out the new 'custom_headers'
>parameter.
>
I integrated your changes from revision 6291:

  'new feature - possibility to define costum headers to be
  passed from the dialog of one side to the other'

...and finally the WWW-Authenticate header arrived at my UAC (which
sent the first INVITE.) It sucessfully builds a Authorization string
and sends a second INVITE.

Unfortunately, b2b_logic doesn't pass on the Authorization header
from the client to the server so authorization is failing. The
module parameters of my script are:

  modparam("b2b_logic", "custom_headers", "WWW-Authenticate;Proxy-Authenticate;Authorization;Subject")

The page 'B2buaTutorial' says:

  If type node with message value is present, it means that the
  client will be created using the info from received SIP message:
  the body, the caller URI, some SIP headers(Accept, Supported,
  Content-Type).

It seems as if custom_headers are only passed from the server to the
client, or maybe b2b_logic only recognizes them in dialog (after the
first INVITE is accepted?)

Is it possible that the custom headers code from revision 6291 is
incomplete and that I should integrate SVN code from another
revision as well? Am I doing something else wrong when testing your
prepaid.xml scenario?

By the way your suggestion to separate headers with a comma probably
does not work because:

  p = strchr(custom_headers.s, ';');

...is what you wrote in b2b_logic.c.

Regards,
Brian