Hi Juha,
this way strange... I do not use the media_ip parameter either... But
everything works like a charm.
Do you set other parameters like 'sip_ip' or 'public_ip'?
Or maybe this is linux specific? Stefan, how does it work for you?
Cheers
Raphael.
On 21.05.11 19:31, Juha Heinanen wrote:
one more thing: in 1.4, leaving media_ip sems.conf commented out makes
sems to issue errors:
May 21 20:26:58 sars sems[8734]: [#b6251b70] [send, AmRtpPacket.cpp:212] ERROR:
while sending RTP packet: Invalid argument
May 21 20:26:58 sars sems[8734]: [#b6251b70] [compile_and_send,
AmRtpStream.cpp:311] ERROR: while sending RTP packet.
so this is not anymore true:
# optional parameter: media_ip=<ip_address>|<device>
#
# - this informs SEMS about the IP address or interface that
# SEMS uses to send and receive media. If not set, defaults
# to first non-loopback interface.
i have only one non-loopback interface:
eth0 Link encap:Ethernet HWaddr 00:01:2e:bc:9c:64
inet addr:xxx.xxx.xxx.xxx Bcast:192.98.100.255 Mask:255.255.255.0
inet6 addr: fe80::201:2eff:febc:9c64/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:861085 errors:0 dropped:0 overruns:0 frame:0
TX packets:76502 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:243231032 (231.9 MiB) TX bytes:43117680 (41.1 MiB)
Interrupt:27 Base address:0xe000
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:63971 errors:0 dropped:0 overruns:0 frame:0
TX packets:63971 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8174210 (7.7 MiB) TX bytes:8174210 (7.7 MiB)
-- juha
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
