i noticed that if i add sbc application p-call-control parameter ctl;next_hop=ip:port
to invite received by sems sbc, sems sends the request to ip:port, but also replaces host:port of Request URI with ip:port, which in my case is wrong thing to do. is it a bug or intentional that ctl;next_hop=ip:port changes Request-URI rather just causing sems to send the request as is to next_hop like next_hop in sems.conf does? if not a bug, is it somehow possible to make sbc to override sems.conf next_hop value without changing Request-URI? -- juha _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
