Can't reregister landline account after inactivity: 400 (InvalidTransportModeException)

[theblackhole]

Hello and happy new year!

After 1.5 year of inactivity, I decided to use signal-cli again. My account was created with a landline number (so registered with voice) and I upgraded from 0.11.11 to the latest 0.13.11.

It seems like I have to register again because when I do signal-cli listAccounts I first get [401] Authorization failed! (AccountCheckException) then after a second check I get User is not registered. (NotRegisteredException)

But when I try to register, I get a Failed to register: StatusCode: 400 (InvalidTransportModeException) error.
I tried with and without the --reregister flag and it does this with the 2 devices I was using signal-cli on (one was linked to the other but I don't remember which was the main one so I tried to reregister on both)

date && signal-cli --verbose -a +33********* register --reregister --captcha 'signalcaptcha://signal-hcaptcha******'
lun. 06 janv. 2025 16:17:00 CET
2025-01-06T16:17:01.164+0100 [main] DEBUG org.asamk.signal.App - Starting signal-cli 0.13.11
2025-01-06T16:17:01.475+0100 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_DATA_HOME not set, falling back to home dir
2025-01-06T16:17:01.735+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2025-01-06T16:17:01.876+0100 [main] INFO  com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.sqlite.jdbc4.JDBC4Connection@458342d3
2025-01-06T16:17:01.878+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2025-01-06T16:17:02.734+0100 [main] DEBUG o.a.s.m.util.NumberVerificationUtils - No registration session, creating new one.
2025-01-06T16:17:03.925+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
2025-01-06T16:17:03.929+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
Failed to register: StatusCode: 400 (InvalidTransportModeException)
org.whispersystems.signalservice.api.push.exceptions.InvalidTransportModeException: StatusCode: 400
	at org.whispersystems.signalservice.internal.push.PushServiceSocket$RegistrationCodeRequestResponseHandler.handle(PushServiceSocket.java:3303)
	at org.whispersystems.signalservice.internal.push.PushServiceSocket.makeServiceRequest(PushServiceSocket.java:2372)
	at org.whispersystems.signalservice.internal.push.PushServiceSocket.requestVerificationCode(PushServiceSocket.java:447)
	at org.whispersystems.signalservice.api.registration.RegistrationApi.requestSmsVerificationCode$lambda$3(RegistrationApi.kt:73)
	at org.whispersystems.signalservice.api.NetworkResult$Companion.fromFetch(NetworkResult.kt:44)
	at org.whispersystems.signalservice.api.registration.RegistrationApi.requestSmsVerificationCode(RegistrationApi.kt:72)
	at org.asamk.signal.manager.util.NumberVerificationUtils.requestVerificationCode(NumberVerificationUtils.java:96)
	at org.asamk.signal.manager.internal.RegistrationManagerImpl.register(RegistrationManagerImpl.java:140)
	at org.asamk.signal.commands.RegisterCommand.register(RegisterCommand.java:80)
	at org.asamk.signal.commands.RegisterCommand.handleCommand(RegisterCommand.java:51)
	at org.asamk.signal.commands.CommandHandler.handleRegistrationCommand(CommandHandler.java:33)
	at org.asamk.signal.App.handleRegistrationCommand(App.java:265)
	at org.asamk.signal.App.handleCommand(App.java:174)
	at org.asamk.signal.App.init(App.java:144)
	at org.asamk.signal.Main.main(Main.java:56)