PROBLEMI DI CHIAMATA IN USCITA

[massimo11979]

Con la nuova versione non riesco più a ricevere le chiamate da sip in rete utilizzo un hardware TG100 Yeastar.

[arnonym]

English please.

[massimo11979]

Inglese per favore.

With the new version, I can no longer receive SIP calls over the network using a Yeastar TG100 hardware. What has changed from version 5.3 to 5.4?

[arnonym]

Can you take a look at or post some logs?

[massimo11979]

Puoi dare un'occhiata o pubblicare alcuni log?

22:52:11.579 pjsua_core.c .TX 752 bytes Response msg 200/OPTIONS/cseq=102 (tdta0x14382640) to UDP 192.168.1.180:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.180:5060;rport=5060;received=192.168.1.180;branch=z9hG4bK1fbba725
Call-ID: 09cf730c5498559e3ba9ad5d709aefec@192.168.1.180
From: "Unknown" sip:Unknown@192.168.1.180;tag=as44e61b4b
To: sip:20001@192.168.1.78;ob;tag=z9hG4bK1fbba725
CSeq: 102 OPTIONS
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Accept: application/sdp, application/pidf+xml, application/xpidf+xml, application/dialog-info+xml, application/simple-message-summary, message/sipfrag;version=2.0, application/im-iscomposing+xml, text/plain
Supported: replaces, 100rel, timer, siprec, norefersub, trickle-ice
Allow-Events: presence, dialog, message-summary, refer
Content-Length: 0
--end msg--
22:52:11.579 pjsua_core.c .RX 559 bytes Response msg 200/REGISTER/cseq=62013 (rdata0x14378e08) from UDP 192.168.1.180:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.78:5060;branch=z9hG4bKPj1sqrB-wPLipYoOHNGOgHHy6U.e131Ve9;received=192.168.1.78;rport=5060
From: sip:20001@192.168.1.180;tag=OVDyQR7uqrIS.QrdrVCUpAmpyNBaclCO
To: sip:20001@192.168.1.180;tag=as5c0b458b
Call-ID: hqOkqBztu36HrgQ0NZfD0HIskqJcK4mB
CSeq: 62013 REGISTER
Server: TG100
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Expires: 300
Contact: sip:20001@192.168.1.78:5060;ob;expires=300
Date: Sun, 01 Feb 2026 21:52:11 GMT
Content-Length: 0
--end msg--
22:52:11.579 pjsua_acc.c ....SIP outbound status for acc 0 is not active
22:52:11.579 pjsua_acc.c ....Service-Route updated for acc 0 with 0 URI(s)
22:52:11.579 pjsua_acc.c ....sip:20001@192.168.1.180: registration success, status=200 (OK), will re-register in 300 seconds
22:52:11.579 pjsua_acc.c ....Keep-alive timer started for acc 0, destination:192.168.1.180:5060, interval:13s
| 22:52:11.579616 [1] OnRegState: 200 OK
22:52:12.572 pjsua_aud.c Closing sound device after idle for 1 second(s)
22:52:12.572 pjsua_aud.c .Closing null sound device..
22:53:31.582 pjsua_core.c .RX 523 bytes Request msg OPTIONS/cseq=102 (rdata0x14378e08) from UDP 192.168.1.180:5060:
OPTIONS sip:20001@192.168.1.78:5060;ob SIP/2.0
Via: SIP/2.0/UDP 192.168.1.180:5060;branch=z9hG4bK55cbcb24;rport
Max-Forwards: 70
From: "Unknown" sip:Unknown@192.168.1.180;tag=as0a32999f
To: sip:20001@192.168.1.78:5060;ob
Contact: sip:Unknown@192.168.1.180
Call-ID: 6888ecda436323ea166185f41066a44b@192.168.1.180
CSeq: 102 OPTIONS
User-Agent: TG100
Date: Sun, 01 Feb 2026 21:53:31 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Length: 0
--end msg--
22:53:31.582 pjsua_core.c .TX 752 bytes Response msg 200/OPTIONS/cseq=102 (tdta0x14376840) to UDP 192.168.1.180:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.180:5060;rport=5060;received=192.168.1.180;branch=z9hG4bK55cbcb24
Call-ID: 6888ecda436323ea166185f41066a44b@192.168.1.180
From: "Unknown" sip:Unknown@192.168.1.180;tag=as0a32999f
To: sip:20001@192.168.1.78;ob;tag=z9hG4bK55cbcb24
CSeq: 102 OPTIONS
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Accept: application/sdp, application/pidf+xml, application/xpidf+xml, application/dialog-info+xml, application/simple-message-summary, message/sipfrag;version=2.0, application/im-iscomposing+xml, text/plain
Supported: replaces, 100rel, timer, siprec, norefersub, trickle-ice
Allow-Events: presence, dialog, message-summary, refer
Content-Length: 0
--end msg--
22:54:51.584 pjsua_core.c .RX 523 bytes Request msg OPTIONS/cseq=102 (rdata0x14378e08) from UDP 192.168.1.180:5060:
OPTIONS sip:20001@192.168.1.78:5060;ob SIP/2.0
Via: SIP/2.0/UDP 192.168.1.180:5060;branch=z9hG4bK5bcbb3b5;rport
Max-Forwards: 70
From: "Unknown" sip:Unknown@192.168.1.180;tag=as66533a24
To: sip:20001@192.168.1.78:5060;ob
Contact: sip:Unknown@192.168.1.180
Call-ID: 1dd46060547355717c63c58d6b16e253@192.168.1.180
CSeq: 102 OPTIONS
User-Agent: TG100
Date: Sun, 01 Feb 2026 21:54:51 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Length: 0
--end msg--
22:54:51.584 pjsua_core.c .TX 752 bytes Response msg 200/OPTIONS/cseq=102 (tdta0x14376840) to UDP 192.168.1.180:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.180:5060;rport=5060;received=192.168.1.180;branch=z9hG4bK5bcbb3b5
Call-ID: 1dd46060547355717c63c58d6b16e253@192.168.1.180
From: "Unknown" sip:Unknown@192.168.1.180;tag=as66533a24
To: sip:20001@192.168.1.78;ob;tag=z9hG4bK5bcbb3b5
CSeq: 102 OPTIONS
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Accept: application/sdp, application/pidf+xml, application/xpidf+xml, application/dialog-info+xml, application/simple-message-summary, message/sipfrag;version=2.0, application/im-iscomposing+xml, text/plain
Supported: replaces, 100rel, timer, siprec, norefersub, trickle-ice
Allow-Events: presence, dialog, message-summary, refer
Content-Length: 0
--end msg--

[massimo11979]

Hi,
after upgrading ha-sip from 5.3 to 5.4, outgoing calls started failing. The add-on crashes immediately when receiving a dial command. The same configuration worked fine on 5.3.

Environment

Add-on: ha-sip 5.4 (previously 5.3 OK)

Home Assistant OS: 17.0 (amd64 / qemux86-64)

Home Assistant Core: 2026.1.3

Home Assistant Supervisor: 2026.01.1

SIP server / gateway: Yeastar TG100 (Asterisk realm asterisk)

SIP registrar: sip:192.168.1.180

Account: sip:20001@192.168.1.180 (UDP/TCP enabled, TLS disabled)

Python shown in logs: 3.13.5

PJSUA: 2.16 (from logs)

ha-sip add-on config (relevant parts)
sip:
enabled: true
registrar_uri: sip:192.168.1.180
id_uri: sip:20001@192.168.1.180
realm: asterisk
user_name: "20001"
password: ********
answer_mode: listen
settle_time: 1

How to reproduce

Call via Home Assistant service hassio.addon_stdin:

addon: c7744bff_ha-sip
input:
command: dial
sip_account: 1
number: "sip:+phonenumber@192.168.1.180"
ring_timeout: 30
menu:
language: it-IT
message: "Test call from ha-sip"
wait_for_audio_to_finish: true
post_action: hangup
timeout: 30

Expected behavior

The add-on should initiate an outgoing SIP call (INVITE) and ring the destination.

Actual behavior

The add-on logs Got "dial" and then crashes with a PJSUA assert before any INVITE is sent.

Logs (relevant excerpt)
| 23:21:25.908980 [ ] Got "dial" command for sip:+phonenumber@192.168.1.180
23:21:25.909 ../src/pjsua-lib/pjsua Assert failed: call_id>=0 && call_id<(int)pjsua_var.ua_cfg.max_calls
23:21:25.909 call.cpp pjsua_call_get_info(id, &pj_ci) error: Invalid value or argument (PJ_EINVAL)
Traceback (most recent call last):
File "/ha-sip/main.py", line 168, in
main()
File "/ha-sip/main.py", line 155, in main
handle_command_list(command_client, command_handler)
File "/ha-sip/main.py", line 31, in handle_command_list
command_handler.handle_command(command, None)
File "/ha-sip/command_handler.py", line 86, in handle_command
call.make_call(...)
File "/ha-sip/call.py", line 722, in make_call
new_call = Call(... pj.PJSUA_INVALID_ID, ...)
File "/ha-sip/call.py", line 120, in init
self.callback_id, other_ids = self.get_callback_ids()
File "/ha-sip/call.py", line 509, in get_callback_ids
call_info = self.get_call_info()
File "/ha-sip/call.py", line 517, in get_call_info
ci = self.getInfo()
File "/root/.local/lib/python3.13/site-packages/pjsua2.py", line 11239, in getInfo
return _pjsua2.Call_getInfo(self)
pjsua2.Error

Notes

Registration is successful (OnRegState: 200 OK) and keep-alive OPTIONS work.

Only outgoing dial triggers the crash.

This started only after upgrading to 5.4; 5.3 worked with the same TG100 setup.

If you need more logs (full add-on log around the crash) I can provide them.

Thanks!

[arnonym]

Thanks for the report. I could identify the problem and will publish a fix soon. Sorry for any inconvenience!

[massimo11979]

Grazie per la segnalazione. Sono riuscito a identificare il problema e pubblicherò presto una soluzione. Ci scusiamo per il disagio!

You're welcome, it's a pleasure to collaborate!

[arnonym]

Fixed in 5.4.1.

[massimo11979]

I've already downloaded version 5.4.1, and it works fine. Thanks.