Hi Garry,
Proto 1 is actually PROTO_UDP - there is an internal proto enum
assigning those values.
If you are sure on your checks and if you have opensips installed from
sources, I can provide you a patch to print the source socket and
destination IP when the such a SEND fails.
Sometimes I notices similar error when the destination port is 0 (for
whatever obscure reasons).
So, just let me know if you have the means to apply and use the patch.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 07.08.2015 20:57, Garry M. Paxinos wrote:
Greetings,
Sorry, I sent a reply from my cellphone and it has a different email
address than my subscribed address.
Definitely understand the intent of the message. But I am certain
OSIPS is configured to listen on an external IP address and not
localhost -
listen=udp:199.193.188.70:5060 <http://199.193.188.70:5060>
I checked and there are no 'listens' on localhost (with either alias
or IP address) and mhomed is not set.
The server works fine under light load, but when call volume ramps up
the problem mentioned below starts happening. So I know it is
listening properly on the external IP address.
As Protocol '1' is ICMP, I'm wondering if there is any correlation to
the other discussions on this list regarding UDP versus SIP ping as well?
Thanks,
Pax.
On Fri, Aug 7, 2015 at 1:09 PM, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hello Gary,
Well, the message says it all: probably your OpenSIPS is listening
only on 127.0.0.1 (lo) but it is trying to send a ping to an
external IP address (some device registered with something else
than 127.0.0.1/8 <http://127.0.0.1/8> .
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 06.08.2015 20:27, Garry M. Paxinos wrote:
We are experimenting with OSIPS 2.1. The system seems to
operate normally when testing, but when we start to put it under
some load we start seeing the error messages below. We have
configured Linux similarly to how our production systems are
configuration when it comes to memory, number of sockets,...
Does anyone have any suggestions?
ERROR:nathelper:msg_send: send() for proto 1 failed
ERROR:nathelper:nh_timer: sip msg_send failed!
ERROR:core:proto_udp_send:
sendto(sock,0x7f51383271d0,4,0,0x7ffe0596d3d0,16): Invalid
argument(22)
CRITICAL:core:proto_udp_send: invalid sendtoparameters#012one
possible reason is the server is bound to localhost
and#012attempts to send to the net
--
*Garry M. Paxinos*
CTO
*netTALK*.COM, INC. | *1080* NW 163rd Drive, Miami, FL 33169
(E)[email protected] <mailto:[email protected]> | (O) 305.621.1200,
x210 | (C) 954.655.7453
*ΓΝΩΘΙ ΣΑΥΤΟΝ*
"The real voyage of discovery consists not in seeking new
landscapes but in having new eyes." -Proust
"Wherever you go, go with all of your heart" -
Confucius
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
*Garry M. Paxinos*
CTO
*netTALK*.COM, INC. | *1080* NW 163rd Drive, Miami, FL 33169
(E)[email protected] <mailto:[email protected]> | (O) 305.621.1200, x210 |
(C) 954.655.7453
*ΓΝΩΘΙ ΣΑΥΤΟΝ*
"The real voyage of discovery consists not in seeking new landscapes
but in having new eyes." -Proust
"Wherever you go, go with all of your heart" -
Confucius
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
