500 Internal Server Error. from Yealink Phones on BLF Notify

Status
Not open for further replies.

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,414
376
83
Happy New Year everyone!

Just to let you know that this issue is happening again on my platform. Not sure if it is CSeq related as mentioned in the post above because my CSeq numbers for NOTIFY messages are still quite high:

Code:
U 2021/01/01 10:40:06.214221 999.999.999.99:1058 -> 888.888.888.888:5060 #68
SIP/2.0 500 Internal Server Error.
Via: SIP/2.0/UDP 888.888.888.888:5060;rport=5060;branch=z9hG4bKNQ7p372gtmNmB.
From: <sip:202@a2es.myprovider.co.uk:5060>;tag=CC18HJi5wO6B.
To: "201" <sip:201@a2es.myprovider.co.uk:5060>;tag=2367660458.
Call-ID: 0_1879127281@192.168.126.43.
CSeq: 1918703 NOTIFY.
User-Agent: Yealink SIP-T46S 66.84.0.90.
Retry-After: 10.
Content-Length: 0.

Clearly now I need to reboot all my phones, but obviously do not want them all re-registering all at once. I can feel a bit of script programming coming on...
 

screwloose

Member
Feb 5, 2017
49
9
8
40
Happy New Year everyone!

Just to let you know that this issue is happening again on my platform. Not sure if it is CSeq related as mentioned in the post above because my CSeq numbers for NOTIFY messages are still quite high:

Code:
U 2021/01/01 10:40:06.214221 999.999.999.99:1058 -> 888.888.888.888:5060 #68
SIP/2.0 500 Internal Server Error.
Via: SIP/2.0/UDP 888.888.888.888:5060;rport=5060;branch=z9hG4bKNQ7p372gtmNmB.
From: <sip:202@a2es.myprovider.co.uk:5060>;tag=CC18HJi5wO6B.
To: "201" <sip:201@a2es.myprovider.co.uk:5060>;tag=2367660458.
Call-ID: 0_1879127281@192.168.126.43.
CSeq: 1918703 NOTIFY.
User-Agent: Yealink SIP-T46S 66.84.0.90.
Retry-After: 10.
Content-Length: 0.

Clearly now I need to reboot all my phones, but obviously do not want them all re-registering all at once. I can feel a bit of script programming coming on...
Is this because of the year changing to 2021 if they were first registered in 2020?
 

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,414
376
83
Is this because of the year changing to 2021 if they were first registered in 2020?

It is certainly something to do with the year changing, some of these phones where first registered in 2018, some in 2020 and the same issue has occurred every New Year.

It may well be related to the CSeq number being generated by FreeSWITCH following the roll over into the New Year. I do have some Windows based BLF/Messaging applications that I wrote using Qt (https://www.qt.io/) and the PjSIP library (https://www.pjsip.org/). Some, but not all, installations of this application, that had been left running over the New Year, started complaining about invalid CSeq numbers.

As you can see, I don't have any conclusive proof as to what was really happening.
 
Status
Not open for further replies.