Open devoxy1 opened 1 year ago
This issue might be related to this one 3116, may be the same issue on both
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Up
This is still actual. Without no-late-sdp flag and even without re-invite SDP still not updated on final ACK of referred call. A -INVITE--> Opensips -INVITE--> B (both legs SDP is updated correctly with rtpengine IP) REFER to C A -INVITE--> Opensips -INVITE--> C (First INVITE no SDP, ACK - SDP is not updated)
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
up
@devoxy1 can you please check the latest sources, which should include the fix in 1339b7acb4537b4b916d4f804cc4c1c55a61c24d and let us know if this still happens?
Hello @razvancrainea! I recompiled opensips with latest master branch but when i do my scenario with REFER i get segfault everytime on the moment new leg is created
Here is dump that is generated
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/opensips...
[New LWP 1394028]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/opensips -P /var/run/opensips/opensips.pid -f /etc/opensips/opensips.'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xffffff28958948ff in ?? ()
and logfile: https://file.io/yNj28F97lAib
@devoxy1 it looks like the core dump is not correct, as it does not contain any information. Can you please make sure you get a clean core dump, so we can investigate this crash?
Best regards, Răzvan
Hello @razvancrainea, It seems i'm unable to get correct core file, i did all by instruction: disable apport, indicate folder with -w, rename core pattern, but i still get the same core files of size 268M with the similar content. I did core dumps before they usually came out fine with lots of info but this one i cannot seem to get correct. Is there anything else i can try?
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
UP
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
UP
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
UP
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
up
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
Hello!
I'm testing scenario with b2b and REFER on opensips+rtpengine and notice an issue with incorrect SDP on re-invites. The scenario is A -INVITE--> Opensips -INVITE--> B A <-200OK-- Opensips <-200OK-- B ------ Opensips <-REFER-- B ------ Opensips --INVITE-> C ------ Opensips <-200OK-- C ------ Opensips --BYE-> B A <-re-INVITE-- Opensips --re-INVITE-> B
I engage rtp_relay module on b2b_init to use rtpengine. On initial INVITE everything works fine and SDP IP for media is changed to rtpengine on both INVITE and 200OK. However once REFER is complete opensips sends re-invite to A and C and in new INVITE incorrect IP is passed (of A and C respectively).
Piece of my code:
OpenSIPS version you are running
Describe the bug
To Reproduce Steps to reproduce the behavior: Example:
Expected behavior re-INVITE sends rtpengine IP in SDP
Relevant System Logs
OS/environment information
Additional context