Hello Anca, An ven., févr 05, 2010, Anca Vamanu schrieb: >[email protected] wrote: >> I've changed the parameters to: >> >> b2b_init_request("prepaid", >> "sip:[email protected]:5080;transport=tcp", >> "sip:[email protected]:5080;transport=tcp"); >> >> ...because name.host.tld is listening on TCP port 5080. >> Before, the B2BUA modules were sending over TLS, which is how >> the original INVITE from the UAC is sent. Is there a better way >> to tell the B2BUA modules to use TCP rather than another transport? >> >No, unfortunately there is no other way to tell b2b to use other >protocol. > It's probably enough to do it the way I described, but it seems like there must be a more elegant/consistent way to do transport changes.
>> My main question now, is that the host name.host.tld is getting the >> message, but challenging the B2BUA logic with a WWW-Authenticate 401 >> message. This gets passed implicitly back to the UAC which sent the >> INVITE, however it seems that the B2BUA modules strip the WWW- >> Authenticate header so that the UAC only sees a 'sanitized' >> 401 SIP message and cannot authenticate. >> >> How can I adjust the prepaid scenario to accommodate 401 challenges? >> >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. Regards, Brian _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
