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
When bypass_media_after_bridge option is used, call recovery fails because inbound call routes are in reverse order and FS is trying to send re-INVITE to wrong host (that it can't resolve which can be seen in debug logs).
I have dialplan which plays message to user and after that bridges call. When call is connected, FS removes itself from media path by using bypass_media_after_bridge.
After this i simulate FS crash and when calls are recovered, SIP re-invite is sent only to outbound call but not for inbound. When i investigated recovery data in database (MariaDB), I noticed that <sip_invite_route_uri> parameters are in reverse order for inbound call. I can see from debug logs that FS was failing when it tried to resolve that first route (and that is expected as that route should be last and it is not resolvable on host where FS is running).
This happens only when I am using this bypass_media_after_bridge functionality. If I don't use it, all routes are in correct order and everything works as expected when call recovery happens.
Freeswitch version that I'm using is 1.10.11.
I also wrote python script which is reversing <sip_invite_route_uri> addresses (to make them correct order) before crashing and executing sofia recover command and in that scenario everything seems to work correctly, so it looks like that something is causing those routes to reverse when SIP re-INVITEs to bypass media happens.
To reproduce:
Use dialplan with <bypass_media_after_bridge>, crash FS and recover calls.
When bypass_media_after_bridge option is used, call recovery fails because inbound call routes are in reverse order and FS is trying to send re-INVITE to wrong host (that it can't resolve which can be seen in debug logs).
I have dialplan which plays message to user and after that bridges call. When call is connected, FS removes itself from media path by using bypass_media_after_bridge.
After this i simulate FS crash and when calls are recovered, SIP re-invite is sent only to outbound call but not for inbound. When i investigated recovery data in database (MariaDB), I noticed that <sip_invite_route_uri> parameters are in reverse order for inbound call. I can see from debug logs that FS was failing when it tried to resolve that first route (and that is expected as that route should be last and it is not resolvable on host where FS is running).
This happens only when I am using this bypass_media_after_bridge functionality. If I don't use it, all routes are in correct order and everything works as expected when call recovery happens.
Freeswitch version that I'm using is 1.10.11.
I also wrote python script which is reversing <sip_invite_route_uri> addresses (to make them correct order) before crashing and executing sofia recover command and in that scenario everything seems to work correctly, so it looks like that something is causing those routes to reverse when SIP re-INVITEs to bypass media happens.
To reproduce:
Use dialplan with <bypass_media_after_bridge>, crash FS and recover calls.
Expected behavior:
Freeswitch should send SIP re-INVITEs correctly
The text was updated successfully, but these errors were encountered: