<div dir="ltr">Please always respond on a proper thread with a proper subject line. No one can tell what you are talking about and to what thread you are responding when you reply to a Users Digest email.<div><br></div><div>
Regards,</div><div>Ali Pey<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 3, 2013 at 4:47 AM, Chandra Prakash <span dir="ltr"><<a href="mailto:chandraprakash@virtualemployee.com" target="_blank">chandraprakash@virtualemployee.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Thanks Jeff,<br>
<br>
And Sorry for the delayed response.<br>
<br>
The endpoints are Bria.<br>
Network :- 5 Mbps leased line which is directly connected to the server.<br>
<br>
I tried to reconfigure the RTPproxy but in vain.<br>
<br>
Thanks<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:users-bounces@lists.opensips.org">users-bounces@lists.opensips.org</a><br>
[mailto:<a href="mailto:users-bounces@lists.opensips.org">users-bounces@lists.opensips.org</a>] On Behalf Of<br>
<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a><br>
Sent: 26 November 2013 23:05<br>
To: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
Subject: Users Digest, Vol 64, Issue 70<br>
<br>
Send Users mailing list submissions to<br>
<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@lists.opensips.org">users-owner@lists.opensips.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific than<br>
"Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Delay with RTPproxy (Chandra Prakash)<br>
2. DNS SRV failover not working for B2BUA (1.10) (Jeff Pyle)<br>
3. Re: opensips sends CANCEL (Miha)<br>
4. Re: Delay with RTPproxy (Jeff Pyle)<br>
5. Re: DNS SRV failover not working for B2BUA (1.10) (Jeff Pyle)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 26 Nov 2013 19:46:51 +0530<br>
From: "Chandra Prakash" <<a href="mailto:chandraprakash@virtualemployee.com">chandraprakash@virtualemployee.com</a>><br>
Subject: [OpenSIPS-Users] Delay with RTPproxy<br>
To: <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID: <000001ceeab2$29cc5ba0$7d6512e0$@<a href="http://virtualemployee.com" target="_blank">virtualemployee.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
<br>
Hi,<br>
<br>
I've configured opensip 1.8 with RTPproxy 1.2.<br>
<br>
All work fine except there is delay in RTP sessions. Is there any fix for<br>
this problem ?<br>
<br>
Pls help<br>
<br>
Thanks<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 26 Nov 2013 09:23:01 -0500<br>
From: Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>><br>
Subject: [OpenSIPS-Users] DNS SRV failover not working for B2BUA<br>
(1.10)<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID:<br>
<<a href="mailto:CACYJG3Ld_usgP10WGQu4LfEMmfh5MPpVGwhKCiZHqXN4WeFdxQ@mail.gmail.com">CACYJG3Ld_usgP10WGQu4LfEMmfh5MPpVGwhKCiZHqXN4WeFdxQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hello,<br>
<br>
I have an SRV name as follows:<br>
<br>
$ dig +short -tSRV _sip._<a href="http://udp.proxyname.domain.com" target="_blank">udp.proxyname.domain.com</a><br>
1 10 5060 <a href="http://host1.domain.com" target="_blank">host1.domain.com</a>.<br>
2 10 5060 <a href="http://host2.domain.com" target="_blank">host2.domain.com</a>.<br>
<br>
If I t_relay() a request with <a href="http://proxyname.domain.com" target="_blank">proxyname.domain.com</a> as the request domain,<br>
and host1 does not answer within fr_timer seconds, the request is re-relayed<br>
to host2. This is good.<br>
<br>
If I b2b_init_request("top hiding") instead of t_relay(), the 408 is<br>
forwarded back towards the UAC after host1 doesn't answer. The request is<br>
never re-relayed to host2.<br>
<br>
There is a difference in the debug output after the 408 is generated for<br>
host1. With the B2BUA it looks like is_3263_failure() never happens.<br>
<br>
t_relay:<br>
Nov 26 09:03:38 [16296] DBG:tm:timer_routine: timer<br>
routine:0,tl=0x7fbe6c7c0060 next=(nil), timeout=61 Nov 26 09:03:38 [16296]<br>
DBG:tm:final_response_handler: Cancel sent out, sending 408 (0x7fbe6c7bfe10)<br>
Nov 26 09:03:38 [16296] DBG:tm:t_should_relay_response: T_code=100,<br>
new_code=408<br>
Nov 26 09:03:38 [16296] DBG:tm:t_pick_branch: picked branch 0, code 408<br>
(prio=800)<br>
Nov 26 09:03:38 [16296] DBG:tm:is_3263_failure: dns-failover test:<br>
branch=0, last_recv=408, flags=1<br>
Nov 26 09:03:38 [16296] DBG:tm:t_should_relay_response: trying DNS-based<br>
failover Nov 26 09:03:38 [16296] DBG:tm:do_dns_failover: new destination<br>
available Nov 26 09:03:38 [16296] DBG:core:check_ip_address: params<br>
127.0.0.1, 127.0.0.1, 0 Nov 26 09:03:38 [16296] DBG:tm:set_timer: relative<br>
timeout is 500000<br>
<br>
b2b_init_request:<br>
Nov 26 09:12:21 [16401] DBG:tm:timer_routine: timer<br>
routine:0,tl=0x7f09ddcbf7e8 next=(nil), timeout=11 Nov 26 09:12:21 [16401]<br>
DBG:tm:final_response_handler: Cancel sent out, sending 408 (0x7f09ddcbf598)<br>
Nov 26 09:12:21 [16401] DBG:tm:t_should_relay_response: T_code=0,<br>
new_code=408<br>
Nov 26 09:12:21 [16401] DBG:tm:t_pick_branch: picked branch 0, code 408<br>
(prio=800)<br>
Nov 26 09:12:21 [16401] DBG:tm:local_reply: branch=0, save=0, winner=0 Nov<br>
26 09:12:21 [16401] DBG:tm:local_reply: local transaction completed Nov 26<br>
09:12:21 [16401] DBG:tm:run_trans_callbacks: trans=0x7f09ddcbf598, callback<br>
type 256, id 0 entered Nov 26 09:12:21 [16401]<br>
DBG:b2b_entities:b2b_tm_cback: tm [0x7f09ddcbf598] notification cb for [408]<br>
reply Nov 26 09:12:21 [16401] DBG:b2b_entities:b2b_parse_key: hash_index =<br>
[472]<br>
- local_index= [2611231]<br>
Nov 26 09:12:21 [16401] DBG:b2b_entities:b2b_tm_cback: Received reply [408]<br>
for dialog [0x7f09ddcbf2b8], method [INVITE]<br>
<br>
Is there something extra that must occur in the script to get DNS failover<br>
behavior with the B2BUA? Or, is this a bug?<br>
<br>
<br>
Regards,<br>
Jeff<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://lists.opensips.org/pipermail/users/attachments/20131126/28856aa9/att
achment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20131126/28856aa9/att<br>
achment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 26 Nov 2013 15:22:25 +0100<br>
From: Miha <<a href="mailto:miha@softnet.si">miha@softnet.si</a>><br>
Subject: Re: [OpenSIPS-Users] opensips sends CANCEL<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID: <<a href="mailto:5294AEA1.8040001@softnet.si">5294AEA1.8040001@softnet.si</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
Please ignore this email as "CANCEL" was send due to dual forking.<br>
<br>
error messages are due to empty message;)<br>
<br>
br<br>
miha<br>
Dne 11/26/2013 10:09 AM, pi?e Miha:<br>
> Hi,<br>
><br>
> could some take a look at this error and tell me what are they about?<br>
><br>
> You can see from I trace that opensips sends cancel.<br>
><br>
> Tnx!<br>
><br>
><br>
><br>
><br>
> Nov 26 10:04:04 sip2 /usr/sbin/opensips[13364]:<br>
> ERROR:auth:consume_credentials: no authorized credentials found (error<br>
> in scripts)<br>
><br>
><br>
> Nov 26 10:04:06 sip2 /usr/sbin/opensips[13358]:<br>
> INFO:core:parse_first_line: empty or bad first line Nov 26 10:04:06<br>
> sip2 /usr/sbin/opensips[13358]:<br>
> INFO:core:parse_first_line: bad message Nov 26 10:04:06 sip2<br>
> /usr/sbin/opensips[13358]: ERROR:core:parse_msg:<br>
> message=<><br>
> Nov 26 10:04:06 sip2 /usr/sbin/opensips[13358]:<br>
> ERROR:core:receive_msg: parse_msg failed Nov 26 10:04:09 sip2<br>
> /usr/sbin/opensips[13362]:<br>
> INFO:core:parse_first_line: empty or bad first line Nov 26 10:04:09<br>
> sip2 /usr/sbin/opensips[13362]:<br>
> INFO:core:parse_first_line: bad message Nov 26 10:04:09 sip2<br>
> /usr/sbin/opensips[13362]: ERROR:core:parse_msg:<br>
> message=<><br>
> Nov 26 10:04:09 sip2 /usr/sbin/opensips[13362]:<br>
> ERROR:core:receive_msg: parse_msg failed<br>
><br>
><br>
> Nov 26 10:04:17 sip2 /usr/sbin/opensips[13358]: rc_avpair_new: unknown<br>
> attribute 0 Nov 26 10:04:17 sip2 /usr/sbin/opensips[13358]:<br>
> ERROR:aaa_radius:rad_avp_add: failure<br>
> Nov 26 10:04:17 sip2 /usr/sbin/opensips[13358]:<br>
> ERROR:acc:acc_aaa_cdrs: failed to add Sip-Response-Code, 2 Nov 26<br>
> 10:04:17 sip2 /usr/sbin/opensips[13358]:<br>
> ERROR:acc:acc_dlg_callback: Cannot create radius accounting<br>
><br>
><br>
> 5.396017 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP/SDP Request: INVITE<br>
> sip:018108753@OPENSIPS_REGISTRATION_DOMAIN, with session description<br>
> 5.396254 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Status: 407 Proxy<br>
> Authentication Required<br>
> 5.433576 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Request: ACK<br>
> sip:018108753@OPENSIPS_REGISTRATION_DOMAIN<br>
> 5.454962 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP/SDP Request: INVITE<br>
> sip:018108753@OPENSIPS_REGISTRATION_DOMAIN, with session description<br>
> 5.458034 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Status: 100 Giving a try<br>
> 5.458104 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP/SDP Request: INVITE<br>
> sip:38618108753@OPENSIPS_REGISTRATION_DOMAIN, with session description<br>
> 5.459878 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 100 Trying<br>
> 5.495447 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP/SDP Request: INVITE<br>
> <a href="http://sip:38618108753@opensips_domain.com:5060" target="_blank">sip:38618108753@opensips_domain.com:5060</a>, with session description<br>
> 5.501095 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP Status: 100 Giving a try<br>
> 5.501164 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP/SDP Request: INVITE<br>
> sip:38618108753@PUBLIC_IP:12415, with session description<br>
> 5.501184 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP/SDP Request: INVITE<br>
> sip:38618108753@PUBLIC_IP:12839, with session description<br>
> 5.501199 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP/SDP Request: INVITE<br>
> sip:38618108753@PUBLIC_IP:12825, with session description<br>
> 5.508026 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> ICMP Destination unreachable<br>
> (Port unreachable)<br>
> 5.517724 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 100 Trying<br>
> 5.531442 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 100 Trying<br>
> 5.563314 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 180 Ringing<br>
> 5.563426 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP Status: 180 Ringing<br>
> 5.577177 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 180 Ringing<br>
> 5.577295 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Status: 180 Ringing<br>
> 5.670741 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 180 Ringing<br>
> 5.670840 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP Status: 180 Ringing<br>
> 5.999281 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP/SDP Request: INVITE<br>
> sip:38618108753@PUBLIC_IP:12825, with session description<br>
> 6.005052 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> ICMP Destination unreachable<br>
> (Port unreachable)<br>
> 7.000772 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP/SDP Request: INVITE<br>
> sip:38618108753@PUBLIC_IP:12825, with session description<br>
> 7.005184 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> ICMP Destination unreachable<br>
> (Port unreachable)<br>
> 7.044043 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP/SDP Status: 200 OK, with<br>
> session description<br>
> 7.044191 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP/SDP Status: 200 OK, with<br>
> session description<br>
> 7.044242 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Request: CANCEL<br>
> sip:38618108753@PUBLIC_IP:12839<br>
> 7.066863 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP/SDP Status: 200 OK, with<br>
> session description<br>
> 7.066981 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP/SDP Status: 200 OK, with<br>
> session description<br>
> 7.132422 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Request: ACK<br>
> sip:018108753@FS_IP:5060;transport=udp<br>
> 7.132583 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP Request: ACK<br>
> sip:018108753@FS_IP:5060;transport=udp<br>
> 7.137809 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 200 OK<br>
> 7.143045 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Request: ACK<br>
> sip:38618108753@PUBLIC_IP:12415<br>
> 7.143185 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Request: ACK<br>
> sip:38618108753@PUBLIC_IP:12415<br>
> 7.163169 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP/SDP Request: UPDATE<br>
> sip:38618108753@PUBLIC_IP:12415, with session description<br>
> 7.163320 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP/SDP Request: UPDATE<br>
> sip:38618108753@PUBLIC_IP:12415, with session description<br>
> 7.174618 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 487 Request<br>
> Terminated<br>
> 7.174722 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Request: ACK<br>
> sip:38618108753@PUBLIC_IP:12839<br>
> 7.202234 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP/SDP Status: 200 OK, with<br>
> session description<br>
> 7.202322 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP/SDP Status: 200 OK, with<br>
> session description<br>
> 9.598791 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Request: BYE<br>
> sip:mod_sofia@FS_IP:5080<br>
> 9.599032 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP Request: BYE<br>
> sip:mod_sofia@FS_IP:5080<br>
> 9.604072 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Status: 200 OK<br>
> 9.604184 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Status: 200 OK<br>
> 9.609102 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Request: BYE<br>
> sip:38618108751@PUBLIC_IP:12824<br>
> 9.609294 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Request: BYE<br>
> sip:38618108751@PUBLIC_IP:12824<br>
> 9.612840 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> ICMP Destination unreachable<br>
> (Port unreachable)<br>
> 10.105298 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Request: BYE<br>
> sip:38618108751@PUBLIC_IP:12824<br>
> 10.108784 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> ICMP Destination<br>
> unreachable (Port unreachable)<br>
> 10.609232 FS_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> SIP Request: BYE<br>
> sip:38618108751@PUBLIC_IP:12824<br>
> 11.106821 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> PUBLIC_IP SIP Request: BYE<br>
> sip:38618108751@PUBLIC_IP:12824<br>
> 11.110774 PUBLIC_IP -> <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> ICMP Destination<br>
> unreachable (Port unreachable)<br>
> 11.307190 <a href="http://opensips_domain.com" target="_blank">opensips_domain.com</a> -> FS_IP SIP Request: INFO<br>
> sip:FS_IP:5060<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 26 Nov 2013 10:17:23 -0500<br>
From: Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>><br>
Subject: Re: [OpenSIPS-Users] Delay with RTPproxy<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID:<br>
<<a href="mailto:CACYJG3Kb1DNQk-u9AZO7ntRg7Kt1rnkqhHZEcm19yWgqWwP8EQ@mail.gmail.com">CACYJG3Kb1DNQk-u9AZO7ntRg7Kt1rnkqhHZEcm19yWgqWwP8EQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Chandra,<br>
<br>
In my experience RTP delay is almost always the result of network latency or<br>
excessive jitter buffers on the endpoints. I doubt rtpproxy is the problem.<br>
<br>
What endpoints are you using? What is the network configuration?<br>
<br>
<br>
- Jeff<br>
<br>
<br>
<br>
<br>
On Tue, Nov 26, 2013 at 9:16 AM, Chandra Prakash <<br>
<a href="mailto:chandraprakash@virtualemployee.com">chandraprakash@virtualemployee.com</a>> wrote:<br>
<br>
><br>
> Hi,<br>
><br>
> I've configured opensip 1.8 with RTPproxy 1.2.<br>
><br>
> All work fine except there is delay in RTP sessions. Is there any fix<br>
> for this problem ?<br>
><br>
> Pls help<br>
><br>
> Thanks<br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://lists.opensips.org/pipermail/users/attachments/20131126/e2f11a7f/att
achment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20131126/e2f11a7f/att<br>
achment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 26 Nov 2013 12:34:42 -0500<br>
From: Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>><br>
Subject: Re: [OpenSIPS-Users] DNS SRV failover not working for B2BUA<br>
(1.10)<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID:<br>
<<a href="mailto:CACYJG3K_%2BSXEeyc4STyzBEdBUmJY4nkj1EjvfdDS72dp_cw_Hw@mail.gmail.com">CACYJG3K_+SXEeyc4STyzBEdBUmJY4nkj1EjvfdDS72dp_cw_Hw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
I have same the SRV failover problem with uac_registrant-generated REGISTER<br>
requests.<br>
<br>
After little bit of digging it looks like there is no proxy structure<br>
associated with internally generated requests, and no DNS-based failover<br>
without it.<br>
<br>
Issue #140 <<a href="https://github.com/OpenSIPS/opensips/issues/140" target="_blank">https://github.com/OpenSIPS/opensips/issues/140</a>> logged.<br>
<br>
<br>
- Jeff<br>
<br>
<br>
On Tue, Nov 26, 2013 at 9:23 AM, Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>> wrote:<br>
<br>
> Hello,<br>
><br>
> I have an SRV name as follows:<br>
><br>
> $ dig +short -tSRV _sip._<a href="http://udp.proxyname.domain.com" target="_blank">udp.proxyname.domain.com</a><br>
> 1 10 5060 <a href="http://host1.domain.com" target="_blank">host1.domain.com</a>.<br>
> 2 10 5060 <a href="http://host2.domain.com" target="_blank">host2.domain.com</a>.<br>
><br>
> If I t_relay() a request with <a href="http://proxyname.domain.com" target="_blank">proxyname.domain.com</a> as the request<br>
> domain, and host1 does not answer within fr_timer seconds, the request<br>
> is re-relayed to host2. This is good.<br>
><br>
> If I b2b_init_request("top hiding") instead of t_relay(), the 408 is<br>
> forwarded back towards the UAC after host1 doesn't answer. The<br>
> request is never re-relayed to host2.<br>
><br>
> There is a difference in the debug output after the 408 is generated<br>
> for host1. With the B2BUA it looks like is_3263_failure() never happens.<br>
><br>
> t_relay:<br>
> Nov 26 09:03:38 [16296] DBG:tm:timer_routine: timer<br>
> routine:0,tl=0x7fbe6c7c0060 next=(nil), timeout=61 Nov 26 09:03:38<br>
> [16296] DBG:tm:final_response_handler: Cancel sent out, sending 408<br>
> (0x7fbe6c7bfe10) Nov 26 09:03:38 [16296]<br>
> DBG:tm:t_should_relay_response: T_code=100,<br>
> new_code=408<br>
> Nov 26 09:03:38 [16296] DBG:tm:t_pick_branch: picked branch 0, code<br>
> 408<br>
> (prio=800)<br>
> Nov 26 09:03:38 [16296] DBG:tm:is_3263_failure: dns-failover test:<br>
> branch=0, last_recv=408, flags=1<br>
> Nov 26 09:03:38 [16296] DBG:tm:t_should_relay_response: trying<br>
> DNS-based failover Nov 26 09:03:38 [16296] DBG:tm:do_dns_failover: new<br>
> destination available Nov 26 09:03:38 [16296]<br>
> DBG:core:check_ip_address: params 127.0.0.1, 127.0.0.1, 0 Nov 26<br>
> 09:03:38 [16296] DBG:tm:set_timer: relative timeout is 500000<br>
><br>
> b2b_init_request:<br>
> Nov 26 09:12:21 [16401] DBG:tm:timer_routine: timer<br>
> routine:0,tl=0x7f09ddcbf7e8 next=(nil), timeout=11 Nov 26 09:12:21<br>
> [16401] DBG:tm:final_response_handler: Cancel sent out, sending 408<br>
> (0x7f09ddcbf598) Nov 26 09:12:21 [16401]<br>
> DBG:tm:t_should_relay_response: T_code=0,<br>
> new_code=408<br>
> Nov 26 09:12:21 [16401] DBG:tm:t_pick_branch: picked branch 0, code<br>
> 408<br>
> (prio=800)<br>
> Nov 26 09:12:21 [16401] DBG:tm:local_reply: branch=0, save=0, winner=0<br>
> Nov 26 09:12:21 [16401] DBG:tm:local_reply: local transaction<br>
> completed Nov 26 09:12:21 [16401] DBG:tm:run_trans_callbacks:<br>
> trans=0x7f09ddcbf598, callback type 256, id 0 entered Nov 26 09:12:21<br>
> [16401] DBG:b2b_entities:b2b_tm_cback: tm [0x7f09ddcbf598]<br>
> notification cb for [408] reply Nov 26 09:12:21 [16401]<br>
> DBG:b2b_entities:b2b_parse_key: hash_index = [472]<br>
> - local_index= [2611231]<br>
> Nov 26 09:12:21 [16401] DBG:b2b_entities:b2b_tm_cback: Received reply<br>
> [408] for dialog [0x7f09ddcbf2b8], method [INVITE]<br>
><br>
> Is there something extra that must occur in the script to get DNS<br>
> failover behavior with the B2BUA? Or, is this a bug?<br>
><br>
><br>
> Regards,<br>
> Jeff<br>
><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL:<br>
<<a href="http://lists.opensips.org/pipermail/users/attachments/20131126/e2d04642/att
achment.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20131126/e2d04642/att<br>
achment.htm</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
End of Users Digest, Vol 64, Issue 70<br>
*************************************<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div><img class="" src="https://contactmonkey.com/api/v1/tracker?cm_session=71ef4668-0133-4030-a711-5d8810020257&cm_type=open&cm_user_email=alipey@gmail.com"><img class="" src="https://contactmonkey.com/api/v1/tracker?cm_session=b614b967-b523-474d-b3b5-4510ceb95cb7&cm_type=open&cm_user_email=alipey@gmail.com"></div>
</div>