[sr-dev] [kamailio/kamailio] Problem Parsing Route Header (#2079)

[duarterocha91]

Hello Daniel,

Thank you for your answer.

In both scenarios there is Route headers. You sure you're looking at the
correct Options?

The OPTIONS request is based on the 200 Ok received by the callee, so it
has everything that Kamailio added. The capture is taken on the Kamailio.

I also have another scenario where i have 2 uris in one route, where
Kamailio routes correctly but uac_replace fails. But i wasn't able to
reproduce it for testing yet. Are you able to try two adresses in one route
with a uac_restore on auto mode to a different number?

Best regards


A sexta, 27/09/2019, 11:52, Daniel-Constantin Mierla <
notifications at github.com> escreveu:

> One of scenarios is with ACK and OPTIONS without any Route headers, so not
> with two headers.
>
> You also have to take the pcap on kamailio, to see what kamailio adds as
> record route headers and the sip traffic on both sides with caller and
> callee.
>
> With a quick check here, all is working fine with one Route header having
> two addresses. Verify your scenarios and if you get the sip traffic with
> proper headers and the issue is still there, reopen and add pcaps taken on
> kamailio with the sip traffic in both sides.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/kamailio/kamailio/issues/2079?email_source=notifications&email_token=AG2MUKK6LCQVYOU6K5L6FT3QLXQXLA5CNFSM4I3EVLJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7YQ4EY#issuecomment-535891475>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AG2MUKITSAB3FHVKOK263VLQLXQXLANCNFSM4I3EVLJQ>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/2079#issuecomment-535896409
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-dev/attachments/20190927/136c1250/attachment-0001.html>