Re: [sr-dev] [kamailio/kamailio] Branch ordering behavior changed between v5.3 and v5.4 (#2449)

Is it possible that the branches are handled differently when they're added by `append_branch()`? ``` append_branch("sip:1001@gateway1.carrierB.com;transport=tcp", "0.3"); append_branch("sip:1001@gateway2.carrierB.com;transport=tcp", "0.2"); append_branch("sip:1001@gateway3.carrierB.com;transport=tcp", "0.7"); append_branch("sip:1001@gateway4.carrierB.com;transport=tcp", "0.5"); append_branch("sip:1001@gateway5.carrierB.com;transport=tcp", "0.6"); xlog ("=== $(branch(uri)[0]), $(branch(q)[0])\n"); xlog ("=== $(branch(uri)[1]), $(branch(q)[1])\n"); xlog ("=== $(branch(uri)[2]), $(branch(q)[2])\n"); xlog ("=== $(branch(uri)[3]), $(branch(q)[3])\n"); xlog ("=== $(branch(uri)[4]), $(branch(q)[4])\n"); t_load_contacts(); while (t_next_contacts()) { xlog ("==== $ru\n"); } ``` Output: ``` ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: === sip:1001@gateway1.carrierB.com;transport=tcp, 300 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: === sip:1001@gateway2.carrierB.com;transport=tcp, 200 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: === sip:1001@gateway3.carrierB.com;transport=tcp, 700 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: === sip:1001@gateway4.carrierB.com;transport=tcp, 500 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: === sip:1001@gateway5.carrierB.com;transport=tcp, 600 DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: tm [t_serial.c:526]: t_load_contacts(): load_contact mode not selected, using: 0 DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: tm [t_serial.c:340]: ki_t_load_contacts_mode(): nr_branches is 5 DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: <core> [core/xavp.c:539]: xavp_destroy_list(): destroying xavp list 0x7fe88ec9e248 DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: tm [t_serial.c:890]: ki_t_next_contacts(): Appending branch uri-'sip:1001@gateway3.carrierB.com;transport=tcp' dst-'' path-'' inst-'' ruid-'' location_ua-'' DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: <core> [core/xavp.c:539]: xavp_destroy_list(): destroying xavp list 0x7fe88ec9df90 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: ==== sip:1001@carrierB DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: <core> [core/xavp.c:539]: xavp_destroy_list(): destroying xavp list 0x7fe88ec9dcb8 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: ==== sip:1001@gateway5.carrierB.com;transport=tcp DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: <core> [core/xavp.c:539]: xavp_destroy_list(): destroying xavp list 0x7fe88ec9d9e0 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: ==== sip:1001@gateway4.carrierB.com;transport=tcp DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: <core> [core/xavp.c:539]: xavp_destroy_list(): destroying xavp list 0x7fe88ec9d708 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: ==== sip:1001@gateway1.carrierB.com;transport=tcp DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: <core> [core/xavp.c:539]: xavp_destroy_list(): destroying xavp list 0x7fe88ec9d430 ERROR: sipp-ci1-20200826182056-1-23(a)172.18.1.21: ==== sip:1001@gateway2.carrierB.com;transport=tcp DEBUG: sipp-ci1-20200826182056-1-23(a)172.18.1.21: tm [t_serial.c:627]: ki_t_next_contacts(): no contacts in contacts_avp - we are done! ``` -- 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/2449#issuecomment-681047174