[Serusers] SRV failover question
Greger V. Teigre
greger at teigre.com
Mon Dec 4 21:32:50 CET 2006
Paul,
Yes, the link doesn't really help ;-) The point was this snippet:
"In ser CVS there was DNS cache and SRV failover support added recently.
It will do the failover automatically."
You see, SER 0.9.x does not have automatic failover based on SRV (SER
Ottendorf, upcoming release does). You need to do special processing in
onfailure route, which is not really neat nor something you probably
want to do using SRV. Most people use LCR module for PSTN gateways, but
obviously, for occasional URLs with SRV records, that doesn't help much.
g-)
Paul Antinori (pantinor) wrote:
> Hi Steve,
>
> Yes I am trying to get SER to resend the INVITE to priority 2 after
> priority 1 timed out due to connection down scenario.
>
> Thank you,
>
> Paul
>
> -----Original Message-----
> From: Steve Blair [mailto:blairs at isc.upenn.edu]
> Sent: Monday, December 04, 2006 9:37 AM
> To: Paul Antinori (pantinor)
> Cc: Greger V. Teigre; serusers at iptel.org
> Subject: Re: [Serusers] SRV failover question
>
>
> Paul:
>
> Are you trying to get the proxy server to re-send the invite based on
> the SRV list or the phone?
>
> _Steve
>
> Paul Antinori (pantinor) wrote:
>
>> Greger and all,
>>
>> The URL does not really help. You will see my cfg script below is
>> already using rewritehostport with no port and the SRV name.
>> I also am not using t_on_failure as it should not be necessary
>> according the post by Klaus.
>>
>> Heres my SRV table with the ranking priorities:
>>
>> _sip._udp.vxml.pats.cisco.com SRV service location:
>> priority = 1
>> weight = 1
>> port = 5060
>> svr hostname = vxml-1.pats.cisco.com
>> _sip._udp.vxml.pats.cisco.com SRV service location:
>> priority = 2
>> weight = 1
>> port = 5060
>> svr hostname = vxml-2.pats.cisco.com
>> _sip._udp.vxml.pats.cisco.com SRV service location:
>> priority = 3
>> weight = 1
>> port = 5060
>> svr hostname = vxml-3.pats.cisco.com
>> pats.cisco.com nameserver = ns1.pats.cisco.com
>> vxml-1.pats.cisco.com internet address = 10.86.129.x
>> vxml-2.pats.cisco.com internet address = 10.86.129.x
>> vxml-3.pats.cisco.com internet address = 10.86.129.x
>> ns1.pats.cisco.com internet address = 10.86.129.x
>>
>>
>> Thanks anyone for any help,
>>
>> Paul
>>
>>
>>
>> ----------------------------------------------------------------------
>> --
>> *From:* Greger V. Teigre [mailto:greger at teigre.com]
>> *Sent:* Monday, December 04, 2006 6:41 AM
>> *To:* Paul Antinori (pantinor)
>> *Cc:* serusers at iptel.org
>> *Subject:* Re: [Serusers] SRV failover question
>>
>> http://lists.iptel.org/pipermail/serusers/2006-October/030813.html
>>
>> Paul Antinori (pantinor) wrote:
>>
>>> Hi,
>>>
>>> Regarding the SRV query addition in (ser-0.9.7-pre7), when the call
>>> fails on the first priority destination, it never seems to attempt to
>>>
>
>
>>> send the INVITE to the second priority destination in the SRV
>>> response list. Is there anything else to script in the ser.cfg file
>>> to get this to work?
>>>
>>> Thanks for help,
>>>
>>> Paul
>>>
>>> [root at iptel-sip-proxy /]# /usr/sbin/tethereal | grep SIP Capturing on
>>>
>
>
>>> eth0
>>> 10.100556 10.86.142.144 -> 10.86.129.17 SIP Request: INVITE
>>> sip:77710107773365 at 10.86.129.17:5060;transport=udp
>>> 10.101774 10.86.129.17 -> 10.86.142.144 SIP Status: 100 trying --
>>> your call is important to us
>>> 14.233596 10.86.129.17 -> 10.86.142.144 SIP Status: 408 Request
>>> Timeout 14.235930 10.86.142.144 -> 10.86.129.17 SIP Request: ACK
>>> sip:77710107773365 at 10.86.129.17:5060;transport=udp
>>> 2139 packets captured
>>>
>>> [root at iptel-sip-proxy /]# /usr/sbin/tethereal | grep DNS Capturing on
>>>
>
>
>>> eth0
>>> 4.279486 10.86.129.17 -> 10.86.129.16 DNS Standard query SRV
>>> _sip._udp.vxml.pats.cisco.com
>>> 4.279897 10.86.129.16 -> 10.86.129.17 DNS Standard query response
>>> SRV 1 1 5060 vxml-1.pats.cisco.com SRV 2 1 5060 vxml-2.pats.cisco.com
>>>
>
>
>>> SRV 3 1 5060 vxml-3.pats.cisco.com
>>>
>>> 4.280045 10.86.129.17 -> 10.86.129.16 DNS Standard query A
>>> vxml-1.pats.cisco.com
>>> 4.280231 10.86.129.16 -> 10.86.129.17 DNS Standard query response A
>>>
>
>
>>> 10.86.129.2 <--this is unplugged from the network
>>>
>>>
>>> debug=3
>>> fork=yes
>>> log_stderror=yes
>>> rev_dns=no
>>> port=5060
>>> children=4
>>> check_via=no
>>> sip_warning=yes
>>> fifo="/tmp/ser_fifo"
>>> uid="nobody"
>>> gid="nobody"
>>>
>>> #aliases for this proxy server
>>> #ie hostnames/domains that it routes for alias=sox.cisco.com
>>> alias=pats.cisco.com
>>>
>>> loadmodule "/usr/local/lib/ser/modules/sl.so"
>>> loadmodule "/usr/local/lib/ser/modules/tm.so"
>>> loadmodule "/usr/local/lib/ser/modules/rr.so"
>>> loadmodule "/usr/local/lib/ser/modules/maxfwd.so"
>>> loadmodule "/usr/local/lib/ser/modules/usrloc.so"
>>> loadmodule "/usr/local/lib/ser/modules/registrar.so"
>>> loadmodule "/usr/local/lib/ser/modules/textops.so"
>>>
>>> modparam("usrloc", "db_mode", 0)
>>> modparam("rr", "enable_full_lr", 1)
>>> modparam("tm","fr_timer",5)
>>> modparam("tm","fr_inv_timer",5)
>>>
>>> route{
>>>
>>>
>>> if (!mf_process_maxfwd_header("10")) {
>>> sl_send_reply("483","Too Many Hops");
>>> break;
>>> };
>>>
>>> if (uri=~"^sip:1") {
>>> log(1, "SER found 1*\n");
>>> rewritehostport("ccm.pats.cisco.com");route(1);break;
>>> }
>>> if (uri=~"^sip:2") {
>>> log(1, "SER Found 2*\n");
>>> rewritehostport("ccm.pats.cisco.com");route(1);break;
>>> }
>>> if (uri=~"^sip:7") {
>>> log(1, "SER Found 7*\n");
>>>
>>>
> rewritehostport("vxml.pats.cisco.com");route(1);break;
>
>>> }
>>> if (uri=~"^sip:8") {
>>> log(1, "SER Found 8*\n");
>>> rewritehostport("SER.pats.cisco.com");route(1);break;
>>> }
>>> if (uri=~"^sip:9") {
>>> log(1, "SER Found 9*\n");
>>>
>>> rewritehostport("ringtone.pats.cisco.com");route(1);break;
>>> }
>>>
>>> log(1,"Could Not Match DN to Route\n");
>>> route(1);
>>> }
>>>
>>> route[1]
>>> {
>>> if (!t_relay()) {
>>> sl_reply_error();
>>> };
>>> }
>>>
>>> ---------------------------------------------------------------------
>>> ---
>>>
>>> _______________________________________________
>>> Serusers mailing list
>>> Serusers at lists.iptel.org
>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>
>>>
>> ----------------------------------------------------------------------
>> --
>>
>> _______________________________________________
>> Serusers mailing list
>> Serusers at lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20061204/e1e93aa8/attachment.htm>
More information about the sr-users
mailing list