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
[OpenSIPS-Users] 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, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Erasing statistics groups from memory
Hello,
I am using statistics module to store CPS data on demand (via an external
variable shv_set), keys are current seconds ,example :
opensips-cli -x mi get_statistics cps:
{
"cps:2:20221202143557": 1,
"cps:2:20221202143613": 1,
"cps:2:20221202143616": 1
}
The data is stored on the server memory, and then reset via a time_route
everyday (reset_stat) which updates the counters to 0 but the keys persist on
my server.
Is there anyway to erase those keys from the memory "cps:2" Without
restarting my server ?
I know I can use an external Redis or MYSQL servers for such purpose , but I'm
trying as much as possible to keep everything inside opensips.
Thank you
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
