Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: MESSAGE Unhandled transaction terminated (Strange behavior with SIP method MESSAGE) #844

Open
k-levin opened this issue Jun 3, 2024 · 2 comments
Labels

Comments

@k-levin
Copy link

k-levin commented Jun 3, 2024

Context

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

  1. Use TCP and FQDN in SIP URI
  2. Get at least 2 registered Linphones on Asterisk
  3. Send text mesasge from Linphone Desktop to another Linphone Client App
  4. 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

SDK logs URL

https://www.linphone.org:444//tmp/665d8872d2b7e_ce3b0a4c725eddfd58bb.gz

@k-levin k-levin added the bug label Jun 3, 2024
@k-levin k-levin changed the title [Bug]: MESSAGE Unhandled transaction terminated (Strange behavior with SIP Dialog. Doubling headers) [Bug]: MESSAGE Unhandled transaction terminated (Strange behavior with SIP method MESSAGE) Jun 3, 2024
@k-levin
Copy link
Author

k-levin commented Jun 3, 2024

So, It looks like messaging is acting with IMDN but I expected clear SIP messaging. Is it possible to clearify that behaviour? Thanks a lot!

@k-levin
Copy link
Author

k-levin commented Jun 3, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant