Hi Juha,
It might not be very clear in the documentation, however, it seems everything
is working as expected.
Here is the way it should work:
- outbound_proxy:
- sets a pre-loaded route, according to which SEMS routes the request.
- the pre-loaded route is used only on first request within a dialog,
except if force_outbound_proxy is set to yes, in which case it is used for each
and every request.
- next_hop:
- sends the request unconditionally to this host, regardless of other
routing parameters (R-URI, Route-HF).
Now, it seems that you would like to have the next_hop behavior (routing
without pre-loaded route), but only for the first request. Subsequent requests
would be routed just normally (R-URI, or Route, if present). Is that correct?
-Raphael.
On 16.10.2012, at 09:34, Juha Heinanen wrote:
> i have in sems.conf:
>
> outbound_proxy=sip:127.0.0.1:5070
> force_outbound_proxy=no
>
> still when i look with ngrep, i see that sems adds Route header to
> outbound proxy when sbc sends out invite:
>
> U 2012/10/16 10:29:17.041217 127.0.0.1:5090 -> 127.0.0.1:5070
> INVITE sip:[email protected]:5074;transport=tcp SIP/2.0.
> Via: SIP/2.0/UDP 127.0.0.1:5090;branch=z9hG4bK.rUVpa98;rport.
> From: Anonymous
> <sip:[email protected]>;tag=443199CF-507D0CCD00009DFC-36D46700.
> To: <sip:[email protected]>.
> CSeq: 10 INVITE.
> Call-ID: 5B1668E8-507D0CCD00009E08-36D46700.
> Contact: <sip:127.0.0.1:5090>.
> Route: <sip:127.0.0.1:5070;lr>.
> ...
>
> is this a bug or feature?
>
> my goal is to get rid of this pre-loaded Route header and still be able
> to use outbound_proxy instead of next_hop.
>
> - juha
> _______________________________________________
> Sems mailing list
> [email protected]
> http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
