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;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
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:
-
Daniel-Constantin Mierla -
Denys Pozniak