[Serusers] Problem with UAC modules

[Mohammad Khan]

Was I right using the patch file?
Do I need to apply the patch or not?

Thanks,
MOhammad


Marian Dumitru wrote:

> Hi Mohammad,
>
> see my inline comments.
>
> regards,
> Marian
>
> Mohammad Khan wrote:
>
>> I am using ser downloaded from cvs (cvs co -r HEAD sip_router, 
>> download on June 08, 2005 12:30 PM EST)
>> I used the patch file found in modules/uac/doc/replace_from.patch. 
>> (Did I do right?)
>>
>> I am getting below, while trying to start ser
>> Jun  8 18:37:18 sip ser: set_mod_param_regex: parameter <db_url> not 
>> found in module <acc>
>> Jun  8 18:37:18 sip ser: parse error (49,20-21): Can't set module 
>> parameter
>> Jun  8 18:37:18 sip ser: set_mod_param_regex: parameter <db_flag> not 
>> found in module <acc>
>> Jun  8 18:37:18 sip ser: parse error (86,19-20): Can't set module 
>> parameter
>> Jun  8 18:37:18 sip ser: set_mod_param_regex: parameter 
>> <db_missed_flag> not found in module <acc>
>> Jun  8 18:37:18 sip ser: parse error (87,19-20): Can't set module 
>> parameter
>> Jun  8 18:37:18 sip ser: ERROR: bad config file (3 errors)
>
>
> enable mysql support in modules/acc/Makefile - need to uncomment some 
> lines and recompile the module.
>
>>
>> After uncomment acc module (just to see if it works without acc)
>> I am getting these:
>> Jun  8 18:50:48 sip /usr/sbin/ser[3076]: 
>> ERROR:uac:get_autenticate_hdr: reply has no auth hdr 
>> (Proxy-Authenticate)
>> Jun  8 18:50:48 sip /usr/sbin/ser[3076]: ERROR:uac:uac_auth: failed 
>> to extract authenticate hdr
>
>
> you get these messages because (probably) the reply has no 
> "Proxy-Authenticate" hdr. It will be better if you could post ser 
> output with debug=9  and also the net trace.
>
>> Jun  8 18:50:48 sip /usr/sbin/ser[3074]: Warning: sl_send_reply: I 
>> won't send a reply for ACK!!
>> Jun  8 18:50:49 sip /usr/sbin/ser[3076]: Warning: sl_send_reply: I 
>> won't send a reply for ACK!!
>> Jun  8 18:50:51 sip /usr/sbin/ser[3075]: Warning: sl_send_reply: I 
>> won't send a reply for ACK!!
>>
>
> Most probably, some scripting errors - trying to reply to ACK.
>