Looks to me that 3cx needs a ring group of 2 extensions. The first for your phone, the second configured to be connected with sip2mqtt. When someone calls, both extensions should “ring” which would make 3cx not go straight to busy.
I’ve been trying out the great @MartyTremblay docker using @raphii’s add-on structure.
I’ve been able to solve an issue with one of the voip providers I use, it constantly failed registration with error 407 (Proxy Authentication Required). After a lot of trial and error (lots of) I’ve found out that changing a parameter in the sip2mqtt.py script solved all my registration problems:
From this moment on, all my voip providers work, I was also able to connect to my pbx (Yeastar S20), which initially failed miserably with error 401; unfortunately it doesn’t seem to work perfectly, because it doesn’t trigger any action in the script when an incoming call happens, but this is for another day.
does not seem to work with Grandstream PBX which is Asterix-based. Always get 401 unauthorized. I have not tried the edits suggested most recently by @CiBi69, but I will and will report back.
Basically what I am looking for is advanced callerID, similarly to other users, I use IVRs to answer the phone. With voip.ms, you can pair this script with a subaccount, add it into a ring group with your main account, and then both will register the call at the same time. The issue I’m having is the pbx answers the call pretty much instantly, so the caller ID is only displayed in hass for a brief moment. Anyone know how to retain and display the last caller?
This gives us the caller ID, but it does not give us the number that was dialed. If I point a bunch of DIDs at it, I would be interesting in comparing how many calls are made to each DID. I would prefer not to have to run a bunch of copies of the container! An example output would be comparing how many calls came in locally compared to 1-800.
Has anyone done anything creative with the data in HomeAssistant?
Nice, will try to use it simply with an existing fritzbox which is used for my doorbell (Doorline Slim). The doorbell works like an analog a/b phone and utilize sip2mqtt will enable home assistant to easily send push notifications including a still image from the surveillance cam!
Pretty sure this happens because the docker script is trying to build an x86 version of pjsip. Being a Raspberry Pi, we’d would have to change the configure command to build an ARM version of the binary. Any volunteers?
@derdude41065, did you ever get this to work with fritzbox? In my case sip2mqtt seems to register the sip extension just fine, but I do not see incoming calls in the protocol of sip2mqtt, nor the MQTT sensor is showing any change. sip2mqtt protocol:
04/27/2021 08:18:03 AM - INFO - -- Registration Complete --
04/27/2021 08:18:03 AM - INFO - SIP: Status = 100 (In Progress)
04/27/2021 08:18:03 AM - INFO - SIP: Registration complete, status=200 (OK)
04/27/2021 08:18:04 AM - INFO - MQTT: Connected with the broker...
If I place a call to the extension where sip2mqtt says it is registered to, I get the following log entry in fritzbox: 27.04.21 08:21:00 Internettelefonie mit tuerklingel über 172.30.xxx.xxx:5060 war nicht erfolgreich. Ursache: (408)
In Englisch: Internet call with device tuerklingel via IP was not successfull.
