Hi.
I built & installed ser-2.0.0-rc1 on a debian stable amd64. When I try to redirect a call (case where destination user redirects before answering), it gets an SIP error 477. Corresponding error from SER process running in foreground:
0(30330) ERROR: udp_send: sendto(sock,0x2aebd16fc038,1227,0,xx.xx.xx.xx:xxxx,16): Operation not permitted(1) 0(30330) msg_send: ERROR: udp_send failed 0(30330) ERROR: t_send_branch: sending request on branch 0 failed 0(30330) ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL)
Unfortunately, "1" (EPERM) is not documented in sento manpage, as far as I can see, so it's quite hard to track down that problem.
Kernel version is: 2.6.24.5-grsec iptables is used, but putting netcat in place of SER and the client shows that kernel allows packets to reach client (and more simply, it is possible to do a direct call, it's just redirects which fail).
It can be a grsec problem, I still have to check that part, but I wanted to take the chance of helpful feedback in the meantime.
Regards,
On Aug 07, 2008 at 18:27, Vincent Pelletier vincent@nexedi.com wrote:
Hi.
I built & installed ser-2.0.0-rc1 on a debian stable amd64. When I try to redirect a call (case where destination user redirects before answering), it gets an SIP error 477. Corresponding error from SER process running in foreground:
0(30330) ERROR: udp_send: sendto(sock,0x2aebd16fc038,1227,0,xx.xx.xx.xx:xxxx,16): Operation not permitted(1) 0(30330) msg_send: ERROR: udp_send failed 0(30330) ERROR: t_send_branch: sending request on branch 0 failed 0(30330) ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL)
Unfortunately, "1" (EPERM) is not documented in sento manpage, as far as I can see, so it's quite hard to track down that problem.
Kernel version is: 2.6.24.5-grsec iptables is used, but putting netcat in place of SER and the client shows that kernel allows packets to reach client (and more simply, it is possible to do a direct call, it's just redirects which fail).
It can be a grsec problem, I still have to check that part, but I wanted to take the chance of helpful feedback in the meantime.
So far I saw that error only when there where iptables rules blocking the send.
Andrei