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

crush when Contact contain ";isfocus" #475

Closed
sergey-safarov opened this issue Feb 23, 2021 · 6 comments
Closed

crush when Contact contain ";isfocus" #475

sergey-safarov opened this issue Feb 23, 2021 · 6 comments

Comments

@sergey-safarov
Copy link

We use FreeSwitch as a conference server.
When FreeSwitch send "isfocus" in Contact header, then Linphone dies.

Example

Contact: <sip:3500@192.168.100.31:5060;transport=udp>;isfocus

isfocus usage defined rfc4579

If you have FreeSwitch server, then you can reproduce the issue using this dialplan

<include>
  <context name="default">
    <extension name="conference">
      <condition field="destination_number" expression="^3500$">
        <action application="answer" data="is_conference"/>
        <action application="conference" data="3500@video-mcu-stereo"/>
      </condition>
    </extension>
  </context>
</include>
@Viish
Copy link
Member

Viish commented Feb 23, 2021

Please attach SDK logs from the start of the app to the moment it crashes and the symbolized stacktrace of the crash (using gdb or another tool).
Also, what version of the SDK are you using?

@sergey-safarov
Copy link
Author

Sorry, I do not use SDK
I use latest appimage build.
Think I cannot get a stack trace for appimage build.
Should I collect linphone logs?

@Viish Viish transferred this issue from BelledonneCommunications/linphone-sdk Feb 24, 2021
@Viish
Copy link
Member

Viish commented Feb 24, 2021

@julonexus Can you handle it please?

@sergey-safarov
Copy link
Author

I can prepare SIPp script as a test case.

@julonexus
Copy link
Collaborator

Hi,
What is your version of appimage? Is it from releases or snapshots? Logs will be helpful thanks

@sergey-safarov
Copy link
Author

I cannot reproduce the issue now.
I will reopen the ticket when I catch the issue again.

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

No branches or pull requests

3 participants