[quote=“cdavellis”]Anyway, the problem I keep having is: Several times a day the system seems to just stop connecting in or out. When I check the active channels I see this:
emmanuelCLI> sip show channels
Peer User/ANR Call ID Seq (Tx/Rx) Format Last Msg
188.8.131.52 1423443433 4d2e30696ad 00397/00000 unknow(d)
1 active SIP channel(s)
emmanuelCLI> restart now
As you see - I have to restart to clear the channel. any ideas why this would happen. Could it be related to satellite delays? I am stumped.[/quote]
It probably could be related to satellite delays - but i wouldn’t like to say for sure that it is. However, it does seem similar to a SIP problem i’ve been having for the last month or two.
What happens is registration with one or both of my european SIP providers fails (sip show registry reports them as “Failed”). The only way i seem to be able to clear this is to restart asterisk. I’ve worked out that what’s happening is asterisk’s registration attempts time out - 10 times in a row - and asterisk gives up.
To fix the problem, i’ve changed the following settings in asterisk/channels/chan_sip.c in the source code tree:
#define DEFAULT_REGISTRATION_TIMEOUT 40
#define DEFAULT_REGATTEMPTS_MAX 20
I changed those from 20 and 10 respectively - i.e., doubled the timeout time and doubled the number of attempts it will make when a registration attempt times out.
This seems to have done the trick. Something similar might work for you too. It’s possible that what’s happening with you is that the satellite delay is pushing the registration round-trip time closer to the timeout limit - and a bit of network congestion pushes it over the edge. Does asterisk report SIP registration as failed?
You should be able to see if this is what’s happening from the logs - registration failures should be recorded in /var/log/asterisk/messages .