Where is this shit bro ? i need this  

https://dect.snom.com/M400/M400_v0650_b0002.fwu  

profilePicture

Chris GAR

$userLabel.Name

Joined: 17.03.2023

12 Comments

  1. So Fa

    Apr 05, 2023

    Gibt es hier eine Lösung zu? Stehe vor der selben Herausforderung.

  2. Benjamin Gasser

    Apr 18, 2023

    +1

  3. Gianmaria Tononi

    Apr 18, 2023

    Hi,

    The firmware 650B2 for the M400 was pulled from our server due to some issues we verified on it, and it isn't publicly available, our developers are working on a new release but we do not have a time frame for now.

    Thank you

  4. Chris GAR

    Apr 18, 2023

    Okay thank you ! 

  5. Benjamin Gasser

    Apr 19, 2023

    Thanks for the quick reply! With my new purchased M400, I am on stock version 610B4. I try to connect to my local 3CX SBC 18.1.36 and fail. Do you know if 610B4 firmware is working with 3CX SBC version 18.1.36, or do I require the 650B2?

    1. Chris GAR

      Apr 19, 2023

      Hi, 

      Our M400 in 610.3 works on the SBC 18.1.36 but I think it is more stable on the 650.2  

  6. Benjamin Gasser

    Apr 19, 2023

    Thanks a lot, Chris GAR! In SIP Log of the M400, it states

    Received from udp:192.168.0.101:5060 at 19/04/2023 10:04:21  (378 bytes)
    SIP/2.0 500 Server Internal Error

    So I think there's something wrong with the SBC. It runs on a Raspberry Pi 4, and in 3CX Start-Up edition, the SBC appears online (with that green square symbol).

    Any idea?

    1. Chris GAR

      Apr 19, 2023

      If the SBC comes up correctly, I advise you to look at the SNOM instead, check if the outbound proxy is the IP of your SBC. In principle, nothing specific, here is my configuration for the SNOM if that can help you.

      1. Benjamin Gasser

        Apr 19, 2023

        Thanks a lot for your assistance, highly appeciated! My settings seem to be fine, and in the log message, 192.168.0.101 is the 3CX SBC. What I found out further is this in the SIP Log:

        Sent to udp:224.0.1.75:5060 at 19/04/2023 10:04:21  (718 bytes)

        SUBSCRIBE sip:MAC%3a000[…M400-Mac-address…]@224.0.1.75 SIP/2.0
        […]

        Received from udp:192.168.0.101:5060 at 19/04/2023 10:04:21  (378 bytes)

        SIP/2.0 500 Server Internal Error

        […]

        So, the M400 tries to connect to 224.0.1.75 – I am not quite sure, if the Server Internal Error is caused by the SBC or that IP address 224.0.1.75, where it tries to connect to.

        Edit: I just learnt that 224.0.1.75 seems to be a SIP multicast address. So, it seems like the Server Internal Error was caused and given by the SBC.

        1. Chris GAR

          Apr 19, 2023

          Does it work in STUN?
          This would allow to check if the SBC is working properly.

          1. Benjamin Gasser

            Apr 19, 2023

            I don't have any STUN devices, just the M400 and the M85s. With the mobile apps on Android and iOS, things are working well.

            Update: I set up an SBC on my Windows office machine (192.168.11.52). Same behaviour in SIP Log of M400 also here:

            […]
            Received from udp:192.168.11.52:5060 at 19/04/2023 14:44:10  (381 bytes)
            SIP/2.0 500 Server Internal Error
            […]

            1. Benjamin Gasser

              Apr 20, 2023

              It works today. I have no clue why.

              Thanks again, Chris GAR, for your efforts!