Raphael Coeffic writes: > No, at least, not for the same interface. At the moment, you will need > two distinct interfaces. Normally, you would define two interfaces, > one with sip_ip=[IPv4] and media_ip=[IPv4], and one with sip_ip=[IPv6] > and media_ip=[IPv6]. So you will need to use the additional_interfaces > parameter to define the additional one.
ok, with this sems.conf, i didn't get any more complains to syslog: additional_interfaces=ipv4,ipv6 sip_ip_ipv4=127.0.0.1 sip_port_ipv4=5090 media_ip_ipv4=192.98.102.10 rtp_low_port_ipv4=40000 rtp_high_port_ipv4=45999 sip_ip_ipv6=::1 sip_port_ipv6=5090 media_ip_ipv6=2002:c062:660a::1 rtp_low_port_ipv6=46000 rtp_high_port_ipv6=45999 it requires that i use ipv6 for sip signaling between my sip proxy and sems if sdp has ipv6 media address. > However, I have a patch which is not yet ported to master, but will be > shortly, which allows to define signaling-only as well as media-only > interfaces. This would allow you to combine IPv6 signaling with IPv4 > media and vice-versa. that would suit me better, because then all sip traffic between my sip proxy and sems could always use ipv4 no matter what ip version is used by media. > But this means that you will have to specify the > outbound interface for media explicitly, which does not really allow > for using one or the other depending on what is in the SDP... > > Would that fit your purpose? yes it would, provided that i would know how to specify media interface explicitly. > If not, I might find some time to implement automatic media interface > determination based on what is in the SDP. I think that should fix > your scenario. that would, of course, be the simplest solution from user's point of view. but i can live with the config that i showed in above. it just means that i need to add one more (local) listen ipv6 address to my sip proxy. by the way, cisco ios gateways implement ANAT (rfc 4091), which allows sdp stream contains both ipv4 and ipv6 media address. that would be useful in sems outbound calls too. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
