Thanks Alex. I found the issue! That was in device side
https://knowledgebase-iframe.polycom.com/kb/viewContent.do?externalId=15474
--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
___
Kamailio (SER) - Users Mailing List
sr-users@l
It is certainly possible that I am mistaken about the root cause.
—
Sent from my iPad
> On Jan 27, 2020, at 2:37 AM, Zhan Bazarov wrote:
>
> hello! Thanks for reply!
>
> So, now I have two INVITE requests with interval in few seconds:
>
> INVITE sip:jyu3xsfkrz6c5qn@10.3.0.116;transport=tcp
hello! Thanks for reply!
So, now I have two INVITE requests with interval in few seconds:
INVITE sip:jyu3xsfkrz6c5qn@10.3.0.116;transport=tcp SIP/2.0
Record-Route:
Record-Route:
Record-Route:
Via: SIP/2.0/TCP
some.proxy.net:5078;branch=z9hG4bK24ec.940ea1b24f9ae5d68a6f97928661dbb6.0
Via: SIP/2
Hello! Thanks for reply!
Removing unnecessary headers didn't solve issue.
Switching on TCP didn't solve it neither.
--
Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
Is it possible to get a log, sip trace or even a capture for wireshark
out of the phone?
That may reveal more about what had happened.
Med Liberalistiske Hilsner --
Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog
Sofienlundve
Hi Zhan,
At first glance, it does not appear that anything about the second
request is grammatically invalid.
I suspect the problem you are encountering is UDP fragmentation, as
explained in my blog post here:
http://www.evaristesys.com/blog/sip-udp-fragmentation-and-kamailio-the-sip-header-die
We have Kamailio-cluster via route53(round-robin) some-domain.net
we have two kamailio with public IP's
phone1 is registered on kam1
phone2 is registered on kam2
when we are calling from phone1 to phone2 callflow looks:
phone1 => kam1 => asterisk => kam1 => t_relay(address of second
kamailio:50
