On 4 Apr 2023, at 13:04, Fred Posner
<fred(a)pgpx.io> wrote:
I don’t believe kamailio does rfc8141 but I may not be correct.
—fred
> On Apr 4, 2023, at 6:03 AM, a.izquierdo(a)zaleos.net wrote:
>
> Hello,
>
> I'm running a Kamailio instance with some routing logic in it. When a UA sends an
INVITE with urn:emergency:service:sos as RURI, Kamailio responds with a 400 Bad Request
URI. I have set debug log level and it looks like the problem is in the parse_uri.c when
sanity_check("1511", "7") is called:
If you read the docs for
the sanity module, you’ll soon discover that it’s focused on SIP URI’s, not URN’s. I do
think that Kamailio can handle URNs
but you have to be careful when selecting which modules and functions to use with those.
Vaguely remember testing this at SIPit, but that was a long time ago :-)
/O
parse_uri(): bad char ':' in state 3 parsed: <urn:emergency:service> (21) /
<urn:emergency:service:sos> (25)
According to RFC8141 (
https://www.rfc-editor.org/rfc/rfc8141), this is a correct URN, but
maybe I'm missing something.
Is there a way to make Kamailio parse this RURI?
Kamailio version used: 5.6.4
Thank you!
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: