Community

Content

Page tree

Starting to implement D717 Deskphones running Firmware 10.1.141.10 (recommended 3CX version)

We see behaviour that these phones lose registration and after about 20 sec. the registration restores itself.
It now appears to happen everytime exactly after 2 min.
However no registration means the phone is unusable, for calling outbound or inbound.

Also found a recent thread about an D735 (although I do not know if this is the same reason, there it is even a more recent version.
And I prefer to use the 'stable' version of software.

profilePicture

Summa College Netwerkbeheer

End user

Joined: 07.02.2024

3 Comments

  1. End user Summa College Netwerkbeheer

    Currently looking in to the value user_expiry.
    This was set (out of the box) at 120 (which could explain the 2min.)

    In V6, 120 is not a valid value.
    In V7 it would be.

    Now testing with different values which are allowed for V6.

    user_expiry

  2. End user Summa College Netwerkbeheer

    3CX has new maintenance firmware as recommended.
    Our phones now run this firmware: 10.1.169.13

    However this makes no difference.
    I figured out that the 120 sec. value comes from 3CX server SNOM phone template.
    However changing it there now shows another value in the WEB UI of the SNOM phone.
    (Which in 3CX the phone gets a warning/fault, because of the use of a custom template)

    Although the behaviour is still the same.
    Values tried 3600 (which should be the default in SNOM perpective)
    And also 86400 (10 hour, just to check)

    Both still gave the behaviour of 120 sec. (even after multiple factory resets and reprovision actions)
     

    Further more, I do not believe adjusting the interval of the re-register action will change the behaviour.
    So I still think that If I set it to 10 hours, every 10 hours the phone would de-register (being unable to call or be called) and re-register after 20 sec.

    Also currently working with our supplier to try to get answer trough SNOM support.

    If I have a solution, I will post it here.

  3. End user Summa College Netwerkbeheer

    I managed to resolve this issue.
    It appears it has nothing to do with the user_expiry setting.

    There was a Cisco Firewall in the path from phone to 3CX server that still did SIP inspection in the Global Policy.
    This also uses a value of 2 minutes, so likely this was interupting with the SIP traffic.

    Using below guide I managed to disable SIP inspection.
    https://wrmem.net/index.php/2020/05/08/disable-sip-inspection-on-firepower-through-flexconfig/


    However, it still remains weird for me that there is such a big difference between SNOM default value (3600) and the value (120) provided from SNOM to 3CX to use with the 3CX server.
    https://service.snom.com/display/wiki/user_expiry