Juha Heinanen writes: > when conference app receives invite from conf_auth, there is one > record-route entry added by the proxy and of course the same when > conf_auth app receives 200 ok from conference app. but when conf_auth > then sends ack to this 200 ok, the ack contains TWO route entries, which > looks wrong to me.
now i remember that this is exactly the same problem that i reported a week ago about sbc module adding an extra route entry when i had outbound_proxy defined in sbc profile config, but no next_hop_ip and next_hop_port. how can i get rid of the this extra route entry to outbound_proxy when i am not using sbc? there is no next_hop_* params in sems.conf or at least they are not listed in core/etc/sems.conf.sample. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
