[Spce-user] Deleted subscriber still registering

[Daniel Grotti]

ah!
can you check the kamailio.sems_registation table?
Do you still have entries there related to deleted subscribers ?


*Daniel Grotti *
Head of Customer Support

Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2032 <callto:+4313012032>
Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
Website: www.sipwise.com <http://www.sipwise.com>

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

On 03/15/2016 12:29 PM, stefanormc wrote:
> not really
>
> there is no end user. let me try to better explain:
>
> - customer ‘mario rossi’ had a subscriber configured
> - this subscriber had a remote authentication set-up in his 
> preferences, against a 
> provider: peer_auth_user, peer_auth_pass, peer_auth_realm,
> - customer was then deleted from NGCP
> - peer receives auth request from NGCP even though there is no 
> subscriber active
>
> this problem showed up after upgrading NGCP from 3,8 to 4,1 on 
> customers/subscribers that were deleted before the upgrade
>
> thanks
>
>
>
>> Il giorno 15/mar/2016, alle ore 09:58, Daniel Grotti 
>> <dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>> ha scritto:
>>
>> Hi Stefano,
>> well, that's an end device issue.
>> If NGCP receive a REGISTER/INVITE it always reply and try to 
>> authenticate the message. That's by design.
>> If the end user fails more then X times (3 by default) and the DoS 
>> attack system is enable, the user will be banned.
>> So I don't see the problem here. Just de-configure your end device.
>>
>> Regards,
>>
>>
>>
>> *Daniel Grotti *
>> Head of Customer Support
>>
>> Sipwise GmbH <http://www.sipwise.com/> , Campus 21/Europaring F15
>> AT-2345 Brunn am Gebirge
>>
>> Phone: +43(0)1 301 2032 <callto:+4313012032>
>> Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
>> Website: www.sipwise.com <http://www.sipwise.com/>
>>
>> Particulars according Austrian Companies Code paragraph 14
>> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
>> FN:305595f, Commercial Court Vienna, ATU64002206
>>
>> On 03/15/2016 09:50 AM, stefanormc wrote:
>>> Hello Daniel,
>>>
>>> I think a missed a meaningful bit: the subscribers’ remote 
>>> authentication towards the provider keeps on trying to register the 
>>> subscriber that was deleted.
>>> The subscriber in nowhere in the db but on the other end I still see 
>>> attempts from sipwise to authenticate the deleted subscriber.
>>>
>>> thanks
>>>
>>>
>>>> Il giorno 14/mar/2016, alle ore 14:12, Daniel Grotti 
>>>> <dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>> ha scritto:
>>>>
>>>> Hi Stefano,
>>>> I don't really understand the issue here.
>>>> How deleted subscriber can be registered ? Where do you see them 
>>>> DB, kamailio mem ?
>>>>
>>>>
>>>>
>>>>
>>>> *Daniel Grotti *
>>>> Head of Customer Support
>>>>
>>>> Sipwise GmbH <http://www.sipwise.com/> , Campus 21/Europaring F15
>>>> AT-2345 Brunn am Gebirge
>>>>
>>>> Phone: +43(0)1 301 2032 <callto:+4313012032>
>>>> Email: dgrotti at sipwise.com <mailto:dgrotti at sipwise.com>
>>>> Website: www.sipwise.com <http://www.sipwise.com/>
>>>>
>>>> Particulars according Austrian Companies Code paragraph 14
>>>> "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
>>>> FN:305595f, Commercial Court Vienna, ATU64002206
>>>>
>>>> On 03/08/2016 10:04 AM, stefanormc wrote:
>>>>> Hello,
>>>>>
>>>>> I’m experiencing the following problem: on a 3.7 sipwise I deleted some subscribers and re-created them on a 4.2 new install. It all worked fine until I upgraded from 3.7 to 4.1 when deleted subscribers started registering again although I did read it should be a bug fix of rel. 4.1. How can I solve it? I thought of moving back the subscriber to the ‘old’ sipwise but I am afraid I would still have 2 UIID.
>>>>> thanks
>>>>> stefano
>>>>> _______________________________________________
>>>>> Spce-user mailing list
>>>>> Spce-user at lists.sipwise.com
>>>>> https://lists.sipwise.com/listinfo/spce-user
>>>>
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20160315/890e78ea/attachment.html>