On 17/07/14 20:56, Andras FOGARASI wrote:
On 7/17/14, 5:34 PM, Frank Carmickle wrote:
On Jul 17, 2014, at 11:27 AM, Andras FOGARASI <fogar...@fogarasi.com> wrote:
On 7/17/14, 3:41 PM, Frank Carmickle wrote:
I would expect that if it was a NAT issue you would see it much sooner than 15
minutes, 30-60 seconds. Are session timers being stripped by Kamailio? You
say it's a TURN server or is it acting more like a media relay where it is
signaled into the path? What TURN server are you using? How is it configured?
The problem occurs even without TURN, in pure peer-to-peer mode. We use
TURN only in emergency case (symmetric NAT and like that...). I do
nothing with session timers - i didn't think about it until now…
How do you set up the TURN only in emergency case? Do the phones do it
themselves? Does Kamailio control the TURN, rtpengine/mediaproxy-ng?
Who sends the bye?
Caller send BYE as i see.
Meanwhile i made some debug: after 15 minutes an UPDATE comes. Sometimes
the UPDATE is answered with 200 OK, then the call doesn't drop,
continues and everything works as expected. Sometimes it's not answered
at all (it seems timeout), then hangs up.
Is the UPDATE forwarded from the proxy? Can you see some activity on the
network? Maybe you can run kamailio with debug=3 in cfg and get more log
messages from there that can provide further hints.
Also, you can try to run over tcp to see if it reproduces in the same way.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
_______________________________________________
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
