Stefan Sayer writes: > ok. just a minor correction: setting outbound_proxy in sems.conf is > ok, setting force_outbound_proxy possibly not.
after cherry picking the last commit to 1.4, i now have in sems.conf: outbound_proxy=sip:127.0.0.1:5080 #force_outbound_proxy=yes next_hop_ip=127.0.0.1 next_hop_port=5080 when conf_auth app sends re-invite to ua that includes ip/port info of the conference in its sdp, wireshark shows that it is NOT send to 127.0.0.1 at port 5080, but to 192.98.102.10 at port 5060, i.e., the above is not honored. route headers are now ok. 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. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
