[Sems] media

Discussion:

[Sems] media_ip

Jeremy A

2009-07-27 06:14:58 UTC

I have discovered a sems.conf parameter - media_ip - which sets the
originating IP address for media (RTP)

Ordinarily this does not need to be set, but in the case of dual homed
servers this can default to the wrong interface.

This has not been a problem for me so far - in fact I not sure if it has
any effect. However can I suggest the template sems.conf file include an
entry and description for it?

Thanks

Jeremy

Stefan Sayer

2009-07-27 07:44:07 UTC

Permalink

Hi,

Post by Jeremy A
I have discovered a sems.conf parameter - media_ip - which sets the
originating IP address for media (RTP)
Ordinarily this does not need to be set, but in the case of dual homed
servers this can default to the wrong interface.
This has not been a problem for me so far - in fact I not sure if it has
any effect. However can I suggest the template sems.conf file include an
entry and description for it?

it's the first one (both 1.1 and trunk):
http://ftp.iptel.org/pub/sems/doc/current/sems.conf.sample.html

############################################################
# Network configuration

# 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.
#
# Examples:
# media_ip=10.0.0.34
# media_ip=eth0

BR
Stefan

Post by Jeremy A
Thanks
Jeremy
_______________________________________________
Sems mailing list
Sems at lists.iptel.org
http://lists.iptel.org/mailman/listinfo/sems

--
Stefan Sayer
VoIP Services

stefan.sayer at iptego.com
www.iptego.com

IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany

Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann

Jeremy A

2009-07-27 07:53:14 UTC

Permalink

Post by Stefan Sayer
http://ftp.iptel.org/pub/sems/doc/current/sems.conf.sample.html
############################################################
# Network configuration
# 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.
#
# media_ip=10.0.0.34
# media_ip=eth0

Thanks, I just kept updating my legacy sems.conf so missed the new (?)
parameter.

A supplementary question is how this works in dual homed machines? I
guess that it would be very helpful if the advertised media IP matched
the interface it was being used on?

I have a dual homed machine - but that is also a gateway, so the public
IP media address advertised internally still routes to the server. If
the server is not the gateway then special routing may be necessary?

Jeremy

Stefan Sayer

2009-07-27 12:08:08 UTC

Permalink

Post by Jeremy A

Thanks, I just kept updating my legacy sems.conf so missed the new (?)

Post by Jeremy A
parameter.
A supplementary question is how this works in dual homed machines? I
guess that it would be very helpful if the advertised media IP matched
the interface it was being used on?

the advertised IP used is the configured "public_ip", and if this is not
set, then the "media_ip" is used. the interface used is always the
"media_ip". Some days ago Andreas posted a patch for media server behind
static NAT, and advertised SIP/media IP to be configured separately. See
the email with subject "public_ip has no effect".

Post by Jeremy A
I have a dual homed machine - but that is also a gateway, so the public
IP media address advertised internally still routes to the server. If
the server is not the gateway then special routing may be necessary?

hm, I don't know if I get you right, but if your media server is on a
private network, then you definitely need special routing; if you have
e.g. static NAT, then the advertised IP address needs to match the
publicly visible one.

Stefan

Post by Jeremy A
Jeremy
_______________________________________________
Sems mailing list
Sems at lists.iptel.org
http://lists.iptel.org/mailman/listinfo/sems