Bogdan,<br><br>You are right it is the destination. I added the following to udp_server.c when the error occurs:<br><br> LOG(L_ERR, "sa = %d, %s, %d\n", to->sin.sin_family,<br> inet_ntoa(to->
sin.sin_addr), ntohs(to->sin.sin_port));<br><br>Which logs:<br><br> sa = 2, <a href="http://0.0.1.244">0.0.1.244</a>, 5060<br><br>This address is clearly invalid. Interesting thing though is that I ran an ngrep to see if I could locate a message that contains this IP and could not find one:
<br><br>ngrep -p port 5060 | grep "<a href="http://0.0.1.244">0.0.1.244</a>"<br><br>The above came up clean even though the log kept reporting the error.<br><br>Any more ideas?<br><br>Martin<br><br><div><span class="gmail_quote">
On 2/5/07, <b class="gmail_sendername">Bogdan-Andrei Iancu</b> <<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Martin,<br><br>after all, it look the root problem is the destination address - the<br>detection of the egress socket (triggered by mhomed) also fails because<br>of an Invalid Argument (as originally).<br><br>my guess is that an invalid ip or port is used for sending the message.
<br>If you cannot track this down, I can try to prepare a patch to print the<br>destination address/port in case of error.<br><br>regards,<br>bogdan<br><br>Martin Burns wrote:<br><br>> Thanks for your reply Bogdan,<br>
><br>> There is definitely both UDP and TCP listening:<br>><br>> Starting openser: openserListening on<br>> udp: xx.xx.xx.xxx [xx.xx.xx.xxx]:5060<br>> tcp: xx.xx.xx.xxx [xx.xx.xx.xxx
]:5060<br>> Aliases:<br>> ......<br>><br>> Is it possible that there is simply too many messages for the server<br>> to handle?<br>><br>> At the moment the server is configured with:<br>><br>> children=20
<br>> tcp_children=2<br>><br>> and an ngrep suggests quite a few messages per second.<br>><br>> Thanks<br>><br>> Martin<br>><br>> On 2/5/07, *Bogdan-Andrei Iancu* <<a href="mailto:bogdan@voice-system.ro">
bogdan@voice-system.ro</a><br>> <mailto:<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>>> wrote:<br>><br>> Hi Martin,<br>><br>> the last error you posted says you want to forward something using UDP
<br>> (proto 1), but there is no listen socket for UDP.<br>> can you check is there is no UDP listen configured on your openser?<br>><br>> regards,<br>> bogdan<br>><br>> Martin Burns wrote:
<br>><br>> > We have over 4 proxies running openser-1.1.0-notls. Recently we<br>> > started to see the following error in the logs of one of the<br>> proxies:<br>> ><br>> > Feb 4 06:46:21 proxy01 /usr/local/sbin/openser[4670]: ERROR:
<br>> > udp_send: sendto(sock,0xb3c35898,594,0,0xb3c257f4,16): Invalid<br>> > argument(22)<br>> > Feb 4 06:46:21 proxy01 /usr/local/sbin/openser[4670]: CRITICAL:<br>> > invalid sendtoparameters one possible reason is the server is
<br>> bound to<br>> > localhost and attempts to send to the net<br>> > Feb 4 06:46:21 proxy01 /usr/local/sbin/openser[4670]: msg_send:<br>> > ERROR: udp_send failed<br>> > Feb 4 06:46:21 proxy01 /usr/local/sbin/openser[4670]:
<br>> > ERROR:tm:t_forward_nonack: sending request failed<br>> ><br>> > Now the errors suggests a binding to localhost, however our<br>> > openser.cfg has the following:<br>> >
<br>> > listen=eth0:5060<br>> ><br>> > After a brief search we came across a couple of over people<br>> having a<br>> > similar problem. Once of the suggested fixes was to add a mhomed=1
<br>> > line to the cfg.<br>> ><br>> > Well we tried this (even though we are not multi homed) and the<br>> error<br>> > changed to:<br>> ><br>> > Feb 5 02:54:09 proxy01 /usr/local/sbin/openser[2209]: ERROR:
<br>> > get_out_socket: connect failed: Invalid argument<br>> > Feb 5 02:54:09 proxy01 /usr/local/sbin/openser[2209]: ERROR:<br>> > get_out_socket: no socket found<br>> > Feb 5 02:54:09 proxy01 /usr/local/sbin/openser[2209]:
<br>> > ERROR:tm:add_uac: can't fwd to af 2, proto 1 (no corresponding<br>> > listening socket)<br>> > Feb 5 02:54:09 proxy01 /usr/local/sbin/openser[2209]:<br>> > ERROR:tm:t_forward_nonack: failure to add branches
<br>> ><br>> > Does anyone have any suggestions or ideas as to what is causing this<br>> > error.<br>> ><br>> > Thanks<br>> ><br>> > mburns<br>> >
<br>> >------------------------------------------------------------------------<br>><br>> ><br>> >_______________________________________________<br>> >Users mailing list<br>> >
<a href="mailto:Users@openser.org">Users@openser.org</a> <mailto:<a href="mailto:Users@openser.org">Users@openser.org</a>><br>> > <a href="http://openser.org/cgi-bin/mailman/listinfo/users">http://openser.org/cgi-bin/mailman/listinfo/users
</a><br>> ><br>> ><br>><br>><br><br></blockquote></div><br>