Hi Oliver,

What version are you using?
Actually, the parser had been rock solid so far. Anyway, if the header
can not be dealt with, the processing of the packet resumes. Maybe it
would be worth posting the whole log of packet processing.
If you don't have any customized module and are convinced it's ser's
fault, it might be good to open a bug report and attach the core.

WL.

ps. The instance from iptel.org seems to survive pretty well ;).

olivier.taylor wrote:
  

When there is a space between sip: and the uri in the headers, I get a core dump.
I have patch my ser.cfg and it's ok now, but I think this is a bug, even if the 
headers are incorrects.

Olivier

    if (method =="REGISTER")
     {
      if (search("^From: <sip:[ ].*"))  {       
            xlog("L_NOTICE", "Bad From Header...Express Talk");
            break;
        };
    };
solve the problem, but...



REGISTER sip:brol.com SIP/2.0.
Via: SIP/2.0/UDP xx.xx.148.109:63521;rport;branch=z9hG4bK422760.
Max-Forwards: 20.
To: <sip: 990005180@brol.com>.
From: <sip: 990005180@brol.com>;tag=8312.
Call-ID: 1151739691-2760-PHOTO@192.168.0.11.
CSeq: 39 REGISTER.
Contact: <sip: 990005180@xx.xx.148.109:63521>;expires=3600;q=0.90.
User-Agent: Express Talk 1.04.
Content-Length: 0.


Jul  1 13:32:04 finalcut ser[44275]: ERROR: get_hdr_field: bad to header
Jul  1 13:32:04 finalcut ser[44275]: find_first_route: Error while parsing headers
Jul  1 13:32:04 finalcut ser[44275]: ERROR: get_hdr_field: bad to header
Jul  1 13:32:04 finalcut ser[44275]: ERROR:parse_from_header: bad msg or missing 
FROM header
Jul  1 13:32:05 finalcut kernel: pid 44275 (ser), uid 0: exited on signal 11 
(core dumped)

  
------------------------------------------------------------------------

_______________________________________________
Serusers mailing list
Serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers