[Freeswitch-users] server failure
Tim St. Pierre
fs-list at communicatefreely.net
Sun Sep 19 21:21:39 PDT 2010
I think you are missing something, or at least not really explaining the problem.
SIP doesn't need to maintain a connection between calls. If you are using udp, there isn't any
If your server goes down (ie. crashes or reboots), and the registration information is stored in a
persistent database, it can still be valid when it comes back up, or that registration data can also
be used by a different server that is replicating the same data. Usually it's NAT that gets in the
way of this - closing the udp ports due to inactivity or something else similar. There are lots of
failover options in SIP. You can use SRV records with multiple proxies, etc. All a phone needs to
do is to keep a server informed of where to find it if a call comes in. There is no need to
maintain a connection.
Depending on the endpoint, a lot of phones will switch to a backup server, and keep trying the
primary server. If it comes back up, it wil re-register to the primary. Again, if this data is
replicated, it doesn't really matter which server it registers to, as long as it registers somewhere.
Maybe if you explain in a bit more detail, someone can help out a bit more.
marian szczepkowski wrote:
> From what I can gather the idiots who wrote SIP decided that a server
> is a never a point of failure, x.25 and all other telecommunication
> protocols I have had experience with are able to recover from a remote
> end error/restart. All I can find with SIP is a daft time out in the
> device to perform a re-registration request, and until that time the
> unit is unable to make a call.
> Am I missing something or do I have to go jump through hoops with my
> phone code to re-connect to a server after a server failure.
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
More information about the FreeSWITCH-users