This is strange. I only get the issues if I use rtpproxy_offer(). If I use force_rtp_proxy() then there are no delays.
- Julian On Tue, Jul 13, 2010 at 4:43 PM, Julian Yap <julianok...@gmail.com> wrote: > I'm having a problem where is looks like there is a delay in OpenSIPS > relaying a SIP packet back to the originating UA. > > Here is a stripped Ngrep trace which shows the time stamps. > > In the example: > 9.9.9.101 = IP of the Calling UA > 8.8.8.41 = IP of the Proxy > 9.9.9.15 = IP of the Called UA > > The 180 Ringing is received by the Proxy at 16:00:58.628464 but is > only relayed on at 16:00:58.918988. > > Trace: > > U 2010/07/13 16:00:58.560395 9.9.9.101:10673 -> 8.8.8.41:5060 > INVITE sip:5551...@my.proxy.com;user=phone SIP/2.0. > -- > U 2010/07/13 16:00:58.560599 8.8.8.41:5060 -> 9.9.9.101:10673 > SIP/2.0 100 Trying. > -- > U 2010/07/13 16:00:58.560658 8.8.8.41:5060 -> 9.9.9.101:10673 > SIP/2.0 407 Proxy Authentication Required. > -- > U 2010/07/13 16:00:58.588648 9.9.9.101:10673 -> 8.8.8.41:5060 > ACK sip:5551...@my.proxy.com SIP/2.0. > -- > U 2010/07/13 16:00:58.592480 9.9.9.101:10673 -> 8.8.8.41:5060 > INVITE sip:5551...@my.proxy.com;user=phone SIP/2.0. > -- > U 2010/07/13 16:00:58.592592 8.8.8.41:5060 -> 9.9.9.101:10673 > SIP/2.0 100 Trying. > -- > U 2010/07/13 16:00:58.594010 8.8.8.41:5060 -> 9.9.9.15:5060 > INVITE sip:+18085551...@9.9.9.15 SIP/2.0. > -- > U 2010/07/13 16:00:58.598573 9.9.9.15:5060 -> 8.8.8.41:5060 > SIP/2.0 100 Trying. > -- > U 2010/07/13 16:00:58.628464 9.9.9.15:5060 -> 8.8.8.41:5060 > SIP/2.0 180 Ringing. > -- > U 2010/07/13 16:00:58.628780 9.9.9.15:5060 -> 8.8.8.41:5060 > SIP/2.0 200 OK. > -- > U 2010/07/13 16:00:58.918988 8.8.8.41:5060 -> 9.9.9.101:10673 > SIP/2.0 180 Ringing. > _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users