THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#53 - wrong TM response code User who did this - Andrei Pelinescu-Onciul (andrei) ---------- Yes, it did, but on the lo interface (that's why it's not in the ngrep dump). First of all you can see that the INVITE forwarded back to 83.136.33.3:5200 it's on the second branch (branch number 1 and not 0): Via: SIP/2.0/UDP 83.136.32.159;branch=z9hG4bK404.f2951c02.1 (note the .1 at the end) Then looking at syslog.txt: Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: 3df971d27197-l2satt3hm9s8@83-136-33-3 appending branch to gateway ... ..... Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: main branch: Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: $ru=sip:00123456@labs.nic.at Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: $du=<null> .... Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: additional branch 0: Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: RURI=sip:klaus.darilion@83.136.33.3:5200;line=m3yhutkd Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30989]: INFO: <script>: DURI=sip:83.136.33.3:5200 Basically there are 2 branches and the main/first branch tries to send the invite to sip:00123456@labs.nic.at which will cause it to loop it back to the proxy (that's not probably what you want, either the uri is wrong, the dst uri is not set or you miss a forward gateway rule). The proxy receives the INVTIE for sip:00123456@labs.nic.at, and the auth. fails (the credentials are probably removed in the script before forwarding, but even if they would not be removed they would be for klaus.darilion and not for 00123456): Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30990]: INFO: <script>: 3df971d27197-l2satt3hm9s8@83-136-33-3 authentication failed, wrong or missing credentials, challenging... .... Mar 26 13:41:58 plaudertasche /usr/sbin/kamailio[30990]: DEBUG: sl [sl.c:318]: reply in stateless mode (sl) Then the proxy will reply with 407 for the INV to sip:00123456@labs.nic.at, on the lo interface (that's why it's not in the ngrep dump). In the end there are 2 responses for the INV transaction: the 407 and the 482 and the proxy chooses the 407. ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=53#comment54 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.