15 May
2020
15 May
'20
10:33 p.m.
Hello Community,
Do you think in case calls coming from public IP to kamailio which is
listening on private IP with advertise and running rtpproxy. It could be
making issues with the signalling packets?
Should i maybe have 2 NIC configured one for public IP second for private
network without advertise?
I am still seeking for solution of this problem.
Today we changed our configuration to public IP's only and so far it works
well. No stuck calls in dialog.
Best regards!
czw., 14 maj 2020 o 23:15 Alex Balashov <abalashov(a)evaristesys.com>
napisał(a):
On Thu, May 14, 2020 at 10:59:44PM +0200, Voip support
wrote:
Maybe in request route i should add something
like :
is_method("BYE"){
xlog("Received $rm from $si with call id $ci ");
}
Then take wireshark trace and wait for the hung call and check if
kamailio
logs has the line that the BYE was received?
This would confirm the BYE is getting received but it will no give me any
information why ist not relayed.
Extra information is never bad information, and think logging
fundamental requests is good practice. However, I agree that this won't
give you much insight into why it's not relayed. But perhaps there are
contemporaneous log entries which can shed light on that; Kamailio is
generally pretty good about logging situations where t_relay() fails or
an interface cannot be selected or some other networking-related cause
that is known a priori at the time the relay attempt is made.
I'm thinking either outbound routing issue, or Kamailio isn't getting
the BYE in the first place.
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users