Hi, In a different scenario from yours, i encountered the same problem of loose_route() unexpectedly returning false. In my case, it was when i was running a softphone on the same computer as the ser proxy. If someone would send a routed message to the phone, for example a BYE, or a re-INVITE, SER would return false at the loose_route() function. This means that ser identifies the previous hop as doing strict routing. I was able to solve this by removing the ser-proxy IP address from the alias="...." list in ser.cfg, and then using the domain module to gain back the same functionality (or close) when doing the uri==myself. Don't know how your ser.cfg looks like, but just thought that maybe this might be useful. Regards, Cesc Hi Paul! That something I also asked several times and no answer yet. In my experience, loose_route() is true if the request URI contains the "lr" paramter (message comes from a strict router). Nevertheless, the loose_route function will remove its own Route: header. I solve the troubles by allowing t_relay for all messages with to-tag (in-dialog). regards, klaus Java Rockx wrote: Unclassified ALG <sip:3475626630@66.243.109.99:5060;user=phone>;tag=550070175. <sip:9195531888@64.152.60.6;user=phone>;tag=10000000-0-1811969809. _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers