You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Sipp to test or produce freeswitch simulation, and the Call-ID field is set to the beginning of s, for example, s1001, opensips starts and debug mode is enabled, and you will see that the printed signaling content $ci is garbled data.
To Reproduce
Start OpenSIPS
Start traffic with special headers
Inspect traces
Notice the Call-ID has wrong format in logs, and opensips failed to process messages within dialog.
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
OpenSIPS version you are running
Describe the bug
When using Sipp to test or produce freeswitch simulation, and the Call-ID field is set to the beginning of s, for example, s1001, opensips starts and debug mode is enabled, and you will see that the printed signaling content $ci is garbled data.
To Reproduce
Call-ID
has wrong format in logs, and opensips failed to process messages within dialog.sipp:
sipp uac.xml:
Expected behavior
Not garbled in reply.
Relevant System Logs
DBG:dialog:get_dlg_by_callid: input ci=(14)
rm=[INVITE],ci=[?H???????],rs=[180]
rm=[INVITE],ci=[?H???????],rs=[200]
OS/environment information
Additional context
The text was updated successfully, but these errors were encountered: