I think it is better to use the contact header param only taking optional port and transport from it.
And not use the Record route information at all this way we support NAPTR/SRV and things are less confusing for the user.

Thanks for the pointing this out, it was not my intent to use the port + transport from the RR.

I will :

• update the PR and the doc too explicitly state that the host part can also contain params.
• parse the module contact param in mod_init and fail if is it invalid.
• make sure we are not using puri.port and puri.transport from the RR
• do a few tests

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.