Something is going wrong here:
On 24.09.2014 18:41, Igor Potjevlesch wrote:
DEBUG: rr [loose.c:90]: is_preloaded(): is_preloaded: No
That's correct. The ACK is not pre-loaded (with a route set).
Checking first local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==14 && [<IP_KAMAILIO_ASTERISK>] == [<IP_KAMAILIO_ASTERISK>] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060
Checking seconf local URI (either alias= or listen= statement)
DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 14==12 && [<IP_KAMAILIO_ASTERISK>] == [192.168.0.19] DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 4060 DEBUG: <core> [forward.c:448]: check_self(): check_self: host != me
Correctly detects that the RURI does not address Kamailio, but
DEBUG: rr [loose.c:674]: after_strict(): Next hop: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on' is loose router
This means, that check_self returned 1 (match) although it didn't matched. This means that the _check_self_func_list (forward.c) is populated and matches the RURI.
Thus, the RURI does not match one of the "standard" aliases (the ones learned by the listen=... statements) but some other module registered a callback which returns MATCH, and thus Kamailio thinks the previous hop is a strict router:
DEBUG: rr [loose.c:724]: after_strict(): The last route URI: 'sip:<IP_KAMAILIO_ASTERISK>;lr=on'
please post your complete alias=.... and listen=... config.
Further, I suspect that you register additional aliases via "domain" or "corex" module and these additional aliases match the RURI. So review your domain and corex configuration.
regards Klaus