I would like to use a SIM7600X 4G Expansion Board (like this one) to connect my raspberry pi to the mobile network.

In this raspberry pi I am also running an XMPP server.

I want to then create an account that will bridge SMS messages between the SIM7600 and my XMPP account (should be easy), and ideally it should also be able to bridge phone calls (might be difficult?).

I know about the XMPP-VoIP JMP.chat, and since they are open source I can get some inspiration from them.

I will try to implement something myself, but I am not an amazing programmer. So I am wondering whether there is already some open source project that is more tailored for this application.

  • 667@lemmy.radio
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    If I understand what I’ve read, you may be interested in a SIP software called asterisk. It may do what you’re looking for.

  • solrize@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    That’s a nice little board! Web search SIM7600X finds various code you can use. Idk if asterisk can support it directly though.

    Another possibility might be to use a consumer mobile phone I guess.

    I wonder if there might be a 5g version of the board sometime.

    • TheHolm@aussie.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      8 months ago

      Very strange line from specs.
      USB Driver Windows XP/7/8/10/11, Linux (driver free on Raspberry Pi Raspbian system)
      Does it mean binary blob driver only? and you need to pay for it to use it on PC?

      • solrize@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 months ago

        I think it means that on Linux, no driver is needed (“driver-free” = free of drivers) since it uses the kernel USB stack. On windows there may be a USB driver that gets loaded. But you’re right, it’s ambiguous.

      • SpicyAnt@mander.xyzOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        8 months ago

        Yeah, it is written funny. But what it means is that the Linux kernel already comes pre-packaged with the drivers necessary to communicate using the protocol used by this device (UART or USB). These Linux drivers (and by extension Raspbian) are natively capable of interfacing via the GPIO pins or via the USB connectors. It is not true that the device is “driver free” as you always need a driver for this, what they meant is that it is not necessary to install any additional drivers for Linux. So “free from installation” I suppose.

        Windows does not come pre-packaged with these drivers, so you need to install them if you want to interface with the device via USB. The chip that the board uses for the UART -> USB conversion is the CP2102. This chip is a common chip used in some ESP32 boards, and I think it would work fine with the standard CP210x driver. But on their site they do provide a specific driver for free (SIMCOM_Windows_USB_Drivers_V1.0.2.exe)

    • SpicyAnt@mander.xyzOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      8 months ago

      I agree, it looks like a nice board!

      But… after ordering it I noticed that while the pictures in the website show the “SIM7600G-H” chip - which supports global GSM and LTE bands - the text description specifies that the chip included in the kit is the “SIM7600CE-T”, which supports the Chinese bands. I am not sure I will get the correct version now 😅 But there are other “SIM7600G-H” modules and USB dongles available out there, and from what I have found this chip is a nice option for GSM/LTE projects.

      • SpicyAnt@mander.xyzOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        The board finally arrived and it is indeed the SIM7600G-H, which is the global version.

        I tried it on my raspberry pi 5 and struggled a bit because there was a change to the UART interface between the PI 4 and PI 5 and the documentation on this board describes the PI 4. But, after some fiddling around I figured out the correct setting and got it to work. The main difference is that the “UART0” needs to be explicitly turned on because the default debugging UART now uses the UART10 interface that is somewhere else on the board.