Hello,

the problem here seems to be the update of To header. Are you changing the To URI as well? I don't see the parameter for it in the Route header.

From URI handling seems to be ok.

Cheers,
Daniel

On 2/21/13 11:12 PM, Ronald Voermans wrote:
Responding to myself: attached is an ngrep (made by homer/sipcature server). Some strange things are happening. When I do a ngrep on the Kamailio, I see the ACK gets mangled:

SIP UA -> Kamalio
ACK sip:08000403@10.254.254.20:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.10:56953;branch=z9hG4bK-d8754z-170b73a13fd7a39d-1---d8754z-.
Max-Forwards: 70.
Route: <sip:10.254.254.1;lr;ftag=868b7d56;nat=yes;vsf=czFwOkQpYzVueyNnLEMbCDY6fyo/ejIqLXoQM2IvdwpSA14CTmo8PmQ->.
Contact: <sip:r.voermans@192.168.1.10:56953;transport=UDP>.
To: <sip:08000403@10.254.254.1;transport=UDP>;tag=a94c095b773be1dd6e8d668a785a9c84dac9696f.
From: "testcallerid"<sip:r.voermans@10.254.254.1;transport=UDP>;tag=868b7d56.
Call-ID: YWYwY2M0MTcwM2VmMTUxMTdkMTUwNDFhM2E2NjI3MTg..
CSeq: 2 ACK.
Proxy-Authorization: Digest username="r.voermans",realm="10.254.254.1",nonce="USabJ1EmmfuYD+XnJVMqKQkK6/VmiXJ8",uri="sip:08000403@10.254.254.1;transport=UDP",response="25e0d8980c67d1785948a44de4e51b44",algorithm=MD5.
User-Agent: Zoiper Communicator 2.04.10164 rev.10204.
Content-Length: 0.
.


Kamailio -> SIP UA
U 2013/02/21 23:04:52.911391 10.254.254.1:5060 -> 10.254.254.20:5060
ACK sip:08000403@10.254.254.20:5060 SIP/2.0.
Record-Route: <sip:10.254.254.1;lr;ftag=868b7d56;nat=yes>.
Via: SIP/2.0/UDP 10.254.254.1;branch=z9hG4bKcydzigwkX.
Via: SIP/2.0/UDP 192.168.1.10:56953;rport=56953;branch=z9hG4bK-d8754z-170b73a13fd7a39d-1---d8754z-.
Max-Forwards: 69.
Contact: <sip:r.voermans@192.168.1.10:56953;transport=UDP>.
To: <sip:#x)1,+2']..qmu.vinu5l{3(yuv....O!y.DP>;tag=a94c095b773be1dd6e8d668a785a9c84dac9696f.
From: "testcallerid"<sip:anonymous@anonymous.invalid>;tag=868b7d56.
Call-ID: YWYwY2M0MTcwM2VmMTUxMTdkMTUwNDFhM2E2NjI3MTg..
CSeq: 2 ACK.
User-Agent: Zoiper Communicator 2.04.10164 rev.10204.
Content-Length: 0.
.

restore_mode modparam is set to 'auto', and I checked that the vsf in Route-headers are correct. Any clues?

Regards,
Ronald



Op 21 feb. 2013, om 16:49 heeft Ronald Voermans <r.voermans@global-datacenter.nl<mailto:r.voermans@global-datacenter.nl>> het volgende geschreven:


Hi,


this last weekend we went live from the old 3.0 version to the latest stable release of Kamailio (3,3,0). All went well, except for one issue. We make use of uac_replace_from in our config, in case a client needs CLIR: uac_replace_from("Anonymous","sip:anonymous@anonymous.invalid");

Since the upgrade we receive the following error:

uac [replace.c:521]: new URI shorter than old URI

Which causes the call to be disconnected after about 20/30 seconds. This, because the ACK is received by Kamailio, but cannot be 'linked' to the transaction i guess.

What is exactly causing this issue and, more importantly, is there any way to resolve this?

Thanks in advance,

Regards,
Ronald Voermans

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users



_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, April 16-17, 2013, Berlin
 - http://conference.kamailio.com -