SIP Trunk with provider - Errors in log

LPV · March 31, 2020, 3:05pm

Hi
Some time ago the log file of Asterisk 16.9 working under FreePBX 15.0.16.44 start contain a lot of errors
Log:
[2020-03-31 17:52:59] ERROR[2329] pjproject: sip_parser.c Error parsing ‘2151816229’: String value was greater than the maximum allowed value.
[2020-03-31 17:52:59] ERROR[2329] pjproject: sip_transport.c Error processing 659 bytes packet from UDP Operator_IP:5060 : PJSIP invalid value error exception when parsing ‘CSeq’ header on line 8 col 18:
OPTIONS sip:My_Phone_number_1@My_IP:5060;line=heglkyo SIP/2.0
Via: SIP/2.0/UDP Operator_IP;rport;branch=z9hG4bKHtg9y4ZDamj8F
Route: <sip:My Phone number 1@My IP:5060>
Max-Forwards: 70
From: sip:mod_sofia@Operator_IP:5060;tag=73D0BQg8eeSvr
To: sip:My_Phone_number_1@Operator_IP
Call-ID: 1f50fa31-6943-43b9-b6c1-6d753eef59fa_e553e58f-2017-4c99-abb7-0cb54c9d9612
CSeq: 2151816229 OPTIONS
Contact: sip:mod_sofia@Operator_IP:5060
User-Agent: SmartSBC-3.20.7-rc4
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Length: 0

– end of packet.
[2020-03-31 17:52:59] ERROR[2329] pjproject: sip_parser.c Error parsing ‘2151816230’: String value was greater than the maximum allowed value.
[2020-03-31 17:52:59] ERROR[2329] pjproject: sip_transport.c Error processing 659 bytes packet from UDP Operator_IP:5060 : PJSIP invalid value error exception when parsing ‘CSeq’ header on line 8 col 18:
OPTIONS sip:My_Phone_number_2@My_IP:5060;line=fzmmfmw SIP/2.0
Via: SIP/2.0/UDP Operator_IP;rport;branch=z9hG4bKj3910ZgH7v8tB
Route: sip:My_Phone_number_2@My_IP:5060
Max-Forwards: 70
From: sip:mod_sofia@Operator_IP:5060;tag=8c7rDj1BcQFFm
To: sip:My_Phone_number_2@Operator_IP
Call-ID: ab4016e3-aa80-491c-8f64-0f2cbced0ee5_e1a6f94e-0b2a-4a21-a0a7-34b1a075c304
CSeq: 2151816230 OPTIONS
Contact: sip:mod_sofia@Operator_IP:5060
User-Agent: SmartSBC-3.20.7-rc4
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Length: 0

– end of packet.

Can anybody say what happen’s?

cynjut · April 7, 2020, 2:22pm

After waiting this week with no help, I’d suggest switching over to a bug report. I’m going to guess your ITSP is sending you traffic that PJ-SIP doesn’t like, but other than that, unless it’s causing a connectivity issue, I’d say ignore it.

Whether it’s causing you problems or not, it’s probably something that needs a ticket and perhaps a discussion with your Tier 2 tech support at your ITSP.