From Kamailio point of view everything is OK. There are just some
issues with your network/TCP configuration.
Kamailio is unable to open a TCP connection to 10.98.118.20, this can
have several reasons:
- no route to 10.98.118.20
- at 10.98.118.20 there is no application listening on port 5060
- a firewall between you and 10.98.118.20
- a local network configuration problem
It would be useful if you could post your Kamailio "listen="
configuration, an "ifconfig" dump and a "route -n" dump.
regards
Klaus
configuration
Am 19.05.2010 20:11, schrieb Nelson Pereira:
I did see that the TM module syntax did change, so I
made the changes in the route, and it looks like this:
# main request routing logic
route{
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
exit;
};
if (msg:len>= 2048 ) {
sl_send_reply("513", "Message too big");
exit;
};
if (loose_route()) {
append_hf("P-hint: rr-enforced\r\n");
route(1);
};
if (!uri==myself) {
append_hf("P-hint: outbound\r\n");
route(1);
};
route(1);
}
route[1]
{
if (src_ip==10.98.6.5) {
t_relay_to_tcp("10.98.118.20", "5060");
}
else {
t_relay_to_tcp();
}
}
This still does not work, im getting the bellow in syslog:
May 19 14:05:09 qa-qsuitePBX-01 /usr/sbin/kamailio[2215]: WARNING:<core>
[tcp_main.c:1200]: WARNING: tcp_do_connect 10.98.118.20:5060: could not find corresponding
listening socket for 10.98.6.5, using default...
May 19 14:05:19 qa-qsuitePBX-01 /usr/sbin/kamailio[2227]: ERROR:<core>
[tcp_main.c:3748]: connect 10.98.118.20:5060 failed (timeout)
May 19 14:05:39 qa-qsuitePBX-01 /usr/sbin/kamailio[2215]: WARNING:<core>
[tcp_main.c:1200]: WARNING: tcp_do_connect 10.98.118.20:5060: could not find corresponding
listening socket for 10.98.6.5, using default...
May 19 14:05:54 qa-qsuitePBX-01 /usr/sbin/kamailio[2227]: ERROR:<core>
[tcp_main.c:3748]: connect 10.98.118.20:5060 failed (timeout)
May 19 14:07:53 qa-qsuitePBX-01 /usr/sbin/kamailio[2215]: WARNING:<core>
[tcp_main.c:1200]: WARNING: tcp_do_connect 10.98.118.20:5060: could not find corresponding
listening socket for 10.98.6.5, using default...
Nelson Pereira
-----Original Message-----
From: sr-users-bounces(a)lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Alex Balashov
Sent: Wednesday, May 19, 2010 2:01 PM
To: sr-users(a)lists.sip-router.org
Subject: Re: [SR-Users] Need help in routing configuration
You might do well to specify what about it "doesn't work," e.g. log
messages and such.
If you're using Kamailio 3.0+, the reason is most likely that t_relay()
invocation syntax has changed:
http://www.kamailio.org/docs/modules/3.0.x/modules/tm.html#t_relay
On 05/19/2010 01:41 PM, Nelson Pereira wrote:
I have the bellow setup for openser, yet this
wont work in Kamilio.
Wondering if anyone could help to make this routing code work?
What Im looking to do is receive Invites in UDP and relaying it via TCP….
route{
if (!mf_process_maxfwd_header("10")) {
sl_send_reply("483","Too Many Hops");
exit;
};
if (msg:len>= 2048 ) {
sl_send_reply("513", "Message too big");
exit;
};
if (loose_route()) {
append_hf("P-hint: rr-enforced\r\n");
route(1);
};
if (!uri==myself) {
append_hf("P-hint: outbound\r\n");
route(1);
};
route(1);
}
route[1]
{
if (src_ip==10.98.6.5) {
if (dst_port==5060) {
t_relay("tcp:10.98.118.20:5060");
}
if (dst_port==5065) {
t_relay("tcp:10.98.118.20:5065");
}
else if (dst_port==5066) {
t_relay("tcp:10.98.118.20:5066");
}
else if (dst_port==5067) {
t_relay("tcp:10.98.118.20:5067");
}
# else {
# t_relay("tcp:10.98.118.20:5060");
# }
}
else {
t_relay("udp:10.98.6.5:5060");
};
}
*Nelson Pereira*
Senior Network Specialist
Protus<http://www.protus.com/>
npereira@protus.com<mailto:name@protus.com>
phone: 613.733.0000 ext.528
MyFax: 613.822.5083
_MyFax.com<http://www.myfax.com/>_ |
_my1voice.com
<http://www.my1voice.com/>_ |
_Campaigner.com<http://www.campaigner.com/>_
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users