3cx Log Reader - Invalid Character

[bruno.cordeiro]

I got this error message on the 3cx Log Reader:

Invalid character in incoming SIP message: 0x01
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
21/09/2021 14:58:35:150 | 9 | Discarded invalid message: INVITE sip:[email protected]:5060;user=phone SIP/2.0
Max-Forwards: 216
Session-Expires: 3600;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:[email protected];user=phone>
From: <sip:[email protected].199>;tag=3841221508-793254362
P-Asserted-Identity: <sip:[email protected].199;user=phone>
Call-ID: [email protected]
CSeq: 1 INVITE
Allow: PUBLISH,MESSAGE,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Via: SIP/2.0/UDP xxx.xxx.xxx.199:5060;branch=z9hG4bKc25bdcf71f64e06f6a01aeb02fd031e9
Contact: <sip:[email protected].199:5060;tgrp=DEFAULT>
Content-Type: multipart/mixed;boundary=10.249.29.42-1632232708-790872
Accept: application/sdp,application/isup
Content-Length: 498

--10.249.29.42-1632232708-790872
Content-Type: application/sdp

v=0
o=PLMS3HA01BCS 1632236151000 1632236151000 IN IP4 213.228.175.199
s=sip call
c=IN IP4 xxx.xxx.xxx.215
t=0 0
m=audio 40038 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20

--10.249.29.42-1632232708-790872
Content-Type: application/ISUP;version=ETSI356;base=ETSI356
Content-Disposition: signal;handling=optional



Level = 8
Severity = Debug
Tread = 9
Source = /home/repomaster/workspace/TrunkBuild_18_0_final/Sources/Projects/PbxServer/src/MCastTransport.cpp, line:440
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Does someone has a clue to what it is?
(All sensative information is covered by (x))!

 

[NickD_3CX]

I'd be very interested to hear what it is that is sending a SIP INVITE like this. Usually SIP Trunk providers don't send multipart messages like this.
Is it a supported SIP Trunk provider or a generic one? Or is it another SIP Endpoint, like another PBX?

However, as the error character is '0x01', it may not be something visible in the text, it may in fact be something in the hex stream.

 

[bruno.cordeiro]

Hi, thanks for answering, no it is not a supported SIP Trunk provider. I will ask the provider if they can send message with no multipart