[OpenSIPS-Devel] [ opensips-Bugs-2870694 ] b2bua UAC sends ACK to wrong URI

[SourceForge.net]

Bugs item #2870694, was opened at 2009-09-30 08:24
Message generated for change (Comment added) made by sokhapkin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2870694&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
>Resolution: None
Priority: 5
Private: No
Submitted By: Sergey Okhapkin (sokhapkin)
Assigned to: Nobody/Anonymous (nobody)
Summary: b2bua UAC sends ACK to wrong URI

Initial Comment:
Here are messages running on client side of b2bua

b2bua        upstream
INVITE AAA ->
<- 100 Trying
<- 183 Session progress
<- 200 OK
    Contact: BBB
ACK AAA ->

UAC should ACK URI received in Contact: header of 200 OK responce, but not the original RURI.


----------------------------------------------------------------------

>Comment By: Sergey Okhapkin (sokhapkin)
Date: 2009-10-08 13:20

Message:
Any resolution on the problem?

----------------------------------------------------------------------

Comment By: Sergey Okhapkin (sokhapkin)
Date: 2009-10-05 09:06

Message:
I do record route on upstream, upstream is running opensips also. I wan't
to use b2bua in the following scenario - b2bua instance works as a
registrar for clients and forwards INVITES to upstream opensips which does
LCR and billing:

        if(is_method("INVITE")) {
                if (! t_newtran()) {
                        sl_reply_error();
                        exit;
                };

                $rd="UPSTREAM_IP_ADDRESS";
                b2b_init_request("top hiding");
                exit;
        };


I'm open for suggestions what could be changed in my setup to pass ALL SIP
messages through LCR/billing instance of opensips.

----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-10-05 08:56

Message:
Hi Sergey,

If you do record route on the initial INVITE on the upstream proxy, you
will receive all the messages from the server side of the dialog on the
upstream proxy. Indeed the messages from the client side will not go
through the server, but do you need these also? Aren't the messages from
the server side enough for billing?

Regards,
Anca


----------------------------------------------------------------------

Comment By: Sergey Okhapkin (sokhapkin)
Date: 2009-10-05 08:37

Message:
Now both ACK and BYE are sent to IP address from "Contact" which is wrong.
Everything should be sent to upstream IP address only, the IP from RURI, or
billing on upstream will not work properly.

----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-10-05 06:47

Message:
Hi,

There was a problem in the last commit. Fixed now. Please test again.

Anca

----------------------------------------------------------------------

Comment By: Sergey Okhapkin (sokhapkin)
Date: 2009-10-02 12:57

Message:
Now we're back to the original problem - ACK RURI instead of ACK Contact.
But BYE is sent correct to RURI.

----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-10-02 11:40

Message:
Hi,

I have fixed this also, The route set was not correctly updated, Please
update and test.

Regards,
Anca

----------------------------------------------------------------------

Comment By: Sergey Okhapkin (sokhapkin)
Date: 2009-10-01 21:31

Message:
Now ACK is sent correct, but I discovered another problem - BYE is
forwarded to IP/port from Contact header received in 200 OK, upsream server
never gets BYE!

----------------------------------------------------------------------

Comment By: Anca Vamanu (anca_vamanu)
Date: 2009-10-01 11:55

Message:
Hi Sergey,

Thank you for the report. It has been fixed in the last commit. Please
update and test.

Regards,
Anca

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2870694&group_id=232389