SIP Message Parsing Fails When CSeq Value Exceeds 2147483647
2025/11/04 17:23:54 ERROR failed to parse caller=TransportLayer caller=Transport<UDP> data="SIP/2.0 401 Unauthorized\r\nVia: SIP/2.0/UDP 192.168.120.12:45915;branch=z9hG4bK.wvgZuugWfGY4m8SG;rport=45915\r\nFrom: \"1001\" <sip:1001@localhost>;tag=xQndqRwRLoSmniHY\r\nTo: <sip:[email protected]>;tag=8vr47DHB26Q4D\r\nCall-ID: ab42e5de-db2b-4c86-a508-e95cede061ad\r\nCSeq: 2147483648 REGISTER\r\nUser-Agent: FreeSWITCH-mod_sofia/1.10.12-release-10222002881-a88d069d6f+git~20240802T210227Z~a88d069d6f~64bit\r\nAllow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE\r\nSupported: timer, path, replaces\r\nWWW-Authenticate: Digest realm=\"localhost\", nonce=\"beb91338-94e4-46ca-9d7f-c18c14549281\", stale=true, algorithm=MD5, qop=\"auth\"\r\nContent-Length: 0\r\n\r\n" **error="parsing header failed line=\"CSeq: 2147483648 REGISTER\": invalid CSeq 2147483648: exceeds maximum permitted value 2**31 - 1**"
Hi @bravpei . Welcome. Thanks for reporting. Yeah there is some work arround CSEQ on sipgo. Probably here is issue in building request.
@emiago Looking forward to your prompt fix