1. Brekeke Product Name and Version: Brekeke SIP Server Advanced Edition v3.17.2.1/583
2. Java version: 11.0.0.1
3. OS type and the version: Ubuntu 24.04 LTS
4. UA (phone), gateway or other hardware/software involved: None
5. Your problem:
Database Cache mode, anyone know how it works (apart from the obvious!!!)
We use 3rd party DB and have another system where user add their SIP login accounts. this then gets replicated to the SQL DB that BSS queries.
All has been fine until we upgraded and now have cache mode. What we have discovered is that a user adds their SIP account to our system. They then login in their SIP phone BEFORE the sync has taken place, so at this stage BSS would fail the register. After a few mins our system adds the SIP account into BSS, but after this, BSS rejects all attempts for that user name, without even checking the DB.
If however I login to the BSS admin page, and make any change to the username, eg add a single '.' to the comment, then BSS allows login and works. I suspect me making a change to the description causes the cache to be refreshed and BSS looks at the DB.
I really want to keep the cache as I think it's really useful for keeping DB traffic down, but how can I avoid the above scenario? I looked through API commands but there doesn't seem to be much about how to force BSS to refresh the cache or very much at all on 3rd party database cache. Interested if anyone else is using it with 3rd party DB and run into this issue.
Thanks
W
2. Java version: 11.0.0.1
3. OS type and the version: Ubuntu 24.04 LTS
4. UA (phone), gateway or other hardware/software involved: None
5. Your problem:
Database Cache mode, anyone know how it works (apart from the obvious!!!)
We use 3rd party DB and have another system where user add their SIP login accounts. this then gets replicated to the SQL DB that BSS queries.
All has been fine until we upgraded and now have cache mode. What we have discovered is that a user adds their SIP account to our system. They then login in their SIP phone BEFORE the sync has taken place, so at this stage BSS would fail the register. After a few mins our system adds the SIP account into BSS, but after this, BSS rejects all attempts for that user name, without even checking the DB.
If however I login to the BSS admin page, and make any change to the username, eg add a single '.' to the comment, then BSS allows login and works. I suspect me making a change to the description causes the cache to be refreshed and BSS looks at the DB.
I really want to keep the cache as I think it's really useful for keeping DB traffic down, but how can I avoid the above scenario? I looked through API commands but there doesn't seem to be much about how to force BSS to refresh the cache or very much at all on 3rd party database cache. Interested if anyone else is using it with 3rd party DB and run into this issue.
Thanks
W