sipsorcery server is down

[eviljafar]

I discovered today that one of my providers had become deregistered in SS. I haven't change anything in the last few weeks. On the Providers tab the Register check box for one of my providers (Callcentric) was unchecked, and the Disabled Reason was "Sipsorcey could not resolve the registrar". I logged into the Callcentric web dashboard and it was showing my service as unregistered. All my outbound calls were working but my inbound calls were going straight to voice mail and not surprisingly my phone was not displaying Message Waiting Indicator

I checked the Register box, hit save and the problem was solved.

I use three providers and the other two did not suffer this problem. I have read the posts about the recent db changes and the outage so I guess it might be related to one or both of these things.

If it was caused by the recent activity and outage why did SS deregister one provider but not the other two? Maybe it had nothing to do with the outage? Are there any setting changes I could make that would avoid this happening in the future?

Jaf.

[MikeTelis]

eviljafar,

it could be the same problem. Hope Aaron will fix it.

[cantaloupe]

[3rd party registrations disabled: A number of people have noted that when the sipsorcery server came back up a number of their 3rd party registrations had been disabled with an error message that the provider host could not be resolved in DNS. This behaviour is by design and is necessary. I still find it amazing what ends up in certain fields for provider information and invalid and non-existent hostnames can result in a lot of unecessary work by the sipsorcery registration agent. In this case the providers disabled had genuine host names but because of the networking issue on the Amazon EC2 instance DNS resolutions appear to have been sporadically failing and providing false results to the sipsorcery registration agent.

http://sipsorcery.wordpress.com/

[MikeTelis]

Of course, this is necessary. I just disagree with the implementation, I think that Aaron could have allowed more attempts and longer time. Say, disable registration if it's impossible to resolve SIP proxy server name within an hour. And of course, it's possible to "stretch" the pause between successive attempts. Say, try every 10 minutes (so it would be only 6 attempts, no such a big deal for sipsorcery registration agent).

[Aaron]

For a SIP provider entry to be turned off due to DNS it takes 6 DNS failures where each one is made 3 minutes apart. To me that's better than 6 retires 10 minutes apart as a transient DNS issues are likely to be resolved in a shorter space of time than 10 minutes and the sooner the provider entry can get registered again the better.

If the server is experiencing a major issue as it was on Thu/Fri it's not going to matter whether the retires are spread over 18 minutes or 60 minutes.

[MikeTelis]

I still can't understand what happened after you rebooted the server. All I know is that I found my registration to comtube.ru disabled and the same happened to all my friends' accounts. Once I checked "Register" box, SS restored registration. It was when I suggested that you keep trying for a longer time. I find it weird that the problem hasn't fixed itself after 18 minutes, but this is exactly what happened!

I realize that disabling registrations is a necessary step to reduce the load onto registration agent and save it from futile attempts in case a user just mistyped server name or the server has ceased to exist. On the other hand, unreasonable disabling may generate even a bigger load as the users login to SS website and proceed to SIP accounts page to re-enable registrations. There is a thick chance some won't quickly realize what happened and keep circling around web pages creating even bigger load.

So, every coin has two sides (that's what my friend said when his mother-in-law died but he had to pay for the funeral!)

[Aaron]

I thought the registrations were disabled before the reboot. The sipsorcery server and the agents did not go down during Thu/Fri they were just not able to communicate with the outside World. At some stages during the two days it appears as if the sipsorcery was able to communicate with DNS bit it was sporadic and somehow that resulted in some provider registrations getting disabled.

[mxnerd]

Though I'm not using Voxalot account anymore, it seems it's blocking Sipsorcery.com
I can login Voxalot website without problem, however.

I tried to re-register in Sipsorcery.com for Voxalot account and the message I got is
"There was an error performing a SIP Proider update.Attempted to perform an unauthorized operation."

[MikeTelis]

I thought the registrations were disabled before the reboot. The sipsorcery server and the agents did not go down during Thu/Fri they were just not able to communicate with the outside World. At some stages during the two days it appears as if the sipsorcery was able to communicate with DNS bit it was sporadic and somehow that resulted in some provider registrations getting disabled.

Oh, yes! I think you're right, it happened before reboot! If so, there's no reason to change your current algorithm.

Thanks for the explanation!

[MikeTelis]

Though I'm not using Voxalot account anymore, it seems it's blocking Sipsorcery.com
I can login Voxalot website without problem, however.

I tried to re-register in Sipsorcery.com for Voxalot account and the message I got is
"There was an error performing a SIP Proider update.Attempted to perform an unauthorized operation."

Try to logout from SS and login again. I don't think something's wrong with Voxalot, it's just that your SS session expired.