The documentation for outbound contains sample configs for edge proxy and registrar configs: http://kamailio.org/docs/modules/4.2.x/modules/outbound.html
I tried to implement these but I don't see anything happen concerning the outbound module. What is supposed to happen to make it work?
The main problem I have is that calls for the endpoints coming in from the registrar fail to get past the loose_routing check and fail with a 500 in the default case of the switch. the R-URI contains username/externalip/port from the endpoint, there is 1 route header (containing the edgeproxy ip) but no username/flow-token. So per http://kamailio.org/docs/modules/4.2.x/modules/rr.html#loose-route-id loose_routing returns false: "If a Route: header is found, the function returns 1 and behaves as described in section 16.12 of RFC 3261. There is only one exception: If the request is out-of-dialog (no to-tag) and there is only one Route: header indicating the local proxy, then the Route: header is removed and the function returns FALSE."
How should the Path header look when registering? According to http://kamailio.org/docs/modules/4.2.x/modules/path.html#idp3043008 there should be a flowtoken inserted, this is not the case. Just a plain Path: sip:ip;lr is added. So when is outbound required?
Can anybody confirm that the examples work?
Hello,
first is important to clarify if you have clients supporting the "SIP-Outbound" extension, which is only for TCP/TLS.
That is different than the (classic) "Outbound Proxy" which got into the common speaking of SIP in the past.
A "classic" Outbound Proxy has to do Path if it routes REGISTER requests.
Cheers, Daniel
On 14/08/15 17:42, Daniel Tryba wrote:
The documentation for outbound contains sample configs for edge proxy and registrar configs: http://kamailio.org/docs/modules/4.2.x/modules/outbound.html
I tried to implement these but I don't see anything happen concerning the outbound module. What is supposed to happen to make it work?
The main problem I have is that calls for the endpoints coming in from the registrar fail to get past the loose_routing check and fail with a 500 in the default case of the switch. the R-URI contains username/externalip/port from the endpoint, there is 1 route header (containing the edgeproxy ip) but no username/flow-token. So per http://kamailio.org/docs/modules/4.2.x/modules/rr.html#loose-route-id loose_routing returns false: "If a Route: header is found, the function returns 1 and behaves as described in section 16.12 of RFC 3261. There is only one exception: If the request is out-of-dialog (no to-tag) and there is only one Route: header indicating the local proxy, then the Route: header is removed and the function returns FALSE."
How should the Path header look when registering? According to http://kamailio.org/docs/modules/4.2.x/modules/path.html#idp3043008 there should be a flowtoken inserted, this is not the case. Just a plain Path: sip:ip;lr is added. So when is outbound required?
Can anybody confirm that the examples work?
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Daniel Tryba -
Daniel-Constantin Mierla