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
Protushttp://www.protus.com/ npereira@protus.commailto:name@protus.com phone: 613.733.0000 ext.528 MyFax: 613.822.5083
MyFax.comhttp://www.myfax.com/ | my1voice.comhttp://www.my1voice.com/ | Campaigner.comhttp://www.campaigner.com/
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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
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@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@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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
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@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@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
Protushttp://www.protus.com/ npereira@protus.commailto:name@protus.com phone: 613.733.0000 ext.528 MyFax: 613.822.5083
_MyFax.comhttp://www.myfax.com/_ | _my1voice.com http://www.my1voice.com/_ | _Campaigner.comhttp://www.campaigner.com/_
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
Here is the info requested:
listen=udp:10.98.6.6:5060 listen=tcp:10.98.6.6:5060 listen=tcp:10.98.6.6:5065 listen=tcp:10.98.6.6:5066 listen=tcp:10.98.6.6:5067
root@qa-qsuitePBX-01:/etc/kamailio# ifconfig eth0 Link encap:Ethernet HWaddr 00:0c:29:78:c5:c7 inet addr:10.98.6.5 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5c7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1243947 errors:0 dropped:0 overruns:0 frame:0 TX packets:118228 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:98039640 (93.4 MB) TX bytes:24794667 (23.6 MB) Base address:0x1400 Memory:f4820000-f4840000
eth1 Link encap:Ethernet HWaddr 00:0c:29:78:c5:d1 inet addr:10.98.6.6 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5d1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1184823 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:89172609 (85.0 MB) TX bytes:30206 (29.4 KB) Base address:0x1440 Memory:f4840000-f4860000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:434 errors:0 dropped:0 overruns:0 frame:0 TX packets:434 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:238102 (232.5 KB) TX bytes:238102 (232.5 KB)
root@qa-qsuitePBX-01:/etc/kamailio# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth0 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth1 root@qa-qsuitePBX-01:/etc/kamailio#
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, May 19, 2010 4:44 PM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
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@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@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
Protushttp://www.protus.com/ npereira@protus.commailto:name@protus.com phone: 613.733.0000 ext.528 MyFax: 613.822.5083
_MyFax.comhttp://www.myfax.com/_ | _my1voice.com http://www.my1voice.com/_ | _Campaigner.comhttp://www.campaigner.com/_
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
Am 20.05.2010 13:39, schrieb Nelson Pereira:
Here is the info requested:
listen=udp:10.98.6.6:5060 listen=tcp:10.98.6.6:5060 listen=tcp:10.98.6.6:5065 listen=tcp:10.98.6.6:5066 listen=tcp:10.98.6.6:5067
looks OK.
root@qa-qsuitePBX-01:/etc/kamailio# ifconfig eth0 Link encap:Ethernet HWaddr 00:0c:29:78:c5:c7 inet addr:10.98.6.5 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5c7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1243947 errors:0 dropped:0 overruns:0 frame:0 TX packets:118228 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:98039640 (93.4 MB) TX bytes:24794667 (23.6 MB) Base address:0x1400 Memory:f4820000-f4840000
eth1 Link encap:Ethernet HWaddr 00:0c:29:78:c5:d1 inet addr:10.98.6.6 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5d1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1184823 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:89172609 (85.0 MB) TX bytes:30206 (29.4 KB) Base address:0x1440 Memory:f4840000-f4860000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:434 errors:0 dropped:0 overruns:0 frame:0 TX packets:434 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:238102 (232.5 KB) TX bytes:238102 (232.5 KB)
root@qa-qsuitePBX-01:/etc/kamailio# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth0 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth1 root@qa-qsuitePBX-01:/etc/kamailio#
I do not know if having 2 identical routes via 2 different infterfaces can cause any problems. Just for testing I would remove one of the redundant routes just to find out if causes a problem.
Further, for testing remove all iptables: iptables -F
Further, Kamailio logs that it is trying to establish a TCP connection but it fails. Thus, use tcpdump/wireshark to verify if Kamailio really tries to create a TCP connection. Use 2 tcpdump processes and capture eth0 and eth1 separately. Then analyze the tcpdump and watch for the SYN messages. Analyze on which interface they are sent. Analyze the source IP address of the SYN packages. Are there any TCP responses from the other party?
Try to start with a simple setup - e.g. only 1 IP address, and only if it works then make the setup more complex (multiple IP addresses, multiple routes, ...)
regards klaus
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, May 19, 2010 4:44 PM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
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@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@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
Protushttp://www.protus.com/ npereira@protus.commailto:name@protus.com phone: 613.733.0000 ext.528 MyFax: 613.822.5083
_MyFax.comhttp://www.myfax.com/_ | _my1voice.com http://www.my1voice.com/_ | _Campaigner.comhttp://www.campaigner.com/_
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
My problem is that Asterisk and Kamailio are running on the same system.
So how would I set this up in order to not have conflicts?
Nelson Pereira
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 20, 2010 7:51 AM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
Am 20.05.2010 13:39, schrieb Nelson Pereira:
Here is the info requested:
listen=udp:10.98.6.6:5060 listen=tcp:10.98.6.6:5060 listen=tcp:10.98.6.6:5065 listen=tcp:10.98.6.6:5066 listen=tcp:10.98.6.6:5067
looks OK.
root@qa-qsuitePBX-01:/etc/kamailio# ifconfig eth0 Link encap:Ethernet HWaddr 00:0c:29:78:c5:c7 inet addr:10.98.6.5 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5c7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1243947 errors:0 dropped:0 overruns:0 frame:0 TX packets:118228 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:98039640 (93.4 MB) TX bytes:24794667 (23.6 MB) Base address:0x1400 Memory:f4820000-f4840000
eth1 Link encap:Ethernet HWaddr 00:0c:29:78:c5:d1 inet addr:10.98.6.6 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5d1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1184823 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:89172609 (85.0 MB) TX bytes:30206 (29.4 KB) Base address:0x1440 Memory:f4840000-f4860000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:434 errors:0 dropped:0 overruns:0 frame:0 TX packets:434 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:238102 (232.5 KB) TX bytes:238102 (232.5 KB)
root@qa-qsuitePBX-01:/etc/kamailio# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth0 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth1 root@qa-qsuitePBX-01:/etc/kamailio#
I do not know if having 2 identical routes via 2 different infterfaces can cause any problems. Just for testing I would remove one of the redundant routes just to find out if causes a problem.
Further, for testing remove all iptables: iptables -F
Further, Kamailio logs that it is trying to establish a TCP connection but it fails. Thus, use tcpdump/wireshark to verify if Kamailio really tries to create a TCP connection. Use 2 tcpdump processes and capture eth0 and eth1 separately. Then analyze the tcpdump and watch for the SYN messages. Analyze on which interface they are sent. Analyze the source IP address of the SYN packages. Are there any TCP responses from the other party?
Try to start with a simple setup - e.g. only 1 IP address, and only if it works then make the setup more complex (multiple IP addresses, multiple routes, ...)
regards klaus
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, May 19, 2010 4:44 PM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
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@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@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
Protushttp://www.protus.com/ npereira@protus.commailto:name@protus.com phone: 613.733.0000 ext.528 MyFax: 613.822.5083
_MyFax.comhttp://www.myfax.com/_ | _my1voice.com http://www.my1voice.com/_ | _Campaigner.comhttp://www.campaigner.com/_
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
many options
here are some: use different ports 5061 to asterisk and the rest to Kamailio, or virtualize, there are many solutions for virtualization, including VMWARE, VirtualBox(Oracle-SUN), and Xen. or: use different Interfaces real or virtual with different IPs, and listed on the specific interface for each application. kamailio eth0 (ip x.x.x.x) asterisk eth0:1 (ip z.z.z.z)
_______________ Omar
On May 20, 2010, at 8:11 AM, Nelson Pereira wrote:
My problem is that Asterisk and Kamailio are running on the same system.
So how would I set this up in order to not have conflicts?
Nelson Pereira
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 20, 2010 7:51 AM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
Am 20.05.2010 13:39, schrieb Nelson Pereira:
Here is the info requested:
listen=udp:10.98.6.6:5060 listen=tcp:10.98.6.6:5060 listen=tcp:10.98.6.6:5065 listen=tcp:10.98.6.6:5066 listen=tcp:10.98.6.6:5067
looks OK.
root@qa-qsuitePBX-01:/etc/kamailio# ifconfig eth0 Link encap:Ethernet HWaddr 00:0c:29:78:c5:c7 inet addr:10.98.6.5 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5c7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1243947 errors:0 dropped:0 overruns:0 frame:0 TX packets:118228 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:98039640 (93.4 MB) TX bytes:24794667 (23.6 MB) Base address:0x1400 Memory:f4820000-f4840000
eth1 Link encap:Ethernet HWaddr 00:0c:29:78:c5:d1 inet addr:10.98.6.6 Bcast:10.98.7.255 Mask:255.255.254.0 inet6 addr: fe80::20c:29ff:fe78:c5d1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1184823 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:89172609 (85.0 MB) TX bytes:30206 (29.4 KB) Base address:0x1440 Memory:f4840000-f4860000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:434 errors:0 dropped:0 overruns:0 frame:0 TX packets:434 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:238102 (232.5 KB) TX bytes:238102 (232.5 KB)
root@qa-qsuitePBX-01:/etc/kamailio# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0 10.98.6.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth0 0.0.0.0 10.98.6.1 0.0.0.0 UG 100 0 0 eth1 root@qa-qsuitePBX-01:/etc/kamailio#
I do not know if having 2 identical routes via 2 different infterfaces can cause any problems. Just for testing I would remove one of the redundant routes just to find out if causes a problem.
Further, for testing remove all iptables: iptables -F
Further, Kamailio logs that it is trying to establish a TCP connection but it fails. Thus, use tcpdump/wireshark to verify if Kamailio really tries to create a TCP connection. Use 2 tcpdump processes and capture eth0 and eth1 separately. Then analyze the tcpdump and watch for the SYN messages. Analyze on which interface they are sent. Analyze the source IP address of the SYN packages. Are there any TCP responses from the other party?
Try to start with a simple setup - e.g. only 1 IP address, and only if it works then make the setup more complex (multiple IP addresses, multiple routes, ...)
regards klaus
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, May 19, 2010 4:44 PM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
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@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@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
Protushttp://www.protus.com/ npereira@protus.commailto:name@protus.com phone: 613.733.0000 ext.528 MyFax: 613.822.5083
_MyFax.comhttp://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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
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
This is exactly what I am doing.
I have this Asterisk/Kamailio as a host on an ESX server. The host has 2 interfaces, eth0 and eth1, see bellow, the interface config:
root@qa-qsuitePBX-01:~# more /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
# The loopback network interface auto lo iface lo inet loopback
# The primary network interface auto eth0 iface eth0 inet static address 10.98.6.5 netmask 255.255.254.0 network 10.98.6.0 broadcast 10.98.7.255 gateway 10.98.6.1
# The secondary network interface auto eth1 iface eth1 inet static address 10.98.6.6 netmask 255.255.254.0 network 10.98.6.0 broadcast 10.98.7.255 gateway 10.98.6.1
up route add -net 10.98.118.0 netmask 255.255.255.0 gw 10.98.6.1 dev eth1
I do not see the invites going from 6.5 to 6.6 then 118.20
So trying to dummy this down to 1 interface and use different ports. But my problem is I don't know what and where to setup aech app (asterisk and Kamailio) to be on separate ports, and make sure the route in Kamailio is correct.
Nelson Pereira
-----Original Message----- From: Omar [mailto:omar@321communications.com] Sent: Thursday, May 20, 2010 9:25 AM To: Nelson Pereira Cc: Klaus Darilion; sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
many options
here are some: use different ports 5061 to asterisk and the rest to Kamailio, or virtualize, there are many solutions for virtualization, including VMWARE, VirtualBox(Oracle-SUN), and Xen. or: use different Interfaces real or virtual with different IPs, and listed on the specific interface for each application. kamailio eth0 (ip x.x.x.x) asterisk eth0:1 (ip z.z.z.z)
_______________ Omar
Ok, I found out that the firewall was not setup to allow connection...
So can someone explain to me how I need to setup asterisk and Kamailio so that they both use the same interface eth0?
10.98.6.5 is Asterisk 10.98.6.5 is Kamailio 10.98.118.20 is the UM
So basically, the connection would look like this:
Asterisk -UDP-> Kamailio -TCP-> UM
So how can I setup all this this way?
Nelson Pereira
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 20, 2010 7:51 AM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
I do not know if having 2 identical routes via 2 different infterfaces can cause any problems. Just for testing I would remove one of the redundant routes just to find out if causes a problem.
Further, for testing remove all iptables: iptables -F
Further, Kamailio logs that it is trying to establish a TCP connection but it fails. Thus, use tcpdump/wireshark to verify if Kamailio really tries to create a TCP connection. Use 2 tcpdump processes and capture eth0 and eth1 separately. Then analyze the tcpdump and watch for the SYN messages. Analyze on which interface they are sent. Analyze the source IP address of the SYN packages. Are there any TCP responses from the other party?
Try to start with a simple setup - e.g. only 1 IP address, and only if it works then make the setup more complex (multiple IP addresses, multiple routes, ...)
regards klaus
For example:
Asterisk: sip.conf (depends on wether you use Asterisk TCP or UDP):
udpbindaddr=10.98.6.5:4444 tcpenable=yes tcpbindaddr=10.98.6.5:4444
Kamailio: listen=tcp:10.98.6.5:5060 listen=tcp:10.98.6.5:....
Asterisk >1.6 supports TCP, so maybe you do not even need Kamailio.
If you want to sniff the SIP communication between Asterisk and Kamailio you have to sniff on the loopback device, e.g.: tcpdump -i lo port 5060 ngrep -d lo port 5060
you can also sniff on all interfaces, using "any" interface.
regards Klaus
Am 20.05.2010 15:25, schrieb Nelson Pereira:
Ok, I found out that the firewall was not setup to allow connection...
So can someone explain to me how I need to setup asterisk and Kamailio so that they both use the same interface eth0?
10.98.6.5 is Asterisk 10.98.6.5 is Kamailio 10.98.118.20 is the UM
So basically, the connection would look like this:
Asterisk -UDP-> Kamailio -TCP-> UM
So how can I setup all this this way?
Nelson Pereira
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 20, 2010 7:51 AM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
I do not know if having 2 identical routes via 2 different infterfaces can cause any problems. Just for testing I would remove one of the redundant routes just to find out if causes a problem.
Further, for testing remove all iptables: iptables -F
Further, Kamailio logs that it is trying to establish a TCP connection but it fails. Thus, use tcpdump/wireshark to verify if Kamailio really tries to create a TCP connection. Use 2 tcpdump processes and capture eth0 and eth1 separately. Then analyze the tcpdump and watch for the SYN messages. Analyze on which interface they are sent. Analyze the source IP address of the SYN packages. Are there any TCP responses from the other party?
Try to start with a simple setup - e.g. only 1 IP address, and only if it works then make the setup more complex (multiple IP addresses, multiple routes, ...)
regards klaus
Im running asterisk 1.4.30 and cannot run anything else, and going to 1.6 is not an option.
Nelson Pereira Senior Network Specialist
Protus npereira@protus.com phone: 613.733.0000 ext.528 MyFax: 613.822.5083
MyFax.com | my1voice.com | Campaigner.com
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, May 20, 2010 10:12 AM To: Nelson Pereira Cc: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Need help in routing configuration
For example:
Asterisk: sip.conf (depends on wether you use Asterisk TCP or UDP):
udpbindaddr=10.98.6.5:4444 tcpenable=yes tcpbindaddr=10.98.6.5:4444
OK, I think im making some progress...
I can now see that Kamailio is sending the invite to UM, but getting a 302 temporarely moved which is what UM does, and the contact field states CONTACT: sip:1989@10.98.6.5:5065;transport=TCP
Here is the debug from Asterisk:
-- Executing [1102@default:1] Dial("SIP/1103-0000002d", "SIP/1102|5") in new stack -- Called 1102I> -- SIP/1102-0000002e is ringing -- SIP/1102-0000002e is ringing -- SIP/1102-0000002e is ringing -- SIP/1102-0000002e is ringing -- Nobody picked up in 5000 ms -- Executing [1102@default:2] SIPAddHeader("SIP/1103-0000002d", "Diversion: sip:1102@10.98.6.5;reason=user-busy;screen=no;privacy=off") in new stack -- Executing [1102@default:3] Dial("SIP/1103-0000002d", "SIP/1989@EX-UM") in new stack -- Called 1989@EX-UM -- Got SIP response 302 "Moved Temporarily" back from 10.98.6.5 -- Now forwarding SIP/1103-0000002d to 'Local/1989@default' (thanks to SIP/EX-UM-0000002f) -- Executing [1989@default:1] Dial("Local/1989@default-a77b,2", "SIP/1989@EX-UM") in new stack [May 20 10:42:42] WARNING[5440]: app_dial.c:1263 dial_exec_full: Skipping dialing interface 'SIP/1989@EX-UM' again since it has already been dialed == Spawn extension (default, 1989, 1) exited non-zero on 'Local/1989@default-a77b,2' == Everyone is busy/congested at this time (1:0/0/1) -- Executing [1102@default:4] Dial("SIP/1103-0000002d", "SIP/1989@openser5065") in new stack -- Called 1989@openser5065 == Spawn extension (default, 1102, 4) exited non-zero on 'SIP/1103-0000002d' qa-qsuitePBX-01*CLI>
Here is the debug from kamailio. Can anyone make out what all this is?
May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:612]: SIP Request: May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:614]: method: <INVITE> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:616]: uri: sip:1989@10.98.6.5:5061 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:618]: version: <SIP/2.0> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 232, <branch> = <z9hG4bK214eb681>; state=6 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 235, <rport> = <n/a>; state=17 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/parse_via.c:2296]: end of header reached, state=5 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:500]: parse_headers: Via found, flags=2 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:502]: parse_headers: this is the first via May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [receive.c:137]: After parse_msg... May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [receive.c:177]: preparing to run routing scripts... May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/parse_to.c:808]: end of header reached, state=10 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:174]: DEBUG: get_hdr_field: <To> [27]; uri=[sip:1989@10.98.6.5:5061] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:176]: DEBUG: to body [sip:1989@10.98.6.5:5061^M ] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:154]: get_hdr_field: cseq <CSeq>: <102> <INVITE> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: maxfwd [mf_funcs.c:85]: value = 70 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:188]: DEBUG: get_hdr_body : content_length=232 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/msg_parser.c:90]: found end of header May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: rr [loose.c:108]: No Route headers found May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: rr [loose.c:907]: There is no Route HF May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [socket_info.c:485]: grep_sock_info - checking if host==us: 9==9 && [10.98.6.5] == [10.98.6.5] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [socket_info.c:488]: grep_sock_info - checking if port 5061 matches port 5061 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_lookup.c:1387]: DEBUG: t_newtran: msg id=1 , global msg id=0 , T on entrance=0xffffffffffffffff May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_lookup.c:528]: t_lookup_request: start searching: hash=44018, isACK=0 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_lookup.c:485]: DEBUG: RFC3261 transaction matching failed May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_lookup.c:711]: DEBUG: t_lookup_request: no transaction found May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/parse_to.c:179]: DEBUG: add_param: tag=as1444d940 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [parser/parse_to.c:808]: end of header reached, state=29 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_hooks.c:374]: DBG: trans=0x7fe75afad0d8, callback type 1, id 0 entered May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_funcs.c:351]: SER: new INVITE May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [msg_translator.c:200]: check_via_address(10.98.6.5, 10.98.6.5, 0) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [mem/shm_mem.c:105]: WARNING:vqm_resize: resize(0) called May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_reply.c:617]: DEBUG: reply sent out. buf=0x8a6e50: SIP/2.0 100 trying -..., shmem=0x7fe75afaf510: SIP/2.0 100 trying - May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_reply.c:627]: DEBUG: _reply_light: finished May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [msg_translator.c:200]: check_via_address(10.98.6.5, 10.98.6.5, 0) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [tcp_main.c:1786]: tcp_send: no open tcp connection found, opening new one May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [ip_addr.c:116]: tcpconn_new: new tcp connection: 10.98.118.20 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [tcp_main.c:1052]: tcpconn_new: on port 5060, type 2 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [tcp_main.c:1351]: tcpconn_add: hashes: 1794:0:0, 2 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [tcp_main.c:1861]: tcp_send: pending write on new connection 0x7fe75afafb48 (-1/887 bytes written) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: tm [t_funcs.c:388]: SER: new transaction fwd'ed May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [tcp_main.c:3067]: handle_ser_child: read response= 7fe75afafb48, 4, fd 26 from 2 (5414) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [io_wait.h:361]: DBG: io_watch_add(0x7ea7c0, 26, 2, 0x7fe75afafb48), fd_no=19 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) May 20 10:42:42 qa-qsuitePBX-01 last message repeated 3 times May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5414]: DEBUG: <core> [receive.c:280]: receive_msg: cleaning up May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [io_wait.h:767]: DBG: io_watch_chg (0x7ea7c0, 26, 0x1, 0xffffffff) fd_no=20 called May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [io_wait.h:588]: DBG: io_watch_del (0x7ea7c0, 26, -1, 0x0) fd_no=20 called May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [tcp_main.c:3627]: tcp: DBG: sendig to child, events 1 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [tcp_main.c:3336]: send2child: to tcp child 1 10(5422), 0x7fe75afafb48 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_read.c:884]: received n=8 con=0x7fe75afafb48, fd=7 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_read.c:713]: tcp_read_req: content-length= 0 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:622]: SIP Reply (status): May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:624]: version: <SIP/2.0> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:626]: status: <100> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:628]: reason: <Trying> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_to.c:808]: end of header reached, state=10 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:174]: DEBUG: get_hdr_field: <TO> [27]; uri=[sip:1989@10.98.6.5:5061] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:176]: DEBUG: to body [sip:1989@10.98.6.5:5061^M ] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:154]: get_hdr_field: cseq <CSEQ>: <102> <INVITE> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 232, <branch> = <z9hG4bK2fba.ab0b4cf4.0>; state=9 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:2339]: parse_via: next_via May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 232, <branch> = <z9hG4bK214eb681>; state=6 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 235, <rport> = <5060>; state=16 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:2296]: end of header reached, state=5 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:500]: parse_headers: Via found, flags=2 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:502]: parse_headers: this is the first via May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [receive.c:137]: After parse_msg... May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:1080]: DEBUG: t_check_msg: msg id=1 global id=0 T start=0xffffffffffffffff May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:967]: DEBUG: t_reply_matching: hash 44018 label 1338290362 branch 0 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:1018]: DEBUG: t_reply_matching: reply matched (T=0x7fe75afad0d8)! May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:1149]: DEBUG: t_check_msg: msg id=1 global id=1 T end=0x7fe75afad0d8 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_reply.c:1915]: DEBUG: reply_received: org. status uas=100, uac[0]=0 local=0 is_invite=1) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_reply.c:1059]: ->>>>>>>>> T_code=100, new_code=100 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_reply.c:1549]: DEBUG: relay_reply: branch=0, save=0, relay=-1 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) May 20 10:42:42 qa-qsuitePBX-01 last message repeated 5 times May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [receive.c:280]: receive_msg: cleaning up May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [io_wait.h:361]: DBG: io_watch_add(0x82ea20, 7, 2, 0x7fe75afafb48), fd_no=1 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_read.c:713]: tcp_read_req: content-length= 0 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:622]: SIP Reply (status): May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:624]: version: <SIP/2.0> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:626]: status: <302> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:628]: reason: <Moved Temporarily> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_to.c:179]: DEBUG: add_param: tag=7a8e8e99f8 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_to.c:808]: end of header reached, state=29 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:174]: DEBUG: get_hdr_field: <TO> [42]; uri=[sip:1989@10.98.6.5:5061] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:176]: DEBUG: to body [sip:1989@10.98.6.5:5061] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:154]: get_hdr_field: cseq <CSEQ>: <102> <INVITE> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 232, <branch> = <z9hG4bK2fba.ab0b4cf4.0>; state=9 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:2339]: parse_via: next_via May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 232, <branch> = <z9hG4bK214eb681>; state=6 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 235, <rport> = <5060>; state=16 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/parse_via.c:2296]: end of header reached, state=5 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:500]: parse_headers: Via found, flags=2 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [parser/msg_parser.c:502]: parse_headers: this is the first via May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [receive.c:137]: After parse_msg... May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:1080]: DEBUG: t_check_msg: msg id=2 global id=1 T start=0xffffffffffffffff May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:967]: DEBUG: t_reply_matching: hash 44018 label 1338290362 branch 0 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:1018]: DEBUG: t_reply_matching: reply matched (T=0x7fe75afad0d8)! May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_lookup.c:1149]: DEBUG: t_check_msg: msg id=2 global id=2 T end=0x7fe75afad0d8 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_reply.c:1915]: DEBUG: reply_received: org. status uas=100, uac[0]=100 local=0 is_invite=1) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_main.c:2017]: tcp_send: send from reader (5422 (10)), reusing fd May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_main.c:2068]: tcp_send: sending... May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_main.c:2106]: tcp_send: after real write: c= 0x7fe75afafb48 n=303 fd=7 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_main.c:2107]: tcp_send: buf= ACK sip:1989@10.98.6.5:5061 SIP/2.0^M Via: SIP/2.0/TCP 10.98.6.5:5065;branch=z9hG4bK2fba.ab0b4cf4.0^M From: "1103" sip:1103@10.98.6.5;tag=as1444d940^M TO: sip:1989@10.98.6.5:5061;tag=7a8e8e99f8^M Call-ID: 20a58e6b33d1e1f416436cab0c067a5e@10.98.6.5^M CSeq: 102 ACK^M Max-Forwards: 69^M Content-Length: 0^M ^M May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_reply.c:1059]: ->>>>>>>>> T_code=100, new_code=302 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_reply.c:1549]: DEBUG: relay_reply: branch=0, save=0, relay=0 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [msg_translator.c:1876]: old size: 486, new size: 429 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [msg_translator.c:1894]: build_res_from_sip_res: copied size: orig:259, new: 202, rest: 227 msg= SIP/2.0 302 Moved Temporarily^M FROM: "1103"sip:1103@10.98.6.5;tag=as1444d940^M TO: sip:1989@10.98.6.5:5061;tag=7a8e8e99f8^M CSEQ: 102 INVITE^M CALL-ID: 20a58e6b33d1e1f416436cab0c067a5e@10.98.6.5^M VIA: SIP/2.0/UDP 10.98.6.5:5060;branch=z9hG4bK214eb681;rport=5060^M CONTACT: sip:1989@10.98.6.5:5065;transport=TCP^M CONTENT-LENGTH: 0^M SERVER: RTCC/3.0.0.0^M Diversion: sip:1102@10.98.6.5;reason=user-busy;screen=no;privacy=off^M ^M May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:612]: SIP Request: May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:614]: method: <ACK> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:616]: uri: sip:1989@10.98.6.5:5061 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:618]: version: <SIP/2.0> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 232, <branch> = <z9hG4bK214eb681>; state=6 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/parse_via.c:1283]: Found param type 235, <rport> = <n/a>; state=17 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/parse_via.c:2296]: end of header reached, state=5 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:500]: parse_headers: Via found, flags=2 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:502]: parse_headers: this is the first via May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [receive.c:137]: After parse_msg... May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [receive.c:177]: preparing to run routing scripts... May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: sl [sl_funcs.c:335]: to late to be a local ACK! May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/parse_to.c:179]: DEBUG: add_param: tag=7a8e8e99f8 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/parse_to.c:808]: end of header reached, state=29 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:174]: DEBUG: get_hdr_field: <To> [42]; uri=[sip:1989@10.98.6.5:5061] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:176]: DEBUG: to body [sip:1989@10.98.6.5:5061] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:154]: get_hdr_field: cseq <CSeq>: <102> <ACK> May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: maxfwd [mf_funcs.c:85]: value = 70 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:188]: DEBUG: get_hdr_body : content_length=0 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [parser/msg_parser.c:90]: found end of header May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: rr [loose.c:108]: No Route headers found May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: rr [loose.c:907]: There is no Route HF May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [socket_info.c:485]: grep_sock_info - checking if host==us: 9==9 && [10.98.6.5] == [10.98.6.5] May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [socket_info.c:488]: grep_sock_info - checking if port 5061 matches port 5061 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: tm [t_lookup.c:1387]: DEBUG: t_newtran: msg id=2 , global msg id=1 , T on entrance=0xffffffffffffffff May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: tm [t_lookup.c:528]: t_lookup_request: start searching: hash=44018, isACK=1 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: tm [t_lookup.c:470]: DEBUG: RFC3261 transaction matched, tid=214eb681 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: tm [t_lookup.c:728]: DEBUG: t_lookup_request: transaction found (T=0x7fe75afad0d8) May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: tm [t_reply.c:1397]: DEBUG: cleanup_uac_timers: RETR/FR timers reset May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [timer.c:593]: timer_add called on an active timer 0x7fe75afad158 (0x7fe75adf5e30, 0x7fe75adf5e30), flags 201 May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: tm [t_funcs.c:184]: tm: put_on_wait: transaction 0x7fe75afad0d8 already on wait May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) May 20 10:42:42 qa-qsuitePBX-01 last message repeated 5 times May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5416]: DEBUG: <core> [receive.c:280]: receive_msg: cleaning up May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: tm [t_reply.c:1397]: DEBUG: cleanup_uac_timers: RETR/FR timers reset May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [usr_avp.c:629]: DEBUG:destroy_avp_list: destroying list (nil) May 20 10:42:42 qa-qsuitePBX-01 last message repeated 5 times May 20 10:42:42 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [receive.c:280]: receive_msg: cleaning up May 20 10:42:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [io_wait.h:588]: DBG: io_watch_del (0x82ea20, 7, -1, 0x10) fd_no=2 called May 20 10:42:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_read.c:811]: releasing con 0x7fe75afafb48, state 0, fd=7, id=2 May 20 10:42:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5422]: DEBUG: <core> [tcp_read.c:812]: extra_data (nil) May 20 10:42:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [tcp_main.c:2855]: handle_tcp_child: reader response= 7fe75afafb48, 0 from 1 May 20 10:42:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [io_wait.h:361]: DBG: io_watch_add(0x7ea7c0, 26, 2, 0x7fe75afafb48), fd_no=19 May 20 10:42:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [tcp_main.c:2959]: handle_tcp_child: CONN_RELEASE 0x7fe75afafb48 refcnt= 1 May 20 10:44:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [tcp_main.c:3729]: tcp_main: entering timer for 0x7fe75afafb48 (ticks=884010523, timeout=884010523 (0 s), wr_timeout=884008666 (268435339 s)), write queue: 0 bytes May 20 10:44:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [tcp_main.c:3773]: tcp_main: timeout for 0x7fe75afafb48 May 20 10:44:48 qa-qsuitePBX-01 /usr/sbin/kamailio[5425]: DEBUG: <core> [io_wait.h:588]: DBG: io_watch_del (0x7ea7c0, 26, -1, 0x10) fd_no=20 called
Nelson Pereira
-
Alex Balashov -
Klaus Darilion -
Nelson Pereira -
Omar