[SR-Users] Record-route issue in Kamailio 3.0.3

[Morten Isaksen]

Hi,

I think I have found a issue with recourd-route in Kamailio 3.0.3.

My old setup was:

Microsoft OCS <--> (TCP) OpenSER (UDP) <---> (UDP) Mediant 2000 (ISDN).

That worked fine.

Now I have inserted a new server in this setup.

Microsoft OCS <--> (TCP) OpenSER (UDP) <---> (UDP) Kamailio (UDP) <-->
(UDP) Mediant 2000 (ISDN).

When OpenSer sends the message to Kamailio the recourd-routes look like this:

Record-Route: <sip:x.x.248.20;r2=on;lr;ftag=3d9e7d131b>
Record-Route: <sip:x.x.248.20;transport=tcp;r2=on;lr;ftag=3d9e7d131b>

But when the message comes back from Kamailio it is:
Record-Route: <sip:x.x.248.7;lr=on;ftag=3d9e7d131b;did=584.1a683a45>,<sip:x.x.248.20;r2=on;lr;ftag=3d9e7d131b>,<sip:x.x.248.20;transport=tcp;r2=on;lr;ftag=3d9e7d131b>

OpenSER forwards the message to the OCS with Record-route unchanged
and the OCS gets confused and does not reply.

I am not that strong in the SIP RFC's. Is it part of the SIP standard
to compact the record-route into one line?

Is it a bug in Kamailio or is it just a parameter that needs to be changed?

Any help will be much appreciated.

-- 
Morten Isaksen