Hi,
we are facing the issue with automated failover in same SIP dialog in rtpengine module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for rtpengines that are in another datacenter with latency higher than about 100ms.
configuration modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.1:2222 udp:10.0.0.2:2222") modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.3:2222 udp:10.0.0.4:2222")
INVITE request from kamailio to 10.0.0.1:2222
3:ICE6:remove5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/AVP8:rtcp-muxl5:demuxe7:call-id20:xxx:received-froml3:IP414:x.x.x.xe8:from-tag10:naluniuntp7:command5:offere
RESPONSE
6:result2:oke
ANSWER request is than send to 10.0.0.2:2222 with error
3:ICE5:force5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF8:rtcp-muxl6:accept5:offere7:call-id20:l63nam58lomphlpvli9o13:received-froml3:IP414:18.212.137.170e8:from-tag10:naluniuntp6:to-tag10:as297c65177:command6:answere
RESPONSE
d6:result5:error12:error-reason15:Unknown call-ide
Only possible fix is to have only one setid with only one server.
First RTPengine is not marked as failed in list of rtpengine servers after the first response.
Hi, what's your sipwise rtpengine version? I once encountered similar issue when the call >60s not yet answered, not sure if the same bug, you may want to upgrade your rtpengine.
https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4ca... * [a6d9c78] MT#13067 fix premature call timeout for un-answered calls
rgds, Loi Dang Phone : +84. 774.735.448 Email : loi.dangthanh@gmail.com
On Fri, Mar 6, 2020 at 3:21 PM Michal Popovic michal.popovic@cloudtalk.io wrote:
Hi,
we are facing the issue with automated failover in same SIP dialog in rtpengine module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for rtpengines that are in another datacenter with latency higher than about 100ms.
configuration modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.1:2222 udp: 10.0.0.2:2222") modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.3:2222 udp: 10.0.0.4:2222")
INVITE request from kamailio to 10.0.0.1:2222
3:ICE6:remove5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/AVP8:rtcp-muxl5:demuxe7:call-id20:xxx:received-froml3:IP414:x.x.x.xe8:from-tag10:naluniuntp7:command5:offere
RESPONSE
6:result2:oke
ANSWER request is than send to 10.0.0.2:2222 with error
3:ICE5:force5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF8:rtcp-muxl6:accept5:offere7:call-id20:l63nam58lomphlpvli9o13:received-froml3:IP414:18.212.137.170e8:from-tag10:naluniuntp6:to-tag10:as297c65177:command6:answere
RESPONSE
d6:result5:error12:error-reason15:Unknown call-ide
Only possible fix is to have only one setid with only one server.
First RTPengine is not marked as failed in list of rtpengine servers after the first response. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi,
will try on newest version and be back with result.
Thanks
On 6 Mar 2020, at 09:47, Lợi Đặng loi.dangthanh@gmail.com wrote:
Hi, what's your sipwise rtpengine version? I once encountered similar issue when the call >60s not yet answered, not sure if the same bug, you may want to upgrade your rtpengine. https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4ca... https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4cac837b0/debian/changelog
- [a6d9c78] MT#13067 fix premature call timeout for un-answered calls
rgds, Loi Dang Phone : +84. 774.735.448 Email : loi.dangthanh@gmail.com mailto:loi.dangthanh@gmail.com
On Fri, Mar 6, 2020 at 3:21 PM Michal Popovic <michal.popovic@cloudtalk.io mailto:michal.popovic@cloudtalk.io> wrote: Hi,
we are facing the issue with automated failover in same SIP dialog in rtpengine module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for rtpengines that are in another datacenter with latency higher than about 100ms.
configuration modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.1:2222 http://10.0.0.1:2222/ udp:10.0.0.2:2222 http://10.0.0.2:2222/") modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.3:2222 http://10.0.0.3:2222/ udp:10.0.0.4:2222 http://10.0.0.4:2222/")
INVITE request from kamailio to 10.0.0.1:2222 http://10.0.0.1:2222/
3:ICE6:remove5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/AVP8:rtcp-muxl5:demuxe7:call-id20:xxx:received-froml3:IP414:x.x.x.xe8:from-tag10:naluniuntp7:command5:offere
RESPONSE
6:result2:oke
ANSWER request is than send to 10.0.0.2:2222 http://10.0.0.2:2222/ with error
3:ICE5:force5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF8:rtcp-muxl6:accept5:offere7:call-id20:l63nam58lomphlpvli9o13:received-froml3:IP414:18.212.137.170e8:from-tag10:naluniuntp6:to-tag10:as297c65177:command6:answere
RESPONSE
d6:result5:error12:error-reason15:Unknown call-ide
Only possible fix is to have only one setid with only one server.
First RTPengine is not marked as failed in list of rtpengine servers after the first response. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
So upgrade to version 8.2.1.2 did not helped. Issue is probably in kamailio module itself, because all requests and responses are correct.
On 6 Mar 2020, at 09:52, Michal Popovic michal.popovic@cloudtalk.io wrote:
Hi,
will try on newest version and be back with result.
Thanks
On 6 Mar 2020, at 09:47, Lợi Đặng <loi.dangthanh@gmail.com mailto:loi.dangthanh@gmail.com> wrote:
Hi, what's your sipwise rtpengine version? I once encountered similar issue when the call >60s not yet answered, not sure if the same bug, you may want to upgrade your rtpengine. https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4ca... https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4cac837b0/debian/changelog
- [a6d9c78] MT#13067 fix premature call timeout for un-answered calls
rgds, Loi Dang Phone : +84. 774.735.448 Email : loi.dangthanh@gmail.com mailto:loi.dangthanh@gmail.com
On Fri, Mar 6, 2020 at 3:21 PM Michal Popovic <michal.popovic@cloudtalk.io mailto:michal.popovic@cloudtalk.io> wrote: Hi,
we are facing the issue with automated failover in same SIP dialog in rtpengine module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for rtpengines that are in another datacenter with latency higher than about 100ms.
configuration modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.1:2222 http://10.0.0.1:2222/ udp:10.0.0.2:2222 http://10.0.0.2:2222/") modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.3:2222 http://10.0.0.3:2222/ udp:10.0.0.4:2222 http://10.0.0.4:2222/")
INVITE request from kamailio to 10.0.0.1:2222 http://10.0.0.1:2222/
3:ICE6:remove5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/AVP8:rtcp-muxl5:demuxe7:call-id20:xxx:received-froml3:IP414:x.x.x.xe8:from-tag10:naluniuntp7:command5:offere
RESPONSE
6:result2:oke
ANSWER request is than send to 10.0.0.2:2222 http://10.0.0.2:2222/ with error
3:ICE5:force5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF8:rtcp-muxl6:accept5:offere7:call-id20:l63nam58lomphlpvli9o13:received-froml3:IP414:18.212.137.170e8:from-tag10:naluniuntp6:to-tag10:as297c65177:command6:answere
RESPONSE
d6:result5:error12:error-reason15:Unknown call-ide
Only possible fix is to have only one setid with only one server.
First RTPengine is not marked as failed in list of rtpengine servers after the first response. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Sorry not properly read in the beginning, i thought both answer and offer sent to the same server that triggered the same bug i encountered but they were not. Not sure weird it is? The answer suppose go to the same rtpengine server as the offer. Try increasing kamailio's debug level and tweak with rtpengine module function to see what went wrong? Btw, is there a typo error in the 1st question in having 2 set with 1 set id 1 ==?
rgds, Loi Dang Thanh Phone : +84. 774.735.448 Email : loi.dangthanh@gmail.com
On Fri, Mar 6, 2020 at 4:26 PM Michal Popovic michal.popovic@cloudtalk.io wrote:
So upgrade to version 8.2.1.2 did not helped. Issue is probably in kamailio module itself, because all requests and responses are correct.
On 6 Mar 2020, at 09:52, Michal Popovic michal.popovic@cloudtalk.io wrote:
Hi,
will try on newest version and be back with result.
Thanks
On 6 Mar 2020, at 09:47, Lợi Đặng loi.dangthanh@gmail.com wrote:
Hi, what's your sipwise rtpengine version? I once encountered similar issue when the call >60s not yet answered, not sure if the same bug, you may want to upgrade your rtpengine.
https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4ca...
- [a6d9c78] MT#13067 fix premature call timeout for un-answered calls
rgds, Loi Dang Phone : +84. 774.735.448 Email : loi.dangthanh@gmail.com
On Fri, Mar 6, 2020 at 3:21 PM Michal Popovic michal.popovic@cloudtalk.io wrote:
Hi,
we are facing the issue with automated failover in same SIP dialog in rtpengine module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for rtpengines that are in another datacenter with latency higher than about 100ms.
configuration modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.1:2222 udp: 10.0.0.2:2222") modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.3:2222 udp: 10.0.0.4:2222")
INVITE request from kamailio to 10.0.0.1:2222
3:ICE6:remove5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/AVP8:rtcp-muxl5:demuxe7:call-id20:xxx:received-froml3:IP414:x.x.x.xe8:from-tag10:naluniuntp7:command5:offere
RESPONSE
6:result2:oke
ANSWER request is than send to 10.0.0.2:2222 with error
3:ICE5:force5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF8:rtcp-muxl6:accept5:offere7:call-id20:l63nam58lomphlpvli9o13:received-froml3:IP414:18.212.137.170e8:from-tag10:naluniuntp6:to-tag10:as297c65177:command6:answere
RESPONSE
d6:result5:error12:error-reason15:Unknown call-ide
Only possible fix is to have only one setid with only one server.
First RTPengine is not marked as failed in list of rtpengine servers after the first response. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi,
setid was type, it is 1 and 2. I have just used made-up addresses.
DEBUG shows even strage output
DEBUG: rtpengine [rtpengine.c:3071]: select_rtpp_node_old(): rtpengine hash table lookup failed to find node for calllen=20 callid=f27oej9e3k0o3vhidpoc viabranch=
DEBUG: rtpengine [rtpengine.c:2634]: rtpp_function_call(): rtpengine hash table insert node=udp:10.0.0.1:2222 for calllen=20 callid=f27oej9e3k0o3vhidpoc viabranch=
and response is this
DEBUG: rtpengine [rtpengine.c:3075]: select_rtpp_node_old(): rtpengine hash table lookup find node=udp:10.0.0.1:2222 for calllen=20 callid=f27oej9e3k0o3vhidpoc viabranch=
and even IP from hash table is correct kamailio will send request to another server
rtpp_function_call(): proxy reply: d6:result5:error12:error-reason15:Unknown call-ide ERROR: rtpengine [rtpengine.c:2588]: rtpp_function_call(): proxy replied with error: Unknown call-id
Michal Popovič System engineer
michal.popovic@cloudtalk.io mailto:michal.popovic@cloudtalk.sk www.cloudtalk.io http://www.cloudtalk.io/
CloudTalk s. r. o. Západný rad 31 811 04 Bratislava Slovakia
On 6 Mar 2020, at 10:56, Lợi Đặng loi.dangthanh@gmail.com wrote:
Sorry not properly read in the beginning, i thought both answer and offer sent to the same server that triggered the same bug i encountered but they were not. Not sure weird it is? The answer suppose go to the same rtpengine server as the offer. Try increasing kamailio's debug level and tweak with rtpengine module function to see what went wrong? Btw, is there a typo error in the 1st question in having 2 set with 1 set id 1 ==?
rgds, Loi Dang Thanh Phone : +84. 774.735.448 Email : loi.dangthanh@gmail.com mailto:loi.dangthanh@gmail.com
On Fri, Mar 6, 2020 at 4:26 PM Michal Popovic <michal.popovic@cloudtalk.io mailto:michal.popovic@cloudtalk.io> wrote: So upgrade to version 8.2.1.2 did not helped. Issue is probably in kamailio module itself, because all requests and responses are correct.
On 6 Mar 2020, at 09:52, Michal Popovic <michal.popovic@cloudtalk.io mailto:michal.popovic@cloudtalk.io> wrote:
Hi,
will try on newest version and be back with result.
Thanks
On 6 Mar 2020, at 09:47, Lợi Đặng <loi.dangthanh@gmail.com mailto:loi.dangthanh@gmail.com> wrote:
Hi, what's your sipwise rtpengine version? I once encountered similar issue when the call >60s not yet answered, not sure if the same bug, you may want to upgrade your rtpengine. https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4ca... https://github.com/sipwise/rtpengine/blob/b507e245b2356f8b965a2671ab5f19a4cac837b0/debian/changelog
- [a6d9c78] MT#13067 fix premature call timeout for un-answered calls
rgds, Loi Dang Phone : +84. 774.735.448 Email : loi.dangthanh@gmail.com mailto:loi.dangthanh@gmail.com
On Fri, Mar 6, 2020 at 3:21 PM Michal Popovic <michal.popovic@cloudtalk.io mailto:michal.popovic@cloudtalk.io> wrote: Hi,
we are facing the issue with automated failover in same SIP dialog in rtpengine module. This issue occurs after we upgraded version 4.4.7 to 5.3.2 and only for rtpengines that are in another datacenter with latency higher than about 100ms.
configuration modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.1:2222 http://10.0.0.1:2222/ udp:10.0.0.2:2222 http://10.0.0.2:2222/") modparam("rtpengine", "rtpengine_sock", "1 == udp:10.0.0.3:2222 http://10.0.0.3:2222/ udp:10.0.0.4:2222 http://10.0.0.4:2222/")
INVITE request from kamailio to 10.0.0.1:2222 http://10.0.0.1:2222/
3:ICE6:remove5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol7:RTP/AVP8:rtcp-muxl5:demuxe7:call-id20:xxx:received-froml3:IP414:x.x.x.xe8:from-tag10:naluniuntp7:command5:offere
RESPONSE
6:result2:oke
ANSWER request is than send to 10.0.0.2:2222 http://10.0.0.2:2222/ with error
3:ICE5:force5:flagsl13:trust-address16:always-transcode17:asymmetric-codecs12:loop-protecte7:replacel6:origin18:session-connectione18:transport-protocol9:RTP/SAVPF8:rtcp-muxl6:accept5:offere7:call-id20:l63nam58lomphlpvli9o13:received-froml3:IP414:18.212.137.170e8:from-tag10:naluniuntp6:to-tag10:as297c65177:command6:answere
RESPONSE
d6:result5:error12:error-reason15:Unknown call-ide
Only possible fix is to have only one setid with only one server.
First RTPengine is not marked as failed in list of rtpengine servers after the first response. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org mailto:sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
Lợi Đặng -
Michal Popovic