[OpenSER-Devel] another media-relay problem

[Dan Pascu]

Juha Heinanen wrote:
> after adding
>
>  echo 1 > /proc/sys/net/ipv4/ip_forward
>
> to /etc/init.d/mediaproxy-relay start case media-relay started at boot.
>
> when i made the fist test call i got the errors below.  after restarting
> relay and dispatcher, the test call worked without problems.
>
> -- juha
>
> Jun  5 12:46:37 localhost media-dispatcher[5812]: [OpenSERControlProtocol,0,] Issuing "update" command to relay at 127.0.0.1
> Jun  5 12:46:37 localhost media-relay[5825]: [RelayClientProtocol,client] Received new SDP offer
> Jun  5 12:46:37 localhost media-relay[5825]: [RelayClientProtocol,client] Traceback (most recent call last):
> Jun  5 12:46:37 localhost media-relay[5825]: [RelayClientProtocol,client]   File "/var/lib/python-support/python2.5/mediaproxy/relay.py", line 119, in lineReceived
> Jun  5 12:46:37 localhost media-relay[5825]: [RelayClientProtocol,client]     response = self.factory.parent.got_command(self.factory.host, self.command, self.headers)
> Jun  5 12:46:37 localhost media-relay[5825]: [RelayClientProtocol,client]   File "/var/lib/python-support/python2.5/mediaproxy/relay.py", line 306, in got_command
> Jun  5 12:46:37 localhost media-relay[5825]: [RelayClientProtocol,client]     local_media = self.session_manager.update_session(dispatcher, **headers)
> Jun  5 12:46:37 localhost media-relay[5825]: [RelayClientProtocol,client]   File "/var/lib/python-support/python2.5/mediaproxy/mediacontrol.py", line 609, in update_session
>   

This error and another one you posted, look like you do not have a 
default route. We made some change that will give an error message if it 
can't determine the address of the interface with the default route. 
Also we added some option to explicitly specify which IP address to use 
for relaying, for people that don't want to use the IP of the interface 
with the default route (which is the most sensible choice in most cases, 
but one should be able to overwrite it for testing purposes or some 
custom environments). These should be available in the next version. 
Until then, make sure your interface is up and you have a default route 
(even if it points to the loopback interface).

-- 
Dan