<!-- Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment). -->
### Description
The docs for `set_contact_alias()` says:
**The new contact URI is immediately visible to other modules** in the way the fix_nated_contact() does it.
I don't know exactly what is meant by the last part of that sentence as that isn't documented, but the first part certainly doesn't hold:
The following snippet: ``` xlog("L_INFO", " Received Contact: $ct"); if (set_contact_alias()) { xlog("L_INFO", " Aliassed Contact: $ct"); } ```
Causes these log entries: ``` 2022-07-26T15:41:57.351148+02:00 proxydev001 prx1[12116]: INFO: Received Contact: sip:sipp@unknowndomain;transport=udp 2022-07-26T15:41:57.351148+02:00 proxydev001 prx1[12116]: INFO: Aliassed Contact: sip:sipp@unknowndomain;transport=udp ```
Which clearly shows that the changed uri is **not visible** to the `pv` module (which exports `$ct`).
both set_contact_alias() and fix_nated_contact() use lumps to insert new contact uri so its not immediatly visible unless you call msg_apply_changes() juste immediatly after those functions
Indeed is not changing the buffer, but internally signals that contact header was updated. I pushed a commit to docs to clarify.
Closed #3201 as completed.