Hi,
There is not bug, it is most probably just you messing (in script) the
RURI to a format that is SIP invalid.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 12.07.2024 08:56, Saint Michael wrote:
(xlog) NOTICE:ru sip:[email protected];transport=UDP rU 19206661392
DST= 1.1.1.1 rd= 1.1.1.1
CRITICAL:core:mk_proxy: could not resolve hostname: ";transport=UDP"
ERROR:tm:uri2proxy: bad host name in URI <sip:;transport=UDP:5060>
ERROR:tm:t_forward_nonack: failure to add branches
ERROR:tm:w_t_relay: t_forward_nonack failed
My box is multihomed, and I am using rttpproxy.
this: socket=udp:*:5060 use_workers 80
or this: socket=udp:1.1.1.1:5060 use_workers 80
make no difference
also to use rttpproxy or not makes no difference
The issue seems to be caused by ru
sip:[email protected];transport=UDP having now the ;transport=UDP,
but I only use RTP, so the tansport= part is irrelevant
The main problem is that my CDR is useless
because if the call fails, the field dst_ip comes as ";transport=UDP"
when it should have been "1.1.1.1"
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
