I think this is a Sofia thing, and it's a problem in Drachtio land, too. At least, that's what I've heard.
> On Dec 30, 2024, at 9:54 pm, Ben Kaufman <[email protected]> wrote: > > That could be what he's referencing. Regarding forking (parallel or serial), > Freeswitch has an issue with it. Going from memory (I could be mistaken) it > rejects subsequent requests having the same call-id with a 482, despite the > fact that the branch parameter of the Via: is different. Reported here: > > https://freeswitch-users.freeswitch.narkive.com/pl2VL6Gu/482-request-merged-in-serial-forking#post1 > > I know that thread is 15 years old, but I believe the behavior stands today. > If that's the cause of either of the issues Benoit having, I'd like to mock > it up and try reporting it to the freeswitch team again. > > > > Kaufman > Senior Voice Engineer > > > > E: [email protected] > > > > > SIP.US Client Support: 800.566.9810 | SIPTRUNK Client Support: > 800.250.6510 | Flowroute Client Support: 855.356.9768 > > From: Alex Balashov <[email protected]> > Sent: Monday, December 30, 2024 2:18 PM > To: Kamailio (SER) - Users Mailing List <[email protected]> > Cc: Ben Kaufman <[email protected]> > Subject: Re: [SR-Users] how to call loose_route() after adding route header > without using msg_apply_changes? > CAUTION: This email originated from outside the organization. Do not click > links or open attachments unless you recognize the sender and know the > content is safe. > > > If you read 3262, there is, in fact, a concept of an RSeq that is > 100rel-specific. > > -- Alex > > > On Dec 30, 2024, at 2:22 pm, Ben Kaufman via sr-users > > <[email protected]> wrote: > > > > Benoit, > > > > You posted "rseq", but do you mean "cseq"? Is the issue you reference > > Freeswitch returning a 482 reply to a serial forked request? > > > > > > Kaufman > > Senior Voice Engineer > > > > > > > > E: [email protected] > > > > > > > > > > SIP.US Client Support: 800.566.9810 | SIPTRUNK Client Support: > > 800.250.6510 | Flowroute Client Support: 855.356.9768 > > > > From: Benoît Panizzon via sr-users <[email protected]> > > Sent: Monday, December 30, 2024 10:14 AM > > To: Fred Posner via sr-users <[email protected]> > > Cc: Fred Posner <[email protected]>; Benoît Panizzon <[email protected]> > > Subject: [SR-Users] Re: how to call loose_route() after adding route header > > without using msg_apply_changes? > > CAUTION: This email originated from outside the organization. Do not click > > links or open attachments unless you recognize the sender and know the > > content is safe. > > > > > > Hi Fred > > > > > I would be remiss if I didn’t mention that FreeSWITCH is a very > > > decent b2bua; especially light-weight if you are already proxying > > > media on rtpengine and “bypass media” in freeswitch. > > > > > > Example: > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ffredposner%2Fcluecon2023&data=05%7C02%7Cbkaufman%40bcmone.com%7Cdfaf1ccb06cf4eba9a1108dd290f2b75%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638711867334200954%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YtJpr0Dp4F%2F%2FITBZpd18oav8yuHqGrhhR1oevShrj5A%3D&reserved=0 > > > > I used your example and we tried FreeSWITCH. Thank you for your > > suggestion. > > > > Unfortunately we ran into massive issues we were not able to solve. > > > > I don't exactly recall which one it was but it appeared in situations > > involving: > > > > * 100rel required > > * parallel branches > > > > It was either the issue that FreeSWITCH itself was dropping rseq > > replies with same rseq number but different totags wrongfully as > > duplicates. > > > > Or it was the issue with those replies with different totags on the 2nd > > leg being mapped to ONE totag on the first leg causing the original > > sender to consider them a duplicates and dropping them. > > > > -- > > Mit freundlichen Grüssen > > > > -Benoît Panizzon- @ HomeOffice und normal erreichbar > > -- > > I m p r o W a r e A G - Leiter Commerce Kunden > > ______________________________________________________ > > > > Zurlindenstrasse 29 Tel +41 61 826 93 00 > > CH-4133 Pratteln Fax +41 61 826 93 01 > > Schweiz Web > > https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.imp.ch%2F&data=05%7C02%7Cbkaufman%40bcmone.com%7Cdfaf1ccb06cf4eba9a1108dd290f2b75%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638711867334219503%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=7Oidk1W8I1JNqpqV1ulcn7CHGb1DYh7qmgCSvTvuvvg%3D&reserved=0 > > ______________________________________________________ > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions -- > > [email protected] > > To unsubscribe send an email to [email protected] > > Important: keep the mailing list in the recipients, do not reply only to > > the sender! > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions -- > > [email protected] > > To unsubscribe send an email to [email protected] > > Important: keep the mailing list in the recipients, do not reply only to > > the sender! > > > -- > Alex Balashov > Principal Consultant > Evariste Systems LLC > Web: > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fevaristesys.com%2F&data=05%7C02%7Cbkaufman%40bcmone.com%7Cdfaf1ccb06cf4eba9a1108dd290f2b75%7Cafc1818e7b6848568913201b9396c4fc%7C1%7C0%7C638711867334231824%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3gwjPZbuGz8%2FA4zPuJUaWZNDcjEzpXV%2BMKla0Pfmrtk%3D&reserved=0 > Tel: +1-706-510-6800 -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800 __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
