Route headers not properly reversed from RR set when RR URIs comma-separated

[abalashov]

When using the -invite flow, a 200 OK is received by the sipexer UA with two RR hops:

Record-Route: <sip:GW_2:5060;lr=on;ftag=37ff691d-7bf2-446b-abaa-9c09fe12deb1;vsf=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AA-;dlgcor=ccf1.7e73;proxy_media=yes>
Record-Route: <sip:GW_1:5060;lr;ftag=37ff691d-7bf2-446b-abaa-9c09fe12deb1;dlgcor=ccf.8be1;fromcor=ejFwbUZxUmpUUFNBejFwbUZxU
UUFNBejFwbUZxUmpUUFM-;proxy_media=yes>

This is properly reversed in the order of the Route headers constructed in the e2e ACK / subsequent in-dialog messages:

Route: <sip:GW_1:5060;lr;ftag=37ff691d-7bf2-446b-abaa-9c09fe12deb1;dlgcor=ccf.8be1;fromcor=ejFwbUZxUmpUUFNBejFwbUZxUmp
FNBejFwbUZxUmpUUFM-;proxy_media=yes>
Route: <sip:GW_2:5060;lr=on;ftag=37ff691d-7bf2-446b-abaa-9c09fe12deb1;vsf=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
-;dlgcor=ccf1.7e73;proxy_media=yes>

However, if the RR set returned is compacted into a single value...

Record-Route: <sip:GW_2:5060;lr=on;ftag=37ff691d-7bf2-446b-abaa-9c09fe12deb1;vsf=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AA-;dlgcor=ccf1.7e73;proxy_media=yes>, <sip:GW_1:5060;lr;ftag=37ff691d-7bf2-446b-abaa-9c09fe12deb1;dlgcor=ccf.8be1;fromcor=ejFwbUZxUmpUUFNBejFwbUZxU
UUFNBejFwbUZxUmpUUFM-;proxy_media=yes>

Then this order is imitated, rather than reversed, in the subsequent Route construction.

[abalashov]

It was pointed out to me that the ABNF spec for record-route technically consists of a name-addr, which could have a comma in it. I choose not to address it in this PR at this time. 😀

[miconda]

Thanks, PR merged!