16 Jul
2014
16 Jul
'14
10:54 p.m.
Hello,
I expect that the signaling is ok at least for call setup.
From signling point of view, I can think of following situations:
- endpoints send keep alive packets (or session updates) which are no
answered. You can add an xlog(...) at the top of request_route{} and
reply_route{} blocks printing at least the method, call-id, cseq, from
and to header, plus the response code for reply block. In this case you
can see if there is some signaling before call is dropped.
- the tls connection is cut (can be done by routers in the middle) and
one endpoint disconnects the call instead of trying first to reconnect
If none of the above is the case, then might be some problem with rtp
transmission and call is disconnected by a device because of that.
Cheers,
Daniel
On 16/07/14 20:39, Andras FOGARASI wrote:
Hi,
I have a simple kamailio install (2 servers, using location service and
a failover node with dispatcher, STUN, clients behind different NATs),
without rtpproxy, only peer-to-peer RTP and TURN server if the
connection is really messy (it's not relevant here). Signaling is over
TLS. Both of the clients are behind NAT.
Basically everything works, but some of the calls are dropped after 15
minutes and some seconds, for me it seems the RTP connection is dropped
but not sure.
I cannot find find out wether it's a kamailio problem or client/NAT problem.
Has anyone idea what is going on?
Thanks,
Andras
_______________________________________________
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
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda