[Serusers] pa module

[Jamey Hicks]

Rafael Morón wrote:

> Hi,
>  
>     I am trying to configure latest ser from cvs with pa module, but I 
> haven't succeeded yet. When I run ser, and try to connect from a SIP 
> client, I get the following errors:
>  

Which SIP client?

>
> 10(30497) parse_hfs(): Error while parsing headers
> 10(30497) pa_handle_registration(): Error while parsing headers
> 10(30497) WARNING: script writer didn't release transaction
> 15(30502) parse_hfs(): Error while parsing headers
> 15(30502) pa_handle_registration(): Error while parsing headers
> 15(30502) WARNING: script writer didn't release transaction
> 13(30500) parse_hfs(): Error while parsing headers
> 13(30500) pa_handle_registration(): Error while parsing headers
> 13(30500) WARNING: script writer didn't release transaction
> 10(30497) parse_hfs(): Error while parsing headers
> 10(30497) pa_handle_registration(): Error while parsing headers
> 12(30499) parse_hfs(): Error while parsing headers
> 12(30499) pa_handle_registration(): Error while parsing headers
> For handling presence, I use this code in ser.cfg:
>  
> if(t_newtran()){
>  if (method=="REGISTER"){
>   pa_handle_registration("registrar");
>   break;
>  };
>  
>  if (method=="SUBSCRIBE"){
>   handle_subscription("registrar");
>   break;
>  };
>  if (method=="PUBLISH"){
>   handle_publish("registrar");
>   break;
>  };
> };

I only create the new transaction once it is known that the method is 
SUBSCRIBE, or PUBLISH.  It also appears that pa_handheld_registration 
might not be needed or has a problem.  I'm not using it now, anyway.

While debugging, I add something like the following to the subscribe clause:
  exec_msg ("cat >> /tmp/subscribe.log");

That way you can send a message transcript to me and I can figure out 
why it has trouble parsing the headers.

Thanks,
Jamey