401 Unauthorized (Registration failed, retry after 60 second

[ACS_Robert]

1. Brekeke Product Name and Version: Brekeke SIP Server 3.7.7.8/477-1

2. Java version:Java HotSpot(TM) 64-Bit Server VM 9.0.1

3. OS type and the version: Centos 7 x64

4. UA (phone), gateway or other hardware/software involved: Vodia PBX v5.3.2.a

5. Your problem:
We are migrating our user base from an older brekeke installation to a new one, with one account we are running into an issue, the user is created on brekeke (exported from old and imported on new) with exact same settings as old brekeke server.

Changed the registration on the PBX (vodia) to point to the new sip server, left all other trunk details the same, the account registers fine and works.

However within 24 hours the client will call us (from their cellphone) and say that they are unable to place any calls, we log into the phone system (vodia) and the trunk is showing the following error on the registration:401 Unauthorized (Registration failed, retry after 60 seconds)

We have done the following:
= Reset password on the brekeke account and set new password in the trunk on pbx
= Delete the user from brekeke and reconfigure from scratch
= Delete the trunk from the pbx and set it back up from scratch

The only way to get it to re-register is to change the host name on the trunk to something else, wait 60 seconds and change it back, the trunk will then register properly and work for a while but then breaks again

the trunk has a proposed duration for registration at 1hr and will send reregistrations at 50% of whatever the time negotiated on the registration was, the minimum allowed registration time is 5min

we have checked the block list on brekeke and it doesnt show the phone system's IP address or username, the phone system is multi-tenant and has several other customers registering to the same brekeke box without issues

we are at a loss and the customer is getting frustrated we have had to push them back to our older brekeke installation which is having issues (failing) and need a long term solution

[Tata]

Can you capture SIP packets and make sure these "401" responses are sent back from the Brekeke SIP Server?

Can you make a SIP registration successfully if you use another SIP client instead of Vodia with the same SIP account?

Does the same issue happen even if you disable the Block List?

[ACS_Robert]

We have not tried doing a packet capture on it as it is a pain in the butt, the registration is direct to brekeke it does not get passed through to the upstream provider and there are other accounts on the same PBX that are registered to the brekeke server

when the issue occurs we tried to register another trunk on the pbx to the same account and it still blocks it, tried it from a different pbx (still vodia but diff ip address) and it registers fine even while this one wont, leading us to think it is being blocked for being too chatty or something even though its not showing up in any of the block lists

we have not tried to disable the blocking features as it was something we were specifically looking forward to as a feature of the new version (we were migrating from brekeke 2.x) we can try that but need to schedule downtime with the clients as we have some 24/7 clients that use the system

the issue is intermittent when it happens, when we first moved the account over to the new brekeke install it was running fine for 4 days before the issue first occurred, after being unable to fix it we moved them back to the old brekeke server and then swapped them back after troubleshooting some more to the new one, it worked for about half a day then broke again. we have left the trunk registered to brekeke now for 3 days but it has no call traffic going through it (all calls are being routed in/out using a trunk to the old brekeke) and the trunk pointing at the new one is fine still

cant find anything in the gui or documentation but is there some sort of whitelist that we could add the system's IP to so it would never block anything from a given ip address

[Tata]

> is there some sort of whitelist that we could add the system's IP to so it would never block anything from a given ip address

Go to [Block List]->[Filtering Policy] and add the IP address as "Allow".