[SR-Users] Issue with uac_replace

Henning Westerholt hw at skalatan.de
Sun Sep 1 12:37:10 CEST 2019


Hello David,

did I got your correctly that another Kamailio "downstream" also uses the uac module for rewriting?

In this case your guess might be correct, that the rr and uac modules are confused because of the two same headers in one Route header.

Two workarounds:

- set other header name in uac with rr_from_store_param and rr_to_store_param

- use the dialog module and use restore_mode dialog to get rid of the Route header

Cheers,

Henning


Am 30.08.19 um 21:19 schrieb David Costa:
Greetings,

I have a Kamailio proxy with uac_replace for To and From Headers. So far everything has worked correctly.

However, I now have a client who encodes my Calling Number too and I’m getting some issues in the restore mechanics. I have the restore setup as "auto" and it's info is stored in "vsf" and "vst" parameters of Record-Route.

On replies sent by my client I have the following Record-Route and From Header (Note : My Kamailio has two IPs which makes it insert two RR headers ):

Record-Route: <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2>
Record-Route: <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2>

From: "+351411110097" <sip:I2116446I_500 at xxx.xxx.xxx.xxx><mailto:sip:I2116446I_500 at xxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4

In this case the restore is done correctly


When the client sends me a BYE request I have the following Route Header and To Header

Route : <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2>,<sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2>
To : "+351411110097" <sip:I2116446I_500 at xxx.xxx.xxx.xxx><mailto:sip:I2116446I_500 at xxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4

In this scenario, the To after restore is :  To :"+351411110097" <sip:Q4525417L_<>Gxxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4, which throws an internal error on Kamailio about bad URI and also makes our MediaGateway reply with a "Bad Request".


Can this error be caused by the restore of the uac_replace mechanics? Both Record Route URIs are on different headers while the both Route URIs are on the same Route header. Can this be the reason?

If you need more information please let me know.

Best Regards
David Costa





_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users at lists.kamailio.org<mailto:sr-users at lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190901/7e89585b/attachment.html>


More information about the sr-users mailing list