Stefan Sayer wrote:
Hello,
SER directly sends out the reply message to next_hop without going through the route script. If you need to process outgoing messages from SEMS, either modify them directly in SEMS, or use one SER instance as SIP stack for SEMS on e.g. port 5070, and have one SER proxy record-route. This way you get replies and followup requests on your record-routing proxy.
ok, I see
thanks