I think it sounds like the issue is having is his phone registers and the server then crashes. Because there is no connection kept open the phone doesn't detect the server is no longer available, so it keeps trying to send calls to the offline server instead of switching to another server.

There are a few solutions:
1) Client side: Either get a phone that can fall back to a backup, or log out and in again
2) Server side: Install a load balancer/ipvs/virtual ip to perform HA so that when one server fails another server automatically takes over its calls
3) Client+server combination: Use DNS SRV records to give the client a list of several servers with weights & priorities. It'll rely on the client supporting that though, and not just calling the same IP from the pool every time.

-Steve


On 20 September 2010 05:21, Tim St. Pierre <fs-list@communicatefreely.net> wrote:
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
state maintained.

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.

-Tim

marian szczepkowski wrote:
>   Hi
>
>  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@lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org


_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org