[OpenSIPS-Users] reinvite and dialog uniqueness.
Ovidiu Sas
osas at voipembedded.com
Fri Dec 2 16:34:35 UTC 2022
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 <johan at democon.be> wrote:
>
> 1. dialog uniqueness
>
> Alice calls Bob
>
> ->INVITE
>
> call-id: 1
>
> from: alice at atlanta;tag=1
>
> to: bob at boston
>
> <- 200
>
> call-id: 1
>
> from: alice at atlanta;tag=1
>
> to: bob at boston;tag=2
>
> -> ACK
>
> call-id: 1
>
> from: alice at atlanta;tag=1
>
> to: bob at 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 at atlanta;tag=1
>
> to: bob at boston;tag=2
>
> or
>
> <- INVITE
>
> call-id: 1
>
> from: alice at atlanta;tag=1
>
> to: bob at 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 at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
VoIP Embedded, Inc.
http://www.voipembedded.com
More information about the Users
mailing list