Stefan Sayer writes: > are you sure you picked the right commit? I'm testing here with > ann_b2b (which essentially does the same), and it sends the reinvite > to next_hop_ip:next_hop_port which is 192.168.5.106:5062 in my case.
it must have been the right commit, because sems does not complain about next_hop_ip and next_hop_port in sems.conf. also # strings /usr/sbin/sems | egrep next_hop_ip Invalid next_hop_ip '%.*s' > can you PM/post me a debug log of the same region? i'll do that in private email. > > also, my proxy still complains about 200 ok from sems not belonging to > > any transaction. looks like conf_auth app does not match the ack > > properly that it receives from conference app to the re-invite that > > conf_auth sent to conference app. > this is a different issue, which makes SEMS match ACK that it sends > through proxy to itself back to the uac transaction instead of the uas > transaction. good when you know what the problem is because it is much more serious than the next hop issue. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
