30 Oct
2013
30 Oct
'13
4:22 p.m.
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
1 Nov
1 Nov
9:25 p.m.
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 - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
9:32 p.m.
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
3 Nov
3 Nov
1:11 a.m.
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(a)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(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
1:13 a.m.
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(a)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(a)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(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
4041
days inactive
4044
days old
4 comments
3 participants
participants (3)
-
Daniel-Constantin Mierla -
Jason Sia -
Juha Heinanen