Re: [OpenSIPS-Users] reinvite and dialog uniqueness.
Johan, In regards to the first question I think the Invite and the Re-Invite have only two differences. The Invite doesn’t has a tag in the To-field, where the Re-Invite contains To:…;tag=2 In addition the Via-header contains a new branch-id because it’s a new transaction. For the second question, I have no experience with OpenSIPS. Best regards, John From: johan Sent: vrijdag 2 december 2022 17:23 To: OpenSIPS users mailling list Subject: reinvite and dialog uniqueness. 1. dialog uniqueness Alice calls Bob ->INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston <- 200 call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 -> ACK call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 Bob does a session refresh <- INVITE question in on the from tag and the to tag. should it be <- INVITE callid: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 or <- INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 or are both the same dialog (call-id + the 2 tags) ? 2. reinvite Secondly, when opensips is used as b2bua scenario as below A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. Is there a way that I can let respond opensips 200 OK on the reinvite without forwarding the request to A ? so I want A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. ->200 instead of A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. <- reinvite -> 200->200 wkr, Confidential - Limited *** Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes eventuelles peuvent contenir des informations confidentielles et/ou protegees par des droits de propriete intellectuelle. Ce message est adresse exclusivement e son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complete sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez recu ce message par erreur, veuillez prevenir l expediteur du message et en detruire le contenu. *** ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] reinvite and dialog uniqueness.
You can try to use topology_hiding and t_reply_with_body(): https://opensips.org/docs/modules/3.3.x/topology_hiding.html https://opensips.org/docs/modules/3.3.x/tm.html#func_t_reply_with_body Never tried it so I don't know if this will work. The question is if the CSeq number will be updated for the leg receiving the reINVITE. -ovidiu On Fri, Dec 2, 2022 at 12:36 PM johan wrote: > > It would be even better to have somehting without b2b. > > On 2/12/2022 17:51, Ovidiu Sas wrote: > > From has the user that initiated the request. > > For a reINVITE, if the reINVITE is issued by bob, then From has bob URIs. > > Take a look at the examples provided in the Session Initiation > > Protocol (SIP) Basic Call Flow Examples RFC: > > https://datatracker.ietf.org/doc/html/rfc3665 > > > > As for the b2b question, take a look at b2b_sed_reply function: > > https://opensips.org/docs/modules/3.3.x/b2b_logic.html#func_b2b_send_reply > > If you need to reply with 200ok to a reINVITE, you need to make sure > > that the SDP in the reINVITE is the same as the initial SDP and send > > back the other party's SDP in 200ok. > > > > -ovidiu > > > > On Fri, Dec 2, 2022 at 11:45 AM johan wrote: > >> I realise that I made an error in my drawing. > >> > >> 1. dialog uniqueness > >> > >> Alice calls Bob > >> > >> ->INVITE > >> > >> call-id: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston > >> > >> <- 200 > >> > >> call-id: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston;tag=2 > >> > >> -> ACK > >> > >> call-id: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston;tag=2 > >> > >> Bob does a session refresh > >> > >> <- INVITE > >> > >> question in on the from tag and the to tag. > >> > >> should it be > >> > >> <- INVITE > >> > >> callid: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston;tag=2 > >> > >> or > >> > >> <- INVITE > >> > >> call-id: 1 > >> > >> to: alice@atlanta;tag=1 > >> > >> from: bob@boston;tag=2 > >> > >> or > >> > >> are both the same dialog (call-id + the 2 tags) ? > >> > >> > >> On 2/12/2022 17:34, Ovidiu Sas wrote: > >> > >> The tag belongs to the SIP endpoint and does not change. > >> Take a look here at an example: > >> https://datatracker.ietf.org/doc/html/rfc3665#section-3.7 > >> > >> Regards, > >> Ovidiu Sas > >> > >> On Fri, Dec 2, 2022 at 11:23 AM johan wrote: > >> > >> 1. dialog uniqueness > >> > >> Alice calls Bob > >> > >> ->INVITE > >> > >> call-id: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston > >> > >> <- 200 > >> > >> call-id: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston;tag=2 > >> > >> -> ACK > >> > >> call-id: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston;tag=2 > >> > >> Bob does a session refresh > >> > >> <- INVITE > >> > >> question in on the from tag and the to tag. > >> > >> should it be > >> > >> <- INVITE > >> > >> callid: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston;tag=2 > >> > >> or > >> > >> <- INVITE > >> > >> call-id: 1 > >> > >> from: alice@atlanta;tag=1 > >> > >> to: bob@boston;tag=2 > >> > >> or > >> > >> are both the same dialog (call-id + the 2 tags) ? > >> > >> > >> 2. reinvite > >> > >> Secondly, > >> > >> when opensips is used as b2bua scenario as below > >> > >> > >> A opensips B > >> > >> -> invite ->invite > >> > >> <-200<- 200 > >> > >> -> ack->ack > >> > >> ... > >> > >> <-reinvite for keeeping > >> session alive. > >> > >> Is there a way that I can let respond opensips 200 OK on the reinvite > >> without forwarding the request to A ? > >> > >> so I want > >> > >> A opensips B > >> > >> -> invite ->invite > >> > >> <-200<- 200 > >> > >> -> ack->ack > >> > >> ... > >> > >> <-reinvite for keeeping > >> session alive. > >> > >> ->200 > >> >
Re: [OpenSIPS-Users] reinvite and dialog uniqueness.
It would be even better to have somehting without b2b. On 2/12/2022 17:51, Ovidiu Sas wrote: From has the user that initiated the request. For a reINVITE, if the reINVITE is issued by bob, then From has bob URIs. Take a look at the examples provided in the Session Initiation Protocol (SIP) Basic Call Flow Examples RFC: https://datatracker.ietf.org/doc/html/rfc3665 As for the b2b question, take a look at b2b_sed_reply function: https://opensips.org/docs/modules/3.3.x/b2b_logic.html#func_b2b_send_reply If you need to reply with 200ok to a reINVITE, you need to make sure that the SDP in the reINVITE is the same as the initial SDP and send back the other party's SDP in 200ok. -ovidiu On Fri, Dec 2, 2022 at 11:45 AM johan wrote: I realise that I made an error in my drawing. 1. dialog uniqueness Alice calls Bob ->INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston <- 200 call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 -> ACK call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 Bob does a session refresh <- INVITE question in on the from tag and the to tag. should it be <- INVITE callid: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 or <- INVITE call-id: 1 to: alice@atlanta;tag=1 from: bob@boston;tag=2 or are both the same dialog (call-id + the 2 tags) ? On 2/12/2022 17:34, Ovidiu Sas wrote: The tag belongs to the SIP endpoint and does not change. Take a look here at an example: https://datatracker.ietf.org/doc/html/rfc3665#section-3.7 Regards, Ovidiu Sas On Fri, Dec 2, 2022 at 11:23 AM johan wrote: 1. dialog uniqueness Alice calls Bob ->INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston <- 200 call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 -> ACK call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 Bob does a session refresh <- INVITE question in on the from tag and the to tag. should it be <- INVITE callid: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 or <- INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 or are both the same dialog (call-id + the 2 tags) ? 2. reinvite Secondly, when opensips is used as b2bua scenario as below A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. Is there a way that I can let respond opensips 200 OK on the reinvite without forwarding the request to A ? so I want A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. ->200 instead of A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. <- reinvite -> 200->200 wkr, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] reinvite and dialog uniqueness.
From has the user that initiated the request. For a reINVITE, if the reINVITE is issued by bob, then From has bob URIs. Take a look at the examples provided in the Session Initiation Protocol (SIP) Basic Call Flow Examples RFC: https://datatracker.ietf.org/doc/html/rfc3665 As for the b2b question, take a look at b2b_sed_reply function: https://opensips.org/docs/modules/3.3.x/b2b_logic.html#func_b2b_send_reply If you need to reply with 200ok to a reINVITE, you need to make sure that the SDP in the reINVITE is the same as the initial SDP and send back the other party's SDP in 200ok. -ovidiu On Fri, Dec 2, 2022 at 11:45 AM johan wrote: > > I realise that I made an error in my drawing. > > 1. dialog uniqueness > > Alice calls Bob > > ->INVITE > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston > > <- 200 > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > -> ACK > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > Bob does a session refresh > > <- INVITE > > question in on the from tag and the to tag. > > should it be > > <- INVITE > > callid: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > or > > <- INVITE > > call-id: 1 > > to: alice@atlanta;tag=1 > > from: bob@boston;tag=2 > > or > > are both the same dialog (call-id + the 2 tags) ? > > > On 2/12/2022 17:34, Ovidiu Sas wrote: > > The tag belongs to the SIP endpoint and does not change. > Take a look here at an example: > https://datatracker.ietf.org/doc/html/rfc3665#section-3.7 > > Regards, > Ovidiu Sas > > On Fri, Dec 2, 2022 at 11:23 AM johan wrote: > > 1. dialog uniqueness > > Alice calls Bob > > ->INVITE > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston > > <- 200 > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > -> ACK > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > Bob does a session refresh > > <- INVITE > > question in on the from tag and the to tag. > > should it be > > <- INVITE > > callid: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > or > > <- INVITE > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > or > > are both the same dialog (call-id + the 2 tags) ? > > > 2. reinvite > > Secondly, > > when opensips is used as b2bua scenario as below > > > A opensips B > > -> invite ->invite > > <-200<- 200 > > -> ack->ack > > ... > ><-reinvite for keeeping session > alive. > > Is there a way that I can let respond opensips 200 OK on the reinvite without > forwarding the request to A ? > > so I want > > A opensips B > > -> invite ->invite > > <-200<- 200 > > -> ack->ack > > ... > ><-reinvite for keeeping session > alive. > >->200 > > > instead of > > A opensips B > > -> invite ->invite > > <-200<- 200 > > -> ack->ack > > ... > ><-reinvite for keeeping session > alive. > > <- reinvite > > -> 200->200 > > > wkr, > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- VoIP Embedded, Inc. http://www.voipembedded.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] reinvite and dialog uniqueness.
I realise that I made an error in my drawing. 1. dialog uniqueness Alice calls Bob ->INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston <- 200 call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 -> ACK call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 Bob does a session refresh <- INVITE question in on the from tag and the to tag. should it be <- INVITE callid: 1 *from: alice@atlanta;tag=1 to: bob@boston;tag=2* or <- INVITE call-id: 1 *to**: alice@atlanta;tag=1 from: bob@boston;tag=2* or are both the same dialog (call-id + the 2 tags) ? On 2/12/2022 17:34, Ovidiu Sas wrote: The tag belongs to the SIP endpoint and does not change. Take a look here at an example: https://datatracker.ietf.org/doc/html/rfc3665#section-3.7 Regards, Ovidiu Sas On Fri, Dec 2, 2022 at 11:23 AM johan wrote: 1. dialog uniqueness Alice calls Bob ->INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston <- 200 call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 -> ACK call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 Bob does a session refresh <- INVITE question in on the from tag and the to tag. should it be <- INVITE callid: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 or <- INVITE call-id: 1 from: alice@atlanta;tag=1 to: bob@boston;tag=2 or are both the same dialog (call-id + the 2 tags) ? 2. reinvite Secondly, when opensips is used as b2bua scenario as below A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. Is there a way that I can let respond opensips 200 OK on the reinvite without forwarding the request to A ? so I want A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. ->200 instead of A opensips B -> invite ->invite <-200<- 200 -> ack->ack ... <-reinvite for keeeping session alive. <- reinvite -> 200->200 wkr, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] reinvite and dialog uniqueness.
The tag belongs to the SIP endpoint and does not change. Take a look here at an example: https://datatracker.ietf.org/doc/html/rfc3665#section-3.7 Regards, Ovidiu Sas On Fri, Dec 2, 2022 at 11:23 AM johan wrote: > > 1. dialog uniqueness > > Alice calls Bob > > ->INVITE > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston > > <- 200 > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > -> ACK > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > Bob does a session refresh > > <- INVITE > > question in on the from tag and the to tag. > > should it be > > <- INVITE > > callid: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > or > > <- INVITE > > call-id: 1 > > from: alice@atlanta;tag=1 > > to: bob@boston;tag=2 > > or > > are both the same dialog (call-id + the 2 tags) ? > > > 2. reinvite > > Secondly, > > when opensips is used as b2bua scenario as below > > > A opensips B > > -> invite ->invite > > <-200<- 200 > > -> ack->ack > > ... > ><-reinvite for keeeping session > alive. > > Is there a way that I can let respond opensips 200 OK on the reinvite without > forwarding the request to A ? > > so I want > > A opensips B > > -> invite ->invite > > <-200<- 200 > > -> ack->ack > > ... > ><-reinvite for keeeping session > alive. > >->200 > > > instead of > > A opensips B > > -> invite ->invite > > <-200<- 200 > > -> ack->ack > > ... > ><-reinvite for keeeping session > alive. > > <- reinvite > > -> 200->200 > > > wkr, > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- VoIP Embedded, Inc. http://www.voipembedded.com ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
