[prev in list] [next in list] [prev in thread] [next in thread]
List: serusers
Subject: Re: [SR-Users] Core variable with from userinfo value of sip uri
From: Daniel-Constantin Mierla <miconda () gmail ! com>
Date: 2022-08-30 7:25:18
Message-ID: d1da73e7-610a-6e81-0cb1-81a1017dcc07 () gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hello,
there is a field password in the internal sip uri structure, but being
"NOT RECOMMENDED" in RFC 3261 19.1.1, is not exposed by a variable,
given that so far is was not used by devices I met out there and also
there was no discussion about it on the lists.
Regex is a solution always, as you said, but if someone wants to add a
var for it, I am fine -- a pull request can be made.
Cheers,
Daniel
On 29.08.22 18:21, Denys Pozniak wrote:
> Hello!
>
> It was accidentally noticed that the variable $fU gets the user part
> of userinfo SIP URI (although it is logical and described in the
> document RFC2543).
> I got message below and my spam filter based on $fU passed it inside
> the network, as $fU was test
>
> From: <sip:test:test@1.1.1.1
> <mailto:sip%3Atest%3Atest@1.1.1.1>>;tag=123456
>
> Sure I can filter it through a regular expression, but maybe it's
> worth adding another core variable with the userinfo value?
>
>
> SIP-URL = "sip:" [ userinfo "@" ] hostport
> url-parameters [ headers ]
> userinfo = user [ ":" password ]
> --
>
> BR,
> Denys Pozniak
>
>
>
> __________________________________________________________
> Kamailio - Users Mailing List - Non Commercial Discussions
> * sr-users@lists.kamailio.org
> Important: keep the mailing list in the recipients, do not reply only to the sender!
> Edit mailing list options or unsubscribe:
> * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
[Attachment #5 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p>there is a field password in the internal sip uri structure, but
being "NOT RECOMMENDED" in RFC 3261 19.1.1, is not exposed by a
variable, given that so far is was not used by devices I met out
there and also there was no discussion about it on the lists.</p>
<p>Regex is a solution always, as you said, but if someone wants to
add a var for it, I am fine -- a pull request can be made.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<div class="moz-cite-prefix">On 29.08.22 18:21, Denys Pozniak wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+x3Axpx6G56PdgAmJGNGEHt2h09TKHdOOdxTa66o_S8hbBh3g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hello!</div>
<div><br>
</div>
It was accidentally noticed that the variable $fU gets the user
part of userinfo SIP URI (although it is logical and described
in the document RFC2543).
<div>I got message below and my spam filter based on $fU passed
it inside the network, as $fU was test<br>
</div>
<div><br>
</div>
<div>From: <<a href="mailto:sip%3Atest%3Atest@1.1.1.1"
moz-do-not-send="true">sip:test:test@1.1.1.1</a>>;tag=123456</div>
<div><br>
<div>
<div>Sure I can filter it through a regular expression, but
maybe it's worth adding another core variable with the
userinfo value?</div>
<div><br>
<br>
<pre class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">SIP-URL \
= "sip:" [ userinfo "@" ] hostport url-parameters [ headers ]
userinfo = user [ ":" password ]</pre>
<pre class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">
</pre>
<pre class="gmail-newpage" \
style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><span \
style="font-family:Arial,Helvetica,sans-serif;font-size:small;color:rgb(34,34,34)">--</span>
</pre>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr"><br>
<div>
<div>BR,</div>
<div>Denys Pozniak<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" \
wrap="">__________________________________________________________ Kamailio - Users \
Mailing List - Non Commercial Discussions
* <a class="moz-txt-link-abbreviated" \
href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* <a class="moz-txt-link-freetext" \
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla -- <a class="moz-txt-link-abbreviated" \
href="http://www.asipto.com">www.asipto.com</a> <a class="moz-txt-link-abbreviated" \
href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a \
class="moz-txt-link-abbreviated" \
href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a></pre> \
</body> </html>
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic