[Spce-user] No ipauth id found, block registration if subscriber created via API

[Daniel Grotti]

Hi Mathias,
can you do the following check:

1. create subscriber via GUI with allowed_ips empty, then check:

mysql> select * from kamailio.usr_preferecens where 
username="<SUBSCRIBER_USERNAME>"


2. create subscriber via API with allowed_ips not set, then check:

mysql> select * from kamailio.usr_preferecens where 
username="<SUBSCRIBER_USERNAME>"


Is there any differences?
In point 2 you maybe have allowed_ips set to value="" ?


Another question, what version are you using?



Daniel Grotti

Head of Customer Support                     Sipwise GmbH
e: dgrotti at sipwise.com                     Europaring F15
t: +43(0)130120332                A-2345 Brunn Am Gebirge
w: www.sipwise.com   FN: 305595f   FG: LG Wiener Neustadt

On 5/13/19 1:46 PM, Hohl Matthias wrote:
> Hello,
> 
> We created a new tool for creating subscribers via the SPCE API, but we 
> found out, that created subscribers don’t use the “domain default” 
> allowed_ips setting.
> 
> We definitely create the subscribers without this value. So if we check 
> the subscriber preferences via web gui the “allowed_ips setting is also 
> blank, also via API GET we don’t get any value for “allowed_ips” back… 
> so it normally should use the domain default settings.
> 
> If we create a subscriber via web interface directly and leave this 
> allowed_ips empty, if works like a charme with the “domain defaults 
> allowed_ips” settings. So this problem is just there, if we create a 
> subscriber via API and leave “allowed_ips” empty.
> 
> Subscriber settings:
> 
> If we check the API via GET it preferences looks like this:
> 
> /  //},//
> //  //"ac" : "720",//
> //  //"allowed_clis" : [//
> //      //"43720560060"//
> //  //],//
> //  //"cc" : "43",//
> //  //"cli" : "43720560060",//
> //  //"concurrent_max_per_account" : 4,//
> //  //"e164_to_ruri" : false,//
> //  //"emergency_suffix" : "invalidAC_",//
> //  //"id" : 933,//
> //  //"subscriber_id" : 933//
> }///
> 
> But if we try to register we get this log entries:
> 
> /May 13 13:27:39 spce proxy[2114]: NOTICE: <script>: New request on 
> proxy - M=REGISTER R=sip:x.telematica.at 
> F=sip:43720560060 at x.telematica.at T=sip:43720560060 at x.telematica.at 
> IP=176.123.xxx.xxx:5060 (127.0.0.1:5060) 
> ID=25da2ba63f1576e66b506a9918105d2a at 127.0.0.1 UA='PBX v1.7 R6' 
> DESTIP=127.0.0.1:5062/
> 
> /May 13 13:27:39 spce proxy[2114]: NOTICE: <script>: Sending reply S=100 
> Trying fs='127.0.0.1:5062' du='127.0.0.1:5060' - R=sip:x.telematica.at 
> ID=25da2ba63f1576e66b506a9918105d2a at 127.0.0.1 UA='PBX v1.7 R6'/
> 
> /May 13 13:27:39 spce proxy[2114]: WARNING: <script>: No ipauth id 
> found, block registration - R=sip:x.telematica.at 
> ID=25da2ba63f1576e66b506a9918105d2a at 127.0.0.1 UA='PBX v1.7 R6'/
> 
> If we sent 0.0.0.0 or the registration IP via API for “allowed_ips” or 
> set the “ignore_allowed_ips” setting to true, then we can register.
> 
> So the problem is, that if this settings are not set via API, the 
> subscriber didn’t use the domain default allowed ip list, where we 
> defined our ip ranges.
> 
> Do you have any idea, how to fix that?
> 
> Mit freundlichen Grüßen,
> 
> Matthias Hohl
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>