Re: [Serusers] SER/PSTN Gateway conf

Yes, if you look at the BYE there is NO WAY SER can find out where to send it. The To header cannot (by RFC) be used for routing and no other header contains either location destination (as in Route) or aor (as in request uri). To check your record routing, look at the INVITE outgoing from your SER towards the gw. If you do proper record routing, take the RFC snippets below and hit the vendor hard on the head. (it may seem that the GW is doing strict routnig, i.e. old-old RFC). g-) The relevant snippet from RFC3261, 12.2.1.1: If the route set is empty, the UAC MUST place the remote target URI into the Request-URI. The UAC MUST NOT add a Route header field to the request. If the route set is not empty, and the first URI in the route set contains the lr parameter (see Section 19.1.1), the UAC MUST place the remote target URI into the Request-URI and MUST include a Route header field containing the route set values in order, including all parameters. If the route set is not empty, and its first URI does not contain the lr parameter, the UAC MUST place the first URI from the route set into the Request-URI, stripping any parameters that are not allowed in a Request-URI. The UAC MUST add a Route header field containing the remainder of the route set values in order, including all parameters. The UAC MUST then place the remote target URI into the Route header field as the last value. Kostas Marneris wrote: