15 May
2024
15 May
'24
7:28 p.m.
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please
use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on
sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask
on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the
developers to troubleshoot the issue.
Note that an issue report may be closed automatically after about 2 months
if there is no interest from developers or community users on pursuing it, being
considered expired. In such case, it can be reopened by writing a comment that includes
the token `/notexpired`. About two weeks before considered expired, the issue is
marked with the label `stale`, trying to notify the submitter and everyone else
that might be interested in it. To remove the label `stale`, write a comment that
includes the token `/notstale`. Also, any comment postpone the `expire` timeline,
being considered that there is interest in pursuing the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
--
### Description
we are using version: kamailio 5.5.1 (x86_64/linux) 8aa8df-dirty and we have a setup with
2 kamailio instances. First one is doing topoh, and the second one is supposed to not do
it
Despite this we do see that some replies the second instance is masking some headers like
record route and contact in the 200ok (not in the 180)
Besides, seems that when the b-side sends a BYE, kamailio show an error, see in logs part
However, in the sip pcap we do see thre BYE like it should be. At least that's what it
seems to me
i attach you the trace
[topoh_bye_bad_message.txt](https://github.com/kamailio/kamailio/files/15324…
do you have any idea of what can be the issue?
<!--
Explain what you did, what you expected to happen, and what actually happened.
--
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
--
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
--
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them
next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
--
```
May 15 13:19:42 vqbert-2 /usr/local/kamailio/sbin/kamailio[31824]: ERROR: <core>
[core/parser/parse_fline.c:272]: parse_first_line(): parse_first_line: bad message
(offset: 54)
��%����QI:19:42 vqbert-2 /usr/local/kamailio/sbin/kamailio[31824]: ERROR: <core>
[core/parser/msg_parser.c:748]: parse_msg(): ERROR: parse_msg: message=<BYE
�ͥ���ĸ��Ը��ĸ���������Ʌ�������Ց��!���ᕈ�|���
����������������� SIP/2.0
Via: SIP/2.0/UDP
199.244.96.39:5060;TH=ucv;branch=z9hG4bK-524287-1---513df3f6b3057f235eef63c542634016;rport
Via: SIP/2.0/UDP 199.244.96.46:5071;rport=5071;branch=z9hG4bK-mx5umw4feykudkd5
Max-Forwards: 69
Route: <sip:79.170.71.169;lr;ftag=11002597000844;did=7842.5393 Route:
<sip:79.170.71.168;lr=on;ftag=11002597000844;did=b09.3b49
��%����QI���ĸ��Ը��ĸ���������Ʌ�������Ց�����!���ᕈ�|���
����������>�����������������`�!ɉU�
Contact: sip:199.244.96.46:5071
To: +233240979290 <sip:+233240979290@79.170.71.168;user=phone>;tag=11002597000844
From: +233307000929
<sip:+233307000929@199.244.96.39.SBC1;user=phone>;tag=W7OXULJ726L2OYQEVKNA____.i
Call-ID: Sonoc2Did!!:C9WJ3uq4gtNwMlcfzxFlM.jAkx0J34pvaRgtCt0vPl0EPxFwMJZfWJZfMBy7MP**
CSeq: 905 BYE
Allow: INVITE, ACK, BYE, CANCEL, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS, UPDATE
User-Agent: PortaSIP
cisco-GUID: 3592442246-2620412195-1372314391-1317599184
h323-conf-id: 3592442246-2620412195-1372314391-1317599184
Content-Length: 0
TH: uch
May 15 13:19:42 vqbert-2
/usr/local/kamailio/sbin/kamailio[31824]: ERROR: <core> [core/receive.c:377]:
receive_msg(): core parsing of SIP message failed (199.244.96.39:5060/1)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save
in a pcap file, then add them next, or attach to issue, or provide a link to download them
(e.g., to a pastebin site).
--
```
No. Time Source Destination Protocol Length Info
17 62.116377 19.24.9.39 10.100.10.169 SIP 1273 Request:
BYE
sip:127.0.0.8;line=sonoc2did-N6IAzBPfOBVfWmZfWBF7WlN-W.y6Mx14NEt7Nw05NhPQpRaAz4rApx4ZgRVZ9lF6z4WZpFIqH.PXKtexHRgEgEgEgEgEORgEgEgEgEgE
|
Frame 17: 1273 bytes on wire (10184 bits), 1273 bytes captured (10184 bits)
Linux cooked capture
Internet Protocol Version 4, Src: 19.24.9.39, Dst: 10.100.10.169
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Session Initiation Protocol (BYE)
Request-Line: BYE
sip:127.0.0.8;line=sonoc2did-N6IAzBPfOBVfWmZfWBF7WlN-W.y6Mx14NEt7Nw05NhPQpRaAz4rApx4ZgRVZ9lF6z4WZpFIqH.PXKtexHRgEgEgEgEgEORgEgEgEgEgE
SIP/2.0
Method: BYE
Request-URI:
sip:127.0.0.8;line=sonoc2did-N6IAzBPfOBVfWmZfWBF7WlN-W.y6Mx14NEt7Nw05NhPQpRaAz4rApx4ZgRVZ9lF6z4WZpFIqH.PXKtexHRgEgEgEgEgEORgEgEgEgEgE
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
19.24.9.39:5060;branch=z9hG4bK-524287-1---513df3f6b3057f235eef63c542634016;rport
Via: SIP/2.0/UDP 19.24.9.46:5071;rport=5071;branch=z9hG4bK-mx5umw4feykudkd5
Max-Forwards: 69
Route: <sip:10.100.10.169;lr;ftag=11002597000844;did=7842.5393 Route:
<sip:10.100.10.168;lr=on;ftag=11002597000844;did=b09.3b49
Route:
<sip:127.0.0.8;line=sonoc2did-N6IAzBPfOBVfWmZfWBF7WlN-W.y6Mx14NEt7Nw05NhPQpRaAz6fLz4rApx4ZgRVZ9lF6z4WZpFIqH.PXKtexHRgEgEgEgEgEORgEgEgEgEgEzuc1mUpGMEeK3jW5o61Yg.4fWBMLWc** Contact: sip:19.24.9.46:5071
To: +233240979290
<sip:+233240979290@10.100.10.168;user=phone>;tag=11002597000844
From: +233307000929
<sip:+233307000929@19.24.9.39.SBC1;user=phone>;tag=W7OXULJ726L2OYQEVKNA____.i
Call-ID:
Sonoc2Did!!:C9WJ3uq4gtNwMlcfzxFlM.jAkx0J34pvaRgtCt0vPl0EPxFwMJZfWJZfMBy7MP**
[Generated Call-ID:
Sonoc2Did!!:C9WJ3uq4gtNwMlcfzxFlM.jAkx0J34pvaRgtCt0vPl0EPxFwMJZfWJZfMBy7MP**]
CSeq: 905 BYE
Allow: INVITE, ACK, BYE, CANCEL, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS,
UPDATE
User-Agent: PortaSIP
cisco-GUID: 3592442246-2620412195-1372314391-1317599184
h323-conf-id: 3592442246-2620412195-1372314391-1317599184
Content-Length: 0
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull
request with a fix.
--
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04,
CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
--
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3853
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3853(a)github.com