Jigasi connection to SIP-Provider Deutsche Telekom (t-online.de)

Hi Folks,

anybody out there who has already successfully established a connection between Jigasi and the SIP-Provider Deutsche Telekom, who uses the SIP Server “tel.t-online.de”?

I successfully established a connection to sipgate.de, however, with Deutsche Telekom it fails either with a timeout or if I try to define a SIP-Proxy it is complaining about a missing REALM. I have successfully registered other phone numbers from Deutsche Telekom at the same line.

Strange thing (without a SIP-Proxy) I get log messages only for “t-online.de”, is there possibly an issue when the provider uses a subdomain (in this case “tel.t-online.de”)?

I don’t want to install an IVR, it is okay, that I have Jigasi support only in one conference room.

Any ideas welcome.

Here are the logs:

(1) without a proxy configuration:

INFORMATION: [42] org.jitsi.jigasi.SipGateway.registrationStateChanged().120 REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:+49234534567@tel.t-online.de) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=-1; reason=A timeout occurred while trying to connect to the server.]

And some lines before:
2020-05-09 10:54:43.125 INFORMATION: [46] impl.dns.ParallelResolverImpl.send().232 Primary DNS seems laggy: no response for _sips._TCP.t-online.de./SRV after 1500ms. Enabling redundant mode.
2020-05-09 10:54:43.126 INFORMATION: [52] impl.dns.ParallelResolverImpl.run().573 Sending query for _sips._TCP.t-online.de./SRV to backup resolvers
2020-05-09 10:54:43.149 INFORMATION: [54] impl.dns.ParallelResolverImpl.run().573 Sending query for _sips._TCP.t-online.de.spdns.de./SRV to backup resolvers
2020-05-09 10:54:43.169 INFORMATION: [52] impl.dns.ParallelResolverImpl.run().573 Sending query for _sip._TCP.t-online.de./SRV to backup resolvers
2020-05-09 10:54:43.191 INFORMATION: [54] impl.dns.ParallelResolverImpl.run().573 Sending query for _sip._TCP.t-online.de.spdns.de./SRV to backup resolvers
2020-05-09 10:54:43.212 INFORMATION: [46] impl.dns.ParallelResolverImpl.send().232 Primary DNS seems laggy: no response for _sip._UDP.t-online.de./SRV after 1500ms. Enabling redundant mode.
2020-05-09 10:54:43.213 INFORMATION: [54] impl.dns.ParallelResolverImpl.run().573 Sending query for _sip._UDP.t-online.de./SRV to backup resolvers
2020-05-09 10:54:43.234 INFORMATION: [52] impl.dns.ParallelResolverImpl.run().573 Sending query for _sip._UDP.t-online.de.spdns.de./SRV to backup resolvers
2020-05-09 10:54:43.252 INFORMATION: [54] impl.dns.ParallelResolverImpl.run().573 Sending query for t-online.de./A to backup resolvers
2020-05-09 10:54:43.265 INFORMATION: [55] impl.dns.ParallelResolverImpl.run().573 Sending query for t-online.de./AAAA to backup resolvers

(2) with proxy configuration:
INFORMATION: [54] org.jitsi.jigasi.SipGateway.registrationStateChanged().120 REG STATE CHANGE ProtocolProviderServiceSipImpl(SIP:+49234523456@tel.t-online.de) -> RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; userRequest=false; reasonCode=1; reason=No realms present, cannot authenticate]

I found a suitable solution for me, nevertheless it should also be functioning by directly registering the phone number.

I let jigasi connect to my internal SIP-Server of my Router (FritzBox) and then let the Router redirect the incoming calls to the connected jigasi Client.

Perhaps someone saves this solution a lot of time in doing researches for this case.