You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the Linphone Desktop with Asterisk PBX to build a video chat lab
General information
Device: Asus VivoBook, Lenovo Yoga 14
OS: Ubuntu 22.04, Windows 11
Version of the App: Desktop 5.2.4 - Qt5.15.2 Core 5.3.41
Expected behaviour
Get a text conversation between two Linphone-Desktop endpoints through Asterisk-20 PBX.
To Reproduce
Use TCP and FQDN in SIP URI
Get at least 2 registered Linphones on Asterisk
Send text mesasge from Linphone Desktop to another Linphone Client App
Not use TLS and secure
Additional context
I have an PBX Asterisk-20 and Linphone endpoints. I use SRV-Record to bind my local domain freedom.kch to TCP 5061 port on Asterisk. When I send text message from 203 (Linphone Android) to 202 (Linphone Desktop Win/Linux) - that well done. But origination of text message from Desktop Linphone is corrupted because of unacceptible structure of MESSAGE SIP request. The request contans two sequences of headers in one same SIP message. It looks like two SIP messages were splited into one or it try to manage any type of feature which server don't handeled
And I don't have this issue between two Linphone-Android clients on same Asterisk config. Chat is proceeding perfect and SIP dialog proceeds without errors
Context
I use the Linphone Desktop with Asterisk PBX to build a video chat lab
General information
Expected behaviour
Get a text conversation between two Linphone-Desktop endpoints through Asterisk-20 PBX.
To Reproduce
Additional context
I have an PBX Asterisk-20 and Linphone endpoints. I use SRV-Record to bind my local domain freedom.kch to TCP 5061 port on Asterisk. When I send text message from 203 (Linphone Android) to 202 (Linphone Desktop Win/Linux) - that well done. But origination of text message from Desktop Linphone is corrupted because of unacceptible structure of MESSAGE SIP request. The request contans two sequences of headers in one same SIP message. It looks like two SIP messages were splited into one or it try to manage any type of feature which server don't handeled
SDK logs URL
https://www.linphone.org:444//tmp/665d8872d2b7e_ce3b0a4c725eddfd58bb.gz
The text was updated successfully, but these errors were encountered: