[OpenSIPS-Users] In-Dialog requests with B2B topology hiding

[Jeryes .]

Bogdan,

Thanks for your help!

I would like to apologize for that, it was my mistake, my PBX was sending
both TO headers, and I couldn't identify that on call trace. I fixed the
problem and now it's working!

Thanks!

Regards,
Jeryes



2013/2/26 Bogdan-Andrei Iancu <bogdan at opensips.org>

> **
> Hi,
>
> All sequential requests of the b2b dialogs will not be visible in the
> script. The fact that you get the ACK in the script means opensips b2b
> failed to match the ACK with any of the b2b dialogs.
> And looking at the trace, this happens because of the bogus TO tag in the
> ACK request ; the bogus tag param is a result of the double TO hdr in the
> 200 OK from b2b to carrier :
>
>
> U 192.168.191.149:6060 -> 204.11.180.165:5080
> SIP/2.0 200 OK.
> v: SIP/2.0/UDP 204.11.180.165:5080
> ;branch=z9hG4bK-f011bf3ff42d89f43e0b098e2a96b328.
> f: "Anonymous" <sip:anonymous at mydomain.com>;tag=3570555794-337860.
> *t: <sip:15265414613 at ss.mydomain.com>;tag=B2B.470.299.*
> i: 15070951-3570555794-337826 at msw1.telengy.net.
> CSeq: 1 INVITE.
> Content-Type: application/sdp.
> *To: <sip:15265414613 at 192.168.194.130>;tag=user-agent-6009.*
> Contact: <sip:192.168.191.149:6060>.
> Server: OpenSIPS (1.8.2-notls (i386/linux)).
> Content-Length: 224.
>
>
> Once in short format "t", once in long forma "To" - this seems to be an
> issue in the b2b.
>
> First of all be sure you are using the latest 1.8 sources from SVN (or use
> the SVN daily generated tarball) - I want to be sure you have all the fixes
> in your sources.
>
> I tried to reproduce this scenario (pushing your INVITE into a b2b), but I
> failed to get the 2 "to" hdrs....
>
> So: (1) update, (2) see if problem still there, (3) update me please.
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
>
> On 02/23/2013 12:19 AM, Jeryes . wrote:
>
> Hi All,
>
>
> I am using Opensips 1.8.2 tls, with B2B UserAgent, running the default
> scenario "top riding".
> The idea of this implementation is just to pass the packages between the
> carrier and the PBX, hiding the topology.
> I'm facing a problem to process the ACK requests after 200 OK (answer),
> and I guess that all the in-dialog requests after first INVITE. The ACK
> requests are beeing forwarded
> by t_relay() method, but that is not keeping the previous dialog, nether
> hiding the topology.
> Should I execute b2b_init_request("top hiding") to ACK requests as I do to
> INVITE, or the top hiding scenario was supposed to generate the ACK
> automaticaly to 200 OK reply, as is described in the tutorial<http://www.opensips.org/Resources/B2buaTutorial#toc11>:
> "Once you ask b2b to handle a call, you *won't see the future in-dialog
> request in the normal route*."?
>
> Do someone has an example about how it is supposed to be the processing of
> the in-dialog requests with b2b top hiding? Am I doing something wrong in
> the script that follows?
>
> Thanks in advance!
>
> Here follows the opensips.cfg:
>
> [....]
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130228/9862f464/attachment.htm>