7960s don't register completely when devstate button is configured

[sgofferj]

I installed asterisk and chan-sccp after a hardware failure on a new Raspberry Pi. My 7960s don't register completely. sccp show devices show their regstate as "Progress" and depending on the asterisk version, interacting with the phones leads to deadlocks of the asterisk. My 7970 registers and works fine. I'll dig out an 7905 and an ATA for testing later.

Reproduction Steps:
unclear

chan-sccp version: (include revision and/or branch if relevant)
Tested with release 4.3.3 and latest git

asterisk version: (include revision and/or branch if relevant)
tested with 16.16, 18.1.1 and 18.2.0

Expected behavior:
Phones register

Observed behavior:
Phones don't register

Screenshots
See below.

Addition / Optional Information:

• Problem started happening recently, didn't happen in an older version of Chan-SCCP: Yes
• Problem can be reliably reproduced, doesn't happen randomly: No
• Platform:
  • Raspberry Pi 3B
  • 64 Bit Ubuntu 20.04

Only debug info I got so far is

    -- SCCP: Alarm Message: Severity: Major (7), 27: Waiting for Requesting Feature Key Status From 192.168.10.203 [14/-888493888]

with .203 being the IP of the asterisk.

[sgofferj]

[sgofferj]

7905 registers fine and works but the speeddials from the config don't show up in the phone.

Edit: On a hunch I removed a devstate feature button I had on the 7960 and they register and work fine now. The same devstate button works fine on the 7970 though.

[sgofferj]

Recompiled now with asterisk 18.2.0 and latest git and same symptoms.Without the devstate button, the phones register fine. With the devstate button, they hang. I captured a full asterisk startup with the requested debug params:

asterisk_start.log

About using a release from earlier this year - I actually used the 4.3.3 release from December last year for testing :).

[dkgroot]

After the devstate changes (middle last year), i ran all the tests on > 7961 and 89xx. Which would explain why it was not uncovered.
The registration process getting as far as it does would indicate the devices don't like one of the messages being sent to them.
Sorry it will take me a little bit of time before i can have a look and test it out on a physical 7960. Happy to see that without the devstate it works fine.

It clearly does not like something of what was sent to it.

    -- SEP00036BC9817D: Set softkeyset to ONHOOK(0) on line 0  and call 0
    -- SEP00036BC9817D: validKeyMask 4294967294
       > SEP00036BC9817D: set poll timeout 53 for session 33
    -- SEP00036BC9817D: Looking for line with instance 5.
    -- SEP00036BC9817D: No line found with instance 5.
       > SEP00036BC9817D: set poll timeout 53 for session 33
    -- SEP00036BC9817D: Looking for line with instance 4.
    -- SEP00036BC9817D: No line found with instance 4.
       > SEP00036BC9817D: set poll timeout 53 for session 33
    -- SEP00036BC9817D: Looking for line with instance 3.
    -- SEP00036BC9817D: No line found with instance 3.
       > SEP00036BC9817D: set poll timeout 53 for session 33
    -- SEP00036BC9817D: Looking for line with instance 2.
    -- SEP00036BC9817D: No line found with instance 2.
       > SEP00036BC9817D: set poll timeout 53 for session 33
    -- SEP00036BC9817D: Looking for line with instance 1.
    -- SCCP: Found line 6002
       > SEP00036BC9817D: set poll timeout 53 for session 33
       > SEP00036BC9817D: set poll timeout 53 for session 33
    -- SEP00036BC9817D: Received Feature Change Event: devstate(29)

As communication stopped immediately after the devstate event happened. It might help to have the phones debug log as well, if it doesn't immediately disconnects at this moment in time.

The secondary issue where asterisk is locked up when you dial a partially registered phone will have to researched as well, and certainly needs fixing too.

[sgofferj]

If you tell me how to get a debug log from a 7960, I can probably produce one.