Skip to content

SIP TLS Messages not received. Old Message prepended to the new SIP packet in terminal log #1639

Open

Description

@prasenjit-roy

Environment

  • Audio development kit: ELECROW ESP32 Display 1024x600, 7" HMI ESP32-P4 IPS Touch Screen Support AI | Touchscreen
  • [Required] Module or chip used: ESP32-P4
  • [Required] IDF version: v6.1-dev-9078-g0e6b480f858
  • [Required] ADF version: v2.7-306-g12ea3042
  • Build system: CMake ( Visual studio code )
  • [Required] Running log: All logs from power-on to problem recurrence
    *** Case 1 TLS Message not received ********************************************************************************************************************

#########################################################

Peer 'yyyyyyyy1' sends a TLS message 'Check-in'

Packet comes in but no message

#########################################################

MESSAGE sip:xxxxxx@108.20.181.21:59404;transport=tls SIP/2.0
Via: SIP/2.0/TLS sip11.linphone.org;rport;branch=z9hG4bK.4pgUUBptaNg4y9vp72tDQ6086c
Via: SIP/2.0/TLS 192.168.11.37:55071;branch=z9hG4bK-271378178;rport=55071;received=108.20.181.21
Max-Forwards: 69
From: sip:yyyyyyyy1@sip.linphone.org:5061;tag=-422600734
To: sip:xxxxxx@sip.linphone.org:5061
Call-ID: 1EDEFA73207068E1287951DDB94534142D04A8B70F38
CSeq: 6 MESSAGE
Contact: sip:yyyyyyyy1@108.20.181.21:55071;transport=tls
User-Agent: ESP32 SIP/2.0
Content-Type: text/plain
Content-Length: 8

I (264990) SIP: [2026-11-17/21:52:15]<<======================
I (271700) SIP: Sending keep-alive to server state 2 240
I (271700) SIP_SESSION: KEEPALIVE
I (284880) SIP: [2026-11-17/21:52:35]<<=====READ 0602 bytes==
I (284880) SIP:

/* Long time gap, no 200 Ok seen - probably missing the ACK */

#########################################################################

Peer 'yyyyyyyy1' sends next TLS message 'xyz' again

Packet comes in but no message.

However now we see the previous 'Check-in' message at the beginning

#########################################################################

Check-inMESSAGE sip:xxxxxx@108.20.181.21:59404;transport=tls SIP/2.0
Via: SIP/2.0/TLS sip11.linphone.org;rport;branch=z9hG4bK.SD5NXpcN7D6HBZDyjym773cFFB
Via: SIP/2.0/TLS 192.168.11.37:55071;branch=z9hG4bK-2064122055;rport=55071;received=108.20.181.21
Max-Forwards: 69
From: sip:yyyyyyyy1@sip.linphone.org:5061;tag=-111794190
To: sip:xxxxxx@sip.linphone.org:5061
Call-ID: E794DCC7FF10E9B4CB8A2DA950ACE8216CEAE1444A85
CSeq: 8 MESSAGE
Contact: sip:yyyyyyyy1@108.20.181.21:55071;transport=tls
User-Agent: ESP32 SIP/2.0
Content-Type: text/plain
Content-Length: 8

*** Case 2 UDP Messsage Received ********************************************************************************************************************

########################################################

Peer 'yyyyyyyy1' send a UDP message 'Check-in'

Packet comes in the first message as expected

########################################################

I (34380) SIP: [2026-11-18/03:08:47]<<=====READ 0574 bytes==
I (34380) SIP:

MESSAGE sip:xxxxxx@108.20.181.21:11190 SIP/2.0
Via: SIP/2.0/UDP sip11.linphone.org;rport;branch=z9hG4bK.ey9Hym31HFcHSD0ey9Q5404Dca
Via: SIP/2.0/UDP 192.168.11.37:16955;branch=z9hG4bK-1744407382;rport=16955;received=108.20.181.21
Max-Forwards: 69
From: sip:yyyyyyyy1@sip.linphone.org:5060;tag=-213918018
To: sip:xxxxxx@sip.linphone.org:5060
Call-ID: E171D7602345E580A3760A209B5FEFE33AA4BF3ED0D8
CSeq: 6 MESSAGE
Contact: sip:yyyyyyyy1@108.20.181.21:16955
User-Agent: ESP32 SIP/2.0
Content-Type: text/plain
Content-Length: 8

Check-in
I (34430) SIP: [2026-11-18/03:08:47]<<======================
I (34430) SIP: [2026-11-18/03:08:47]=======WRITE 0472 bytes>>
I (34440) SIP:

SIP/2.0 200 OK
Via: SIP/2.0/UDP sip11.linphone.org;rport;branch=z9hG4bK.ey9Hym31HFcHSD0ey9Q5404Dca
Contact: sip:xxxxxx@192.168.11.38:11190;transport=UDP
From: sip:yyyyyyyy1@sip.linphone.org:5060;tag=-213918018
To: sip:xxxxxx@sip.linphone.org:5060;tag=-35701695
Call-ID: E171D7602345E580A3760A209B5FEFE33AA4BF3ED0D8
CSeq: 6 MESSAGE
Server: ESP32 SIP/2.0
Allow: ACK, INVITE, BYE, UPDATE, CANCEL, OPTIONS, INFO, MESSAGE
Content-Length: 0

I (34480) SIP: [2026-11-18/03:08:47]=======================>>
I (34490) SIP_SESSION: MESSAGE from sip:prasenjit.roy1@sip.linphone.org:5060;tag=-213918018 [text/plain]: Check-in
I (39450) SIP: Sending keep-alive to server state 2 30
I (39450) SIP_SESSION: KEEPALIVE

  • Operating system: Windows
  • (Windows only) Environment type: Visual Studio code and esp extension
  • Using an IDE?: [Yes (Visual Studio code )]
  • Power supply: USB

Problem Description

SIP TLS packet received but not the actual message content. Message content appears in the terminal log prepended to the SIP packet like this where 'Check-in' was the actual previous sip message
Check-inMESSAGE sip:xxxxxx@108.20.181.21:59404;transport=tls SIP/2.0

Expected Behavior

SIP TLS message should be received and acked and a 200K should be received

Actual Behavior

SIP TLS packet received but not the actual message content. Message content appears in the terminal log prepended to the SIP packet.

Steps to Reproduce

  1. load a SIP_cli project
  2. set SIP transport to TLS on both
  3. send a message "Hello" from one to the other. ( Does not work )

4 Repeat the same with transport UDP and it works as expected.

// If possible, attach a picture of your setup/wiring here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions