…-request
Set the dialog context before calling dlg_bye_all. In this way the dialog context is the correct one in the event route tm:local-request; otherwise it could happen that, in the timer process, the context is invalid due to some previous timed-out transaction which set (and not reset) the dialog context in the dlg_onreply function (locally generated replies).
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/300
-- Commit Summary --
* modules/dialog: make dialog context available in event route tm:local-request
-- File Changes --
M modules/dialog/dlg_handlers.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/300.patchhttps://github.com/kamailio/kamailio/pull/300.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/300
I finally got everything working but see to consistently receive the following 3 errors (see below) over and over when a call is being collected?
Versions:
Homer 3.6
kamailio 4.3.0-dev4
Captagent 4.2.0
Any assistance would be appreciated.
Errors:
Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9921]: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0)
Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9921]: ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<HEP3#004>>
Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9921]: ERROR: <core> [receive.c:129]: receive_msg(): core parsing of SIP message failed (127.0.0.1:33264/1)
Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9922]: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0)
Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9922]: ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<HEP3#002Ü>
Mar 8 22:04:47 ce-homer2 /usr/local/kamailio/sbin/kamailio[9922]: ERROR: <core> [receive.c:129]: receive_msg(): core parsing of SIP message failed (127.0.0.1:33264/1)
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/107
Hi,
We have a bit of confusion regarding tcp_connecton_timeout core parameter.
The documentation says,
--
Lifetime in seconds for TCP sessions. TCP sessions which are inactive for
longer than *tcp_connection_lifetime* will be closed by Kamailio.
--
However we observe a strange behaviour.
1. The connection is NOT closed by Kamailio unless we additionally set
"close_expired_tcp" parameter in usrloc module,
2. Secondly, if we set this parameter to a smaller value say 70 seconds
while sip register expiry is 600 seconds (and close_expired_tcp parameter
enabled in usrloc module), the connection still remains active (tested
after keeping it idle for 120 seconds then sending a sip request on this
connection, we expected the request to fail but it does not fails).
3. if we set this parameter to greater then sip register value, e.g. 610
seconds and set close_expired_tcp parameter in usrloc, then we observe
disconnect after about 8-10 minutes. Whereas we expect it to continue since
user is re-registering every 600 seconds.
Can you guys explain why this is happening? What keeps a tcp connection
active or makes it inactive?
We are using websockets (which use TCP at lower layer) and we observe there
is no websocket frame sent or received over the tcp connection, yet it
remain active after tcp_connection_lifetime in case 2 above and becomes
inactive in case 3.
We are using Kamailio v4.3.1 SVN Rev. 4717b5 on Debian Wheezy 32bit OS.
Please suggest.
Thank you.