<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">Ok, so rfc3263 defines what the user agent should do when a 503 reply, or no reply is received.<BR>What about the rest of the possible SIP replies?<BR><BR>We use several different ITSP's. I just checked the logs for our last 50,000 calls from all of them and there was a total of 19 different replies received.<BR><BR>They are:<BR>200,400,401,403,404,408,410,480,484,486,487,488,500,501,502,503,504,603<BR><BR>Some of these can occur under normal conditions, 486 is busy for example, or 487 is generated by a CANCEL.<BR><BR>What about the rest? Most of the rest can be classified as error conditions. Are you saying that if another error condition besides 503 is received that you don't do failover? Why? <BR><BR>Douglas.<BR><BR><BR><BR>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">----- Original Message ----<BR>From: Bogdan-Andrei Iancu <bogdan@voice-system.ro><BR>To: Douglas Garstang <dougmig33@yahoo.com>; users <A href="http://openser.org/" target=_blank>openser.org</A> <users@openser.org><BR>Sent: Friday, February 15, 2008 5:56:45 AM<BR>Subject: Re: [OpenSER-Users] Failover using NAPTR/SRV<BR><BR>Of course it is.....by IETF - see RFC3263.<BR><BR>4.3 Details of RFC 2782 Process<BR><BR><BR>Regards,<BR>Bogdan<BR><BR><BR>Douglas Garstang wrote:<BR>> Well that's weird. What do you mean by 'fail'? I thought dns_blacklist <BR>> was used when a 503 response was received? What if the connection <BR>> times out? What if another negative reply is received? Is this stuff <BR>> documented anywhere?<BR>><BR>> ----- Original Message ----<BR>> From: Bogdan-Andrei Iancu <<A href="mailto:bogdan@voice-system.ro"
target=_blank rel=nofollow ymailto="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</A>><BR>> To: Tobias Lindgren <<A href="mailto:tobias.lindgren@ip-only.se" target=_blank rel=nofollow ymailto="mailto:tobias.lindgren@ip-only.se">tobias.lindgren@ip-only.se</A>><BR>> Cc: <A href="mailto:users@openser.org" target=_blank rel=nofollow ymailto="mailto:users@openser.org">users@openser.org</A><BR>> Sent: Thursday, February 14, 2008 3:25:33 AM<BR>> Subject: Re: [OpenSER-Users] Failover using NAPTR/SRV<BR>><BR>> Hi Tobias,<BR>><BR>> if you have "dns_backlist=yes" in your config, if one of the destination<BR>> server fails (according to SIP definition), it's IP will be added to a<BR>> temporary blacklist (for 4 minutes) and not used. So, openser should do<BR>> dns-based failover and use the next entry provided by NAPTR/SRV/A lookup.<BR>><BR>> Regards,<BR>> Bogdan<BR>><BR>> Tobias Lindgren
wrote:<BR>> > Hi all,<BR>> ><BR>> > I've been trying to find this information but I cannot find any exact<BR>> > specifications on how it really works.<BR>> ><BR>> > >From what I know using NAPTR/SRV records with OpenSER will allow <BR>> it to<BR>> > find and use servers behind those DNS-records. This works just fine.<BR>> ><BR>> > However, what I'm not sure about is what actually will happen in <BR>> OpenSER<BR>> > when one of two servers in this scenario would fail.<BR>> ><BR>> > For example, I have two servers as SRV where one is primary and one is<BR>> > secondary for SIP/UDP. What will happend in OpenSER when the primary<BR>> > server is down? Will OpenSER continue to send all request first towards<BR>> > that server or will it learn that one server is down and always send<BR>> > requests to the second server for a period of time and try
the primary<BR>> > one just occassionally?<BR>> ><BR>> > Please direct me to any page where this is explained in detail, if such<BR>> > page exists.<BR>> ><BR>> > Br,<BR>> > /Tobias<BR>> ><BR>> > _______________________________________________<BR>> > Users mailing list<BR>> > <A href="mailto:Users@lists.openser.org" target=_blank rel=nofollow ymailto="mailto:Users@lists.openser.org">Users@lists.openser.org</A> <mailto:<A href="mailto:Users@lists.openser.org" target=_blank rel=nofollow ymailto="mailto:Users@lists.openser.org">Users@lists.openser.org</A>><BR>> > <A href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target=_blank rel=nofollow>http://lists.openser.org/cgi-bin/mailman/listinfo/users</A><BR>> ><BR>> > <BR>><BR>><BR>> _______________________________________________<BR>> Users mailing list<BR>> <A
href="mailto:Users@lists.openser.org" target=_blank rel=nofollow ymailto="mailto:Users@lists.openser.org">Users@lists.openser.org</A> <mailto:<A href="mailto:Users@lists.openser.org" target=_blank rel=nofollow ymailto="mailto:Users@lists.openser.org">Users@lists.openser.org</A>><BR>> <A href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target=_blank rel=nofollow>http://lists.openser.org/cgi-bin/mailman/listinfo/users</A><BR>><BR>><BR>> ------------------------------------------------------------------------<BR>> Never miss a thing. Make Yahoo your homepage. <BR>> <<A href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs" target=_blank rel=nofollow>http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs</A>> <BR><BR></DIV><BR></DIV></DIV><BR>
<HR SIZE=1>
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. <A href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ" target=_blank rel=nofollow>Try it now.</A></DIV><BR></DIV></div><br>
<hr size=1>Looking for last minute shopping deals? <a href="http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping">
Find them fast with Yahoo! Search.</a></body></html>