b2b: inherit sending socket when create new dialog after negative ACK

[nikbyte]

This small fix allows to inherit sending socket when create new dialog using previous dialog data.

[github-actions]

Any updates here? No progress has been made in the last 30 days, marking as stale.

[nikbyte]

up

[github-actions]

Any updates here? No progress has been made in the last 30 days, marking as stale.

[nikbyte]

up

[github-actions]

Any updates here? No progress has been made in the last 30 days, marking as stale.

[nikbyte]

up

[bogdan-iancu]

@nikbyte , trying to understand what this is doing (as per your description) - the new dialog I assume is a new client created in the B2B session. But what's the "old" dialog? is the dialog being replaced by the new one (during a bridging) ?

[nikbyte]

Hi @bogdan-iancu . It was hard to remember because time passed, but I did.

If use b2b as a some balancer under which is another SIP server and if that 2nd SIP server makes few outgoing legs, like.

1. INVITE to 1st direction, 503
2. INVITE to 2nd direction, 500
3. INVITE to 3rd direction, call established

And all these few calls goes through b2b, then this flow is the same dialog for b2b, but #2 and #3 forgets outgoing socket if you set it for 1st call. The patch allows to keep outgoing socket for all legs.

[bogdan-iancu]

@nikbyte , if I understand correctly, you do multiple re-briges in B2B, and you want the following bridges / UACs to remember the socket that was use by the prev failing UAC ?