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.
You should understand if your server is functioning. Keep your terminology straight when stating its a "SIP" issue. Each UA is something of its own design. There are, like lots of communications protocols, a lot of things that can sit between a sip server and the UA that could make fluid communications difficult at times over a network. You should start with your registration log though. On 9/18/10, marian szczepkowski <marian@jozep.com.au> 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
-- Sent from my mobile device ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: tgraziano@voice.myitdepartment.net Fax: 434.984.8431 Email: tgraziano@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpdesk@voice.myitdepartment.net Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
Build switch on RAID 6 or RAID 10 ( if expensive then RAID 5). On Sat, Sep 18, 2010 at 4:57 PM, marian szczepkowski <marian@jozep.com.au>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
Well, it's hard to tell from his rant what exactly the failure was. A link failure, a registration failure, disk, etc. He also says there's no failover in SIP, but there are a lot if systems out there running with some type of HA mode (registrar, proxy, etc.). So if he rebuilt a system and he can;t register, he should try to figure out why. If it was a disk failure, a backup is an excellent idea (no matter what level of RAID). On Sat, Sep 18, 2010 at 1:30 PM, Shamun toha md <shamun.toha@gmail.com>wrote:
Build switch on RAID 6 or RAID 10 ( if expensive then RAID 5).
On Sat, Sep 18, 2010 at 4:57 PM, marian szczepkowski <marian@jozep.com.au>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
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
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
participants (5)
-
marian szczepkowski
-
Shamun toha md
-
Steven Ayre
-
Tim St. Pierre
-
Tony Graziano