2008/11/28 Maxim Sobolev <[EMAIL PROTECTED]>:
> Joan wrote:
>> DBUG:handle_command: received command "9506_2 U
>> [EMAIL PROTECTED] 192.168.253.12 16434
>> f0cdb2c2aee55197o0;1"
>> INFO:handle_command: new session [EMAIL PROTECTED], tag
>> f0cdb2c2aee55197o0;1 requested, type strong
>> ERR:handle_command: can't create listener
>> DBUG:doreply: sending reply "9506_2 E10
>
> That's weird. The only case when the RTPproxy can fail like this is when
> it cannot allocate a UDP ports for the session, either due to ports
> already taken by other application or due to kernel not allowing to use
> any ports in the specified range (EADDRINUSE or EACCES). Can you please
> answer the following questions to help me identify the issue:
>
> 1. Did you make any changes to the sources or defines?
>
No, the only change I made was with the include, the one already
commited into trunk.
Currently I've built from a clean "cvs up"
> 2. What is exact command line that you use to run the proxy?
>
rtpproxy as "rtpproxy -s udp:localhost 15000 -f -u openser -l 192.168.253.98
>
> 3. Can you please send me "ifconfig -a" output on that machine?
>
eth0 Link encap:Ethernet HWaddr 00:17:31:b3:04:f8
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:23 Base address:0xc000
eth2 Link encap:Ethernet HWaddr 00:04:76:1c:e9:46
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:18 Base address:0x800
eth3 Link encap:Ethernet HWaddr 00:c0:26:20:03:b0
inet addr:192.168.253.98 Bcast:192.168.253.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:26ff:fe20:3b0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1968265 errors:0 dropped:0 overruns:0 frame:0
TX packets:982835 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2775827076 (2.5 GiB) TX bytes:81564089 (77.7 MiB)
Interrupt:17 Base address:0xe800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:249 errors:0 dropped:0 overruns:0 frame:0
TX packets:249 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16938 (16.5 KiB) TX bytes:16938 (16.5 KiB)
As you will see, there's only one interface active other than the
loopback, also there aren't firewalls.
There's no difference enabling/disabling ip_forwarding
Regards
_______________________________________________
Users mailing list
Users@rtpproxy.org
http://lists.rtpproxy.org/mailman/listinfo/users
