Hi,
I have kamailio server and a freeswitch server during a call the kamailio passes the call to freeswitch to play a media and back to kamailio for routing to the destination, this works fine however for samsung devices (any ROM using linphone). On other device brands, it does not work it always returns USER_BUSY or NUMBER_NOT_FOUND. After investigation, I found out that if the transport is UDP then it works on all phones, the problem happens if I use TCP as the transport. Anyone had experienced on this?
Thanks, Jason
Hello,
On 10/30/13 3:22 PM, Jason Sia wrote:
Hi,
I have kamailio server and a freeswitch server during a call the kamailio passes the call to freeswitch to play a media and back to kamailio for routing to the destination, this works fine however for samsung devices (any ROM using linphone). On other device brands, it does not work it always returns USER_BUSY or NUMBER_NOT_FOUND. After investigation, I found out that if the transport is UDP then it works on all phones, the problem happens if I use TCP as the transport. Anyone had experienced on this?
for transport tcp and when connection cannot be established, check if t_relay() returns error.
With upcoming 4.1, the behavior should be unified as for udp, and get in a failure_route.
Cheers, Daniel
Daniel-Constantin Mierla writes:
With upcoming 4.1, the behavior should be unified as for udp, and get in a failure_route.
yes, i can confirm that udp and tcp behave the same way in 4.1. the only difference is that in tcp case it takes much longer before failure is detected and failure route is called.
-- juha
This works when I am on a Samsung hardware and not on other hardware. I made a tcpdump on kamailio and on the phones it seems that it was getting wrong ip address and never reached the phones but for Samsung devices it reached the phone and the phone even made a call to the stun server. On Nov 2, 2013 3:32 AM, "Juha Heinanen" jh@tutpro.com wrote:
Daniel-Constantin Mierla writes:
With upcoming 4.1, the behavior should be unified as for udp, and get in a failure_route.
yes, i can confirm that udp and tcp behave the same way in 4.1. the only difference is that in tcp case it takes much longer before failure is detected and failure route is called.
-- 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
Note: The two users are online so they should be able to call each other thus user busy is returned when tcp is used as a transport on non Samsung devices On Nov 3, 2013 7:11 AM, "Jason Sia" jsia18@gmail.com wrote:
This works when I am on a Samsung hardware and not on other hardware. I made a tcpdump on kamailio and on the phones it seems that it was getting wrong ip address and never reached the phones but for Samsung devices it reached the phone and the phone even made a call to the stun server. On Nov 2, 2013 3:32 AM, "Juha Heinanen" jh@tutpro.com wrote:
Daniel-Constantin Mierla writes:
With upcoming 4.1, the behavior should be unified as for udp, and get in a failure_route.
yes, i can confirm that udp and tcp behave the same way in 4.1. the only difference is that in tcp case it takes much longer before failure is detected and failure route is called.
-- 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 -
Jason Sia -
Juha Heinanen