now that the send function issue got resolved, i tried core forward function. core cookbook tells:
forward
Forward the SIP request to the given destination in stateless mode. This has the format of [proto:]host[:port]. Host can be an IP or hostname; supported protocols are UDP, TCP and TLS. (For TLS, you need to compile the TLS support into core). If proto or port are not specified, NAPTR and SRV lookups will be used to determine them (if possible).
If destination parameter is missing, the forward will be done based on RURI.
Example of usage:
forward("10.0.0.10:5060"); #or forward();
i then went i tried
forward("tcp:192.98.102.20:5070");
but got errors from that line:
Apr 7 13:52:10 siika /usr/sbin/sip-proxy[22923]: : <core> [proxy.c:278]: ERROR: mk_proxy: could not resolve hostname: "tcp:192.98.102.20:5070" Apr 7 13:52:10 siika /usr/sbin/sip-proxy[22923]: ERROR: <core> [route.c:1214]: fixing failed (code=-478) at cfg:/etc/sip-proxy/sip-proxy.cfg:1584
i also tried with
forward_tcp("192.98.102.20:5070");
but it didn't help either:
Apr 7 13:54:24 siika /usr/sbin/sip-proxy[23056]: : <core> [proxy.c:278]: ERROR: mk_proxy: could not resolve hostname: "192.98.102.20:5070" Apr 7 13:54:24 siika /usr/sbin/sip-proxy[23056]: ERROR: <core> [route.c:1214]: fixing failed (code=-478) at cfg:/etc/sip-proxy/sip-proxy.cfg:1584
how should core cookbook be fixed this time?
-- juha
Hello,
I expect is the old SER parameter format, where it actually requires host and port as different parameter:
forward("1.2.3.4", 5060);
The wiki content looks like documenting the openser style of parameter, but then we got the core from ser for v3.0 and perhaps nobody spotted the difference. There are some common cases, like just forrward() and you can set the $du to get it via an outbound proxy address.
Perhaps the functions should be moved to corex module and add support for all kind of combinations, including pv parameters.
Cheers, Daniel
On 4/7/13 12:57 PM, Juha Heinanen wrote:
now that the send function issue got resolved, i tried core forward function. core cookbook tells:
forward
Forward the SIP request to the given destination in stateless mode. This has the format of [proto:]host[:port]. Host can be an IP or hostname; supported protocols are UDP, TCP and TLS. (For TLS, you need to compile the TLS support into core). If proto or port are not specified, NAPTR and SRV lookups will be used to determine them (if possible).
If destination parameter is missing, the forward will be done based on RURI.
Example of usage:
forward("10.0.0.10:5060"); #or forward();
i then went i tried
forward("tcp:192.98.102.20:5070");
but got errors from that line:
Apr 7 13:52:10 siika /usr/sbin/sip-proxy[22923]: : <core> [proxy.c:278]: ERROR: mk_proxy: could not resolve hostname: "tcp:192.98.102.20:5070" Apr 7 13:52:10 siika /usr/sbin/sip-proxy[22923]: ERROR: <core> [route.c:1214]: fixing failed (code=-478) at cfg:/etc/sip-proxy/sip-proxy.cfg:1584
i also tried with
forward_tcp("192.98.102.20:5070");
but it didn't help either:
Apr 7 13:54:24 siika /usr/sbin/sip-proxy[23056]: : <core> [proxy.c:278]: ERROR: mk_proxy: could not resolve hostname: "192.98.102.20:5070" Apr 7 13:54:24 siika /usr/sbin/sip-proxy[23056]: ERROR: <core> [route.c:1214]: fixing failed (code=-478) at cfg:/etc/sip-proxy/sip-proxy.cfg:1584
how should core cookbook be fixed this time?
-- juha
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-Constantin Mierla writes:
Perhaps the functions should be moved to corex module and add support for all kind of combinations, including pv parameters.
sounds like a good plan to move forward functions to core. in the meantime, i'll update the wiki page and only document the $du/forward() approach.
-- juha