o Juha Heinanen on 05/23/2011 10:36 AM:
Raphael Coeffic writes:
Sorry Juha, we had to come up with something coherent for multiple
interfaces as well.
sure, no problem. in your two interface example, both were used both
for signaling and media. if sems is behind sip proxy for signaling
(which i common use case), there is no need to use internal interface
for media and no need to use external interface for signaling.
following your configuration style, "null" would need to be a valid
value for sip_ip and media_ip:
default interface:
sip_ip = null
media_ip = eth0
intern interface:
sip_ip = lo
media_ip = null
maybe there's a misunderstanding here. SEMS tries to find the proper
interface to send the RTP from if it can select from several; this
interface's media_ip (or public_ip) is then also put in the SDP. The
interface is chosen by the available interfaces according to where the
first message is sent to (the next hop) or came from - this is in
multiple interfaces situation actually the best indication.
In the above use case, you are using two interfaces but for different
purposes (one for signaling, one for media). This is not an
'additional interface' use case, which you would only have if you had
two interfaces for the same purpose.
Now if anyone can explain this in easy to understand language, we
could add that to the documentation...
Stefan
-- juha
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
--
Stefan Sayer
VoIP Services Consulting and Development
Warschauer Str. 24
10243 Berlin
tel:+491621366449
sip:[email protected]
email/xmpp:[email protected]
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
