wrote:

Hello, for 1) Is the device behind nat? Do you have tcp connection lifetime parameter value long enough? for 2) is the physical IP a public space IP? Do you have mhomed parameter set? It is a warning saying that the interface returned by OS for connecting to the destination is not in the listen list. for 3) yes it is expected behaviour, you just need to do record routing as usual, nothing special. Cheers, Daniel On 2/13/12 11:43 AM, Mino Haluz wrote: Hi, our customers are using mostly UDP but some of them want to use TCP. The problem is, I get various TCP errors in kamailio log and I do not understand what they mean 1) ERROR: <core> [tcp_main.c:4130]: connect <customerIP:port> failed This means kamailio is trying to connect with TCP to the customer ?? 2) WARNING: tcp_do_connect <customerIP:port> : could not find corresponding listening socket for IPaddress , using default... ( where IPaddress is kamailio physical IP address) Kamailio has one virtual IP address (heartbeat IP address) and one physical. It listens on the virtual IP address but I do not understand why it is trying to use the physical IP address ? I was investigating this thing because the BYE message is not being relayed if the TCP is used (everytime the 2. error message is printed), so that's why I have to understand what it really means... And the last question, 3) If kamailio is relaying the traffic to the PSTN gateway, and the customer is using TCP, kamailio uses TCP as well for connecting to the PSTN gw. Is this behaviour normal ? I would expect that customer -- TCP --> kamailio --- UDP --> GW, and not customer -- TCP --> kamailio --- TCP --> GW, Thanks, Mino _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- http://www.asipto.comhttp://linkedin.com/in/miconda -- http://twitter.com/miconda