Thirdlane.com logo

Realtime stopped to work

Posted by os11k on Fri, 04/11/2014
Forums
Thirdlane platform General Questions

Hi,

I have one Thirdlane system in production and currently realtime is not working properly. Basically if I add sip peer I can use it, but if I delete it through Gui and I see it is not in DB anymore, asterisk still show this user and I'm able to register with it, In this case helps only asterisk reload. After reload sip users are updated. Any help will be appreciated.

Thank you!

Submitted by os11k on Sat, 04/12/2014 Permalink

Hi,

It is 7.1.1.6, most interesting part is that it used to work before.

Thank you!

Submitted by summitgroup on Sun, 08/03/2014 Permalink

We have exactly the same issue os11k.

Never been able to resolve it even "asterisk guru's" are stumped as to why it's not working when the database connection is perfectly fine and there is no drops.

For now we just have a shell script to do a periodic reload which is a pain but the only way we've been able to get round the issue short of rebuilding the server.

Cheers,

Greg

Submitted by eeman on Wed, 08/13/2014 Permalink

this behavior is due to cache of the realtime peers. not caching is even more disastrous as you never know if a user is online, and BLF functions dont work without it. Another related issue is deleting a extension and re-creating one with the same extension number... it caches the old password resulting in failed registration attempts until sip is reloaded. I have also seen admins, for whatever batshit insane reason, just decide they want to change the sip password of an extension... same behavior. The cache contains the old password.

the irony is the only reason people pushed and pushed and PUSHED alex to move to Realtime was that they didnt like the sip module reloading all the time when they made a change.

the only GOOD fix would be for the Asterisk development group to come up with a command to flush the cache of a single peer. Then updates to an extension could involve flushing the cache of that one sip peer.

Submitted by summitgroup on Thu, 10/16/2014 Permalink

We managed to fix this by running up a brand new fresh install and forklifting the database.

After that, most things that were not working came good.

The one thing that didn't come over was the voicemails as they were in the database and we had to reconfigure any customisations.

Just remember that when you do this you have to use the same MAC and IP address.

Cheers,

Greg