Conversation
|
Call-Id value is something internal at SIP protocol level. There is no reason for letting the user application choose it. |
|
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. |
I don't know what that is and I've never seen anything about that in any SIP RFC specification. |
|
https://datatracker.ietf.org/doc/html/rfc3261#section-8.1.1.4 it says "...generation of Call-IDs is RECOMMENDED." therefore it is not illegal to have the call-id customized |
|
it is also beneficial for users to set the call-id for logging/tracing purposes. |
What is this about? I don't recall it from any spec.
There is already a |
This is not from a spec but a common practice in mobile setups. You can suspend a SIP INVITE on server, send push notification (with the sip call-id of invite), then when the SIP REGISTER arrives with matching sip call-id, the INVITE is resumed and sent to the UAC. The spec i mentioned was related to setting the sip call-id in registers, it is RFC complaint to customize the sip call-id, also the code in the PR is backward compatible. I think folks would benefit from this change but we are fine running our own fork which implements this, please close the PR if you do not want it merged.
|
This is a note for the SIP device implementors. It says nothing about the user being able to "customize" the call-id. |
It is implied because the RFC only recommends auto-generation. I will close PR |
|
No need to close it, we are just discussing. I am on vacation, let's us come back to this soon. |
No description provided.