[SR-Users] problems to parse Cseq 0 value

David Escartin descartin at bts.io
Mon Jun 4 12:25:04 CEST 2018


hello all

we have seen that when an OPTIONS is sent with CSep: 0 OPTIONS, message 
is not parsed.
Jun  4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: 
ERROR: <core> [core/parser/parse_cseq.c:61]: parse_cseq(): no method found
Jun  4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: 
ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
Jun  4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: 
ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
Jun  4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: 
ERROR: <core> [core/parser/msg_parser.c:331]: parse_headers(): bad 
header field [CSeq: 0
Jun  4 10:12:09 proxy-1-aws /usr/local/kamailio/sbin/kamailio[2205]: 
WARNING: <core> [core/receive.c:198]: receive_msg(): parsing relevant 
headers failed
as far i see in rfc3261
"The
    sequence number value MUST be expressible as a 32-bit unsigned
    integer and MUST be less than 2**31."

i don't know if you already discussed about this, but do you think it 
would be something to fix?

best regards and thanks a lot
david escartin



More information about the sr-users mailing list