Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
route[REGFWD] {
xlog("L_INFO", "-----------");
$uac_req(method) = "REGISTER";
$uac_req(ruri) = "sip:" + $avp(domain) + ":" + 'PBX_UDP_PORT';
$uac_req(furi) = "sip:" + $avp(extension) + "@" + $avp(domain);
$uac_req(turi) = "sip:" + $avp(extension) + "@" + $avp(domain);
$uac_req(auser) = $avp(extension);
$uac_req(apasswd) = $avp(secret);
$uac_req(evroute)=1;
$uac_req(hdrs) = "Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER\r\n";
$uac_req(hdrs) = $uac_req(hdrs) + "Contact: <sip:" + $avp(extension) + "@LOCALVIRTUALIP:MY_INTERNAL_UDP_PORT>\r\n";
$uac_req(hdrs) = $uac_req(hdrs) + "Expires: REGISTER_EXPIRATION\r\n";
$uac_req(sock) = "udp:LOCALVIRTUALIP:MY_INTERNAL_UDP_PORT";
xlog("L_INFO", "Forwarding SIP REGISTER to PBX for user $uac_req(furi)");
uac_req_send();
}
event_route[uac:reply] {
xlog("L_NOTICE", "[UAC] - $uac_req(method) request from user $uac_req(auser) to $uac_req(ruri) completed with code: $uac_req(evcode)\n");
}
I have also same error
Mar 11 20:57:00 stage-webrtc-kama-01 /usr/sbin/kamailio[162557]: NOTICE: [35ba98b51f649a01-162583@10.160.201.190 REGISTER uac:reply:2:1248] <script>: [UAC] - REGISTER request from user 1001 to sip:10.156.0.6:5060 completed with code: 401
Mar 11 20:57:00 stage-webrtc-kama-01 /usr/sbin/kamailio[162557]: NOTICE: [35ba98b51f649a01-162583@10.160.201.190 REGISTER uac:reply:2:1248] <script>: [UAC] - REGISTER request from user 1001 to sip:10.156.0.6:5060 completed with code: 200
Mar 11 20:57:05 stage-webrtc-kama-01 /usr/sbin/kamailio[162560]: CRITICAL: [123 OPTIONS :1:0] [core/mem/q_malloc.c:535]: qm_free(): BUG: freeing already freed pointer (0x7fc8acac2e58), called from uac: uac_send.c: uac_send_tm_callback(804), first free uac: uac_send.c: uac_resend_tm_callback(686) - ignoring
I execute that route with Timers.
As a workaround, is there any other possibility to handle 403 reply?
I tried to use t_on_failure, but failure route is not executing.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.