Skip to content

Conversation

@eschmidbauer
Copy link

No description provided.

@ibc
Copy link
Member

ibc commented Dec 31, 2025

Call-Id value is something internal at SIP protocol level. There is no reason for letting the user application choose it.

@eschmidbauer
Copy link
Author

there is benefit from letting the user customize it. For example setting a matching call-id in REGISTER to connect a suspended INVITE with same call-id.
This change is backward compatible and RFC compliant.

@ibc
Copy link
Member

ibc commented Dec 31, 2025

For example setting a matching call-id in REGISTER to connect a suspended INVITE with same call-id.

I don't know what that is and I've never seen anything about that in any SIP RFC specification.

@eschmidbauer
Copy link
Author

eschmidbauer commented Dec 31, 2025

https://datatracker.ietf.org/doc/html/rfc3261#section-8.1.1.4
Use of cryptographically random identifiers (RFC 1750 [12]) in the
generation of Call-IDs is RECOMMENDED. Implementations MAY use the
form "localid@host". Call-IDs are case-sensitive and are simply
compared byte-by-byte.

it says "...generation of Call-IDs is RECOMMENDED." therefore it is not illegal to have the call-id customized

@eschmidbauer
Copy link
Author

it is also beneficial for users to set the call-id for logging/tracing purposes.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants